-
Notifications
You must be signed in to change notification settings - Fork 27
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
Update zarr 3 codec pipeline workflow #423
base: main
Are you sure you want to change the base?
Conversation
serializer = v3_codecs_to_serializer(codecs) | ||
return ZarrV3Codecs( | ||
filters=filters, compressors=compressors, serializer=serializer | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm curious if we replaced the ZArray
class with zarr-python's ArrayV3Metadata
would there be comparable functionality to parse out the filters, compressors and serializer, so those could be passed to zarr-python's create_array
(same args as require_array
)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was going to do this with init_array
but it requires a store path which i didnt want to deal with atm, but might be the right approach
We need to handle codecs so that they match the zarr 3
create_array
apidocs/releases.rst
api.rst