Skip to content
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

Zarr non-uniform axis values #1704

Open
manthey opened this issue Oct 25, 2024 · 0 comments
Open

Zarr non-uniform axis values #1704

manthey opened this issue Oct 25, 2024 · 0 comments
Assignees

Comments

@manthey
Copy link
Member

manthey commented Oct 25, 2024

When a zarr sink has non uniform axis values, I was expecting the top-level metadata for the axis values to still have one entry per axis position. That is, in the test file written here https://github.com/girder/large_image/blob/master/test/test_sink.py#L734, metadata['ValueT'] is {'values': [10.0, 10.0, 10.0, 20.0, 20.0, 20.0, 30.0, 30.0, 30.0, 10.01, 10.01, 10.01, 20.01, 20.01, 20.01, 30.01, 30.01, 30.01, 10.02, 10.02, 10.02, 20.02, 20.02, 20.02, 30.02, 30.02, 30.02, 10.03, 10.03, 10.03, 20.03, 20.03, 20.03, 30.03, 30.03, 30.03], 'uniform': False, 'units': 'millisecond', 'min': 10.0, 'max': 30.03, 'datatype': 'float64'}.

Individual frames have distinct T values, but I was expecting metadata['ValueT']['values'] to have 3 values which would be some value from where t==0, 1, 2 (e.g., [10.0, 20.00, 30.0] or [10.03, 20.03, 30.03]). Otherwise, to use the top level values we have to check if the uniform flag is set and then access the values different depending on it.

@annehaley annehaley self-assigned this Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants