Document that axes/transformations should be consistent with METADATA.ome.xml #71
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
sbesson
approved these changes
Feb 21, 2022
There was a problem hiding this comment.
This clarifies the expectation of raw2ometiff regarding the current source of truth and I think it's valuable to get this in to prevent surprises.
Dealing with the consolidation/reconciliation of metadata duplicated in several places will certainly be a major concern that will arise as part of future OME-NGFF work.
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.
Discussed briefly with @joshmoore / @sbesson / @dgault, we don't currently have a strategy for mismatches between Zarr metadata and
METADATA.ome.xml. Until we figure out a better policy, this at least sets the expectation that onlyMETADATA.ome.xmlis used here.