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

LIF image data ordering #511

Closed
wants to merge 1 commit into from
Closed

Conversation

SeanLeRoy
Copy link
Collaborator

Description

Intended to resolve #508 where it appeared the channels and timepoints were being swapped around. I was able to reproduce this and it seems the default C-like ordering of the images.

Testing

Let me know if you have some good unit test ideas, I think we'd need a new LIF file to test this appropriately (we can use the one from the discussion, but it would largely be testing nothing). I tested it locally by reading in various LIFs and comparing it against FIJI with different ordering styles.

@codecov-commenter
Copy link

codecov-commenter commented Jun 7, 2023

Codecov Report

Patch coverage has no change and project coverage change: -8.36 ⚠️

Comparison is base (448ed25) 94.01% compared to head (095d853) 85.65%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #511      +/-   ##
==========================================
- Coverage   94.01%   85.65%   -8.36%     
==========================================
  Files          53       53              
  Lines        4608     4608              
==========================================
- Hits         4332     3947     -385     
- Misses        276      661     +385     
Impacted Files Coverage Δ
aicsimageio/readers/lif_reader.py 5.98% <ø> (-89.44%) ⬇️

... and 3 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@SeanLeRoy
Copy link
Collaborator Author

Closing this out for now, the problem is more convoluted than I originally thought, may need to wait for a new readlif version

@SeanLeRoy SeanLeRoy closed this Jun 8, 2023
@SeanLeRoy SeanLeRoy deleted the bugfix/3.5.0-lif-file-reader-error branch June 16, 2023 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

channel-z ordering problem when reading lif
2 participants