Repository navigation
Conversation
clbarnes
force-pushed
the
transforms-tests
branch
from
November 1, 2026 19:41
ba624a0 to
33cc79a
Compare
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
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 ports most of the test cases from ome_zarr_transformations_conformance for validating the numerical accuracy of transforms.
Differences from oztc
conformance.tomlwithoztest.json, with the plan for this to be extended per Allow for descriptions in test cases #46.validvalidity but I'm OK with thatshould_error = truecases, previously only used for disconnected transform graphs, were not ported. These are better tested by thevalidate_zarrcases.To do