-
Notifications
You must be signed in to change notification settings - Fork 241
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
Imspector metadata fixes #2913
Imspector metadata fixes #2913
Conversation
@melissalinkert @sbesson Thanks for looking at this. When I last spoke to the LaVision dev team they warned us that this format is subject to constant undocumented revision. We have concentrated since then on supporting their variant on ome-tiff (not without it's own problems) My apologies I should have noted this in the tickets. |
Discussed earlier today. Leaving this out of 5.6.0 and we can review in 5.6.1. |
I'll try and get the FLIMfit builds running again so we can ,potentially, send a test version (inc these changes) to our LaVision users. |
@imunro: any success with #2913 (comment), should we try to coordinate on the review of this PR? |
From my POV the only way I can test this PR is to build a version of FLIMfit incorporating these changes and send it to our known LaVision users to try with their data. |
The code changes here look good and builds and tests are green. Testing the related QA files: QA 11369
QA 17101 and QA 17102
|
This fixes several metadata parsing bugs in
ImspectorReader
that affect the dimensions andModuloAlongT
. The following tickets should be fixed with these changes:https://trac.openmicroscopy.org/ome/ticket/13002
https://trac.openmicroscopy.org/ome/ticket/13180
https://trac.openmicroscopy.org/ome/ticket/13181
https://trac.openmicroscopy.org/ome/ticket/13182
Existing Imspector .msr files should be unaffected, but new files for QA 17102 and QA 11369 need to be tested. Ticket 13180 references a file in QA 17101, but the same file is also present in QA 17102.
For each file, check
showinf -nopix -omexml
and verify that thestep
inModuloAlongT
matches the time per FLIM channel referenced in each ticket (usually 220.875 ps). If an expected value is not in the tickets, check thatend
inModuloAlongT
is greater than 1.Also verify that
SizeZ
,SizeC
, andSizeT
match the expected values in the tickets. The images will be easier to check in ImageJ; in particular check that the second channel looks plausible (for files withSizeC == 2
) and that the plane ordering seems sensible (i.e. the dimension order is not mixed up).This should not affect memo files, so could be deferred until 5.6.1 if necessary. If @imunro gets a chance, a quick review from the original reporter/triager of the above tickets might be useful.