HCS Parser: Create ome.tiff well by well #3251
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes the way how we perform generation of OME.TIFF structure in HCS Parser.
Previously we generated one big
ome.tifffor each sequence, such file contains allwellsrelated to the sequence.The Pros here is that we had more easy and flat structure, but also Cons of such approach is that during generation of very big
ome.tiffs we could fail due to OOM errors, since such pictures requires a lot of memory to be generated.New approach generate
ome.tifffor eachwellin a sequence, it gives as more reliable systems, because, obviously suchome.tiffwill require less memory to be generated.This PR also includes changes regarding integrity check - during this check we validate that all pictures that are present in
Index.xmlfile actually exists.