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

Implement OME-NGFF v0.5 (Zarr v3) #257

Open
ziw-liu opened this issue Oct 16, 2024 · 0 comments
Open

Implement OME-NGFF v0.5 (Zarr v3) #257

ziw-liu opened this issue Oct 16, 2024 · 0 comments
Labels
enhancement New feature or request NGFF OME-NGFF (OME-Zarr format)

Comments

@ziw-liu
Copy link
Collaborator

ziw-liu commented Oct 16, 2024

RFC-2 for OME-NGFF has been adopted as part of the specification. This RFC bumps the NGFF version to 0.5, and uses Zarr v3 as the sole underlying storage format:

This RFC proposes to adopt version 3 of the Zarr format for OME-Zarr. Images that use the new version of OME-Zarr metadata MUST NOT use Zarr version 2 any more.

Zarr v3 is particularly beneficial for large bioimaging data since it supports sharding, allowing for fast parallel reads of slices across ND arrays without producing many (millions) of chunk files. Since managing chunk size to balance file count and read speed is a common trade-off iohub users have to make, iohub should implement OME-NGFF v0.5 and phase out writing (but keep supporting reading) of v0.4.

Currently, we cannot start the implementation because zarr-python, our primary Zarr backend, has not released a stable v3. However the v3 release should come soon.

cc @JoOkuma @ieivanov

@ziw-liu ziw-liu added enhancement New feature or request NGFF OME-NGFF (OME-Zarr format) labels Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request NGFF OME-NGFF (OME-Zarr format)
Projects
None yet
Development

No branches or pull requests

1 participant