add channel_maps as metadata parameter to Bioformatsreader #201
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
…ilePatternMetadata
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.
I frequently use the ashlar python API to stitch my individual tif images using the FilePatternReader. I recently also started using .nd2 files. When adapting my workflow to utilise the BioformatsReader I discovered that it currently does not have the .metadata.channel_map property implemented in the FilePatternReader.
I added it to allow users to also access channel names when utilising the python API. For me this makes my workflow easily adaptable to many different bio format types.
Let me know if there is anything else I should do :)