Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Artifact with image display #631

Closed
arjunrajlab opened this issue Jan 29, 2024 · 2 comments
Closed

Artifact with image display #631

arjunrajlab opened this issue Jan 29, 2024 · 2 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@arjunrajlab
Copy link
Collaborator

We are having an issue with image display with an artifact of a vertical line:

image

This showed up on another file as well recently (the very large "Golnaz" dataset), but this dataset is a lot easier to work with. Here's a link to the dataset:
https://www.dropbox.com/scl/fi/e471z4mu0v4hbtxsc4qae/slide1_2_fluor.nd2?rlkey=emarbyg1q7g3dbt2bfo3kd7kv&dl=0

I also uploaded here to nimbusimage.com:
https://nimbusimage.com/#/datasetView/65b7c46adda92c449e614cce/view?z=5

Send login details to @manthey

@arjunrajlab arjunrajlab added the bug Something isn't working label Jan 29, 2024
@arjunrajlab arjunrajlab added this to the Alpha-Version milestone Jan 29, 2024
@arjunrajlab
Copy link
Collaborator Author

Some more images. Seems to go away when you zoom in.

image image

@manthey
Copy link
Collaborator

manthey commented Jan 29, 2024

This: girder/large_image#1447 will fix the issue.

The issue occurred because when the multi-source source composites images, it now can do general transformations. If a simple power of two scaling is sufficient this is bypassed (which was only the behavior before girder/large_image#1415). The detection on if the basic scaling or the general transform was needed used the general transform needlessly. PR 1447 fixes that.

The actual issue is that when the general transform is applied, an alpha channel is added when needed. On this sample, at anything other than the full resolution, this alpha channel exists for right/bottom edge tiles. The autoscaling for intensity was using this, so the non-edge tiles were fine, but the right/bottom edge tiles were too dark, since the autoscaling didn't apply the same way when a full range alpha channel exists. The alpha channel could also have been skipped (for this image which has one band or sample per pixel) by adding singleBand: true to the multi-source yaml/json file.

More generally, there should probably be a specification in the multi-source to "addAlphaBand: true/false/asneeded" or something to make this behavior more explicit and controllable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants