-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENH: Support different axis orders #45
Comments
ITK's default order of axes is Channel axis should be treated differently, as per #32. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
After #43 ITKIOOMEZarrNGFF will support reading from OME-Zarr stores where spatial axes appear in the order
z,y,x
. For instance, the following are supported:y,x
z,y,x
t,y,x
t,c,z,y,x
t,z,y,x,c
etc.
OME-Zarr and ITK axis access conventions are reversed. A 3D ITK image represents data with x,y,z axes, where "x" is the fastest moving and "z" is the slowest moving image axis. A 3D OME-Zarr store with axes "z", "y", "x" equivalently represents data where "z" is the slowest moving image axis and 'x" is the fastest moving image axis.
EDIT: Note that the order of spatial axes is not explicitly enforced. In theory images with out-of-order spatial axes can be read out of order. However, spatial metadata in the resulting ITK image may similarly be out of order.
Requested Behavior
Allow the user to specify the order in which OME-Zarr axes should permute to map to ITK axes. Handle spatial metadata (direction, origin, spacing) accordingly.
For instance:
or:
NamedAxes
should default to the expected ITK spatial axes, i.e. [x
,y
,z
].Enhancement 1
Allow the user to query what named axes are available and reconfigure accordingly.
Enhancement 2
Consider mapping arbitrary axes to ITK dimensions:
Metadata may get tricky under this general approach.
The text was updated successfully, but these errors were encountered: