fix: 6D mode array path and store readiness check #26
Conversation
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
- 6D mode: array is directly at acquisition.zarr, not at /0 subpath - Add store readiness check for 6D regions mode (retry if zarr.json doesn't exist yet during early acquisition) Ported from Squid repo testing. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Follow-up fixes for #25 discovered during Squid integration testing:
array_path=""instead of"0"for 6D mode (array is at root, not/0subpath)Context
These issues were found when testing the zarr v3 implementation in the actual Squid repo. Unit tests passed but real integration testing revealed:
/0Test plan
simulate_zarr_acquisition.py --structure 6d_regions🤖 Generated with Claude Code