Feat/ome consolidated metadata - #97
Open
konstibob wants to merge 3 commits into
Open
Conversation
Member
|
Blocked until #91 lands. |
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
2 participants
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.
efficiency gain for ome zarr.
MultiscaleImage.open(handle) had to figure out which OME-Zarr version it was looking at. The version is written inside zarr.json. So it did the following:
It builds the OME object from a group you already have. And openX(handle) is now just fromGroup(Group.open(handle)) — so the old entry point still exists and behaves the same, it's only split in two.
This applies to all three OME versions, 0.4 included.
opening a plate or image went from 3 requests to 1. A 0.4 plate went from 6 to 4.