-
Notifications
You must be signed in to change notification settings - Fork 3
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
Ensure Plane DeltaT values are stored into SCIFIO axes #17
Comments
@ctrueden's comment ("non-linear SCIFIO axes to store the time stamps in a data-model-agnostic way") in fiji/fiji#74 got me interested in that topic. I dug a little into the code and stumbled across the If that topic is off the table, feel free to ignore my comment 😄 |
Whoa, how has this PR been sitting for over two years? Because the upstream imglib2 PR has sat that long? Maybe we can resolve this in the upcoming data model hackathon, as part of our work on the RichImage. @stelfrich You're right: the fact that every Plane in OME-XML can have a different DeltaT is more flexible than ImageJ2's axis-driven metadata model. The original "variable width time stamper" would not require the more flexible sort of metadata—just a non-linear time axis. But if we want to fully support what different file formats are already storing sometimes, I guess we need to make the metadata model more flexible. I fear the complexity but it seems like the correct thing to do. |
That was @dietzc's idea as well.
We just have to find a good balance between complexity and usability (as always). The use case that got me interested is actually pretty simple: label each slice of an image sequence with time stamps where the first time point shall be the Another use case that crossed my mind is a rather common setup in live cell fluorescence imaging: acquire a widefield image every 5 minutes and a fluorescence image every 20 minutes. The acquired image sequence is one |
Depends on imglib/imglib2#64
If there are
Plane DeltaT
values present in OME-XML, we should ensure the Axes of the parsed/translated metadata store them appropriately.The text was updated successfully, but these errors were encountered: