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

Fix units -> unit #131

Merged
merged 2 commits into from
Nov 3, 2022
Merged

Fix units -> unit #131

merged 2 commits into from
Nov 3, 2022

Conversation

will-moore
Copy link
Member

See ome/ngff#157

This is a corresponding fix to update all axes "units" to "unit" (as in the Spec).

Copy link
Member

@sbesson sbesson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds like we should schedule an immediate patch release to ensure the unit metadata is written correctly. Is https://github.com/ome/ome-zarr-py/releases/tag/v0.6.1 used anywhere as we probably want to avoid creating mixed data types as well?

@joshmoore
Copy link
Member

👍 for getting this out ASAP.

@will-moore
Copy link
Member Author

@sbesson I checked all the samples at https://idr.github.io/ome-ngff-samples/ for mixed dtypes but didn't see any.
I think scaler.local_mean() isn't used by omero-cli-zarr as it uses from skimage.transform.resize directly.

@will-moore will-moore merged commit de7a530 into ome:master Nov 3, 2022
@will-moore
Copy link
Member Author

Released as omero-cli-zarr 0.5.1

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

Successfully merging this pull request may close these issues.

3 participants