feat: Add zarr v3 support to tensorstore backend#127
Merged
sameeul merged 3 commits intoPolusAI:masterfrom Feb 17, 2026
Merged
Conversation
Implement automatic zarr format detection (v2 vs v3) in the tensorstore backend. The backend now correctly handles both zarr v2 and v3 stores by: - Detecting zarr format using detect_zarr_format() utility - Setting appropriate FileType (OmeZarrV2 or OmeZarrV3) for TSReader/TSWriter - Using format-specific child enumeration: * v2: filesystem fallback (_list_zarr_children) for reliability * v3: native zarr-python array_keys()/group_keys() methods - Parsing metadata from both v2 (attrs["multiscales"]) and v3 (attrs["ome"]["multiscales"]) locations per NGFF 0.5 spec Writer maintains backward compatibility by defaulting to v2 format. Added comprehensive test coverage: - test_read_zarr_v3: Basic v3 zarr reading with tensorstore backend - test_read_zarr_v3_multi_resolution: Multi-resolution v3 zarr support - Added ExpD_chicken_embryo_MIP.ome.zarr (v3) to test dataset Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implement automatic zarr format detection (v2 vs v3) in the tensorstore backend. The backend now correctly handles both zarr v2 and v3 stores by:
Writer maintains backward compatibility by defaulting to v2 format.
Added comprehensive test coverage: