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
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: