You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generate example input and output coordinate arrays for each transformation listed in OME-Zarr RFC-5 (to be included in v0.6 release).
Ideally these would be presented in a language-agnostic format which closely aligns with the OME-Zarr serialisation of transformations so that tools can incorporate the test data into their own tests with little effort.
Define the input/output coordinates as e.g. numpy arrays (easy)
Serialise the OME-Zarr transform graph in a scene/ multiscales (easy-medium)
Describe and serialise the additional information needed by unit tests (medium)
Stretch goal: we could use a similar strategy to the OME-Zarr conformance tests where implementations provide a very simple CLI which takes some input coordinate, transforms them, and writes them out, and we provide a tool which iterates through all the of examples, feeds them into the CLI, and checks the output.
Generate example input and output coordinate arrays for each transformation listed in OME-Zarr RFC-5 (to be included in v0.6 release).
Example of tests already in spatialdata: https://github.com/scverse/spatialdata/blob/cf91ad57b86f43aa8998ff7aa8ef1363972325d8/tests/transformations/ngff/test_ngff_transformations.py#L173
Examples of OME-Zarr configuration for different transforms: https://github.com/bogovicj/ngff-rfc5-coordinate-transformation-examples