Added support for companion ome-tiffs - #53
Merged
Merged
Conversation
This file contains hidden or 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
1 participant
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.
What is the purpose of this PR?
This PR closes #51 by adding support for 10x Genomics Xenium-style companion OME-TIFF files, where each channel is stored as a separate single-page TIFF file but contains OME-XML metadata referencing all channels via UUID.
How did you implement your changes
Updated the companion OME-TIFF detection and reading logic:
MultiplexedDataset._is_companion_ome_tiff_foldernow detects companion files by checking for <UUID FileName= in OME metadata.LazyOmeTiffLoader._parse_companion_channel_mappingnow maps the channel names from the ome-tiff metadata to the actual filenames.MultiplexedDataset.get_channelsreturns proper channel names for ome-tiff files that have them stored as metadata.Remaining issues
None.