mathworks / mathworks/MATLAB-support-for-Zarr-files
Should not allow a path to simultaneously be a Zarr array and a Zarr group?
Nobody has claimed this yet.
- Dominant language
- MATLAB
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Looks like currently something like this is allowed:
>> zarrcreate("myzarr.zarr/A/B/C", [100,100])
>> zarrcreate("myzarr.zarr/A/B/C/D", [100,100])
Here path "myzarr.zarr/A/B/C" should represent a Zarr array (contain .zarray file). From my understanding, writing a Zarr array in "myzarr.zarr/A/B/C/D" should not be allowed (it would be treating "myzarr.zarr/A/B/C" as a group instead of an array)?
Similarly if "myzarr.zarr/A/B/C" is a Zarr group (contains .zgroup file), then I think the following should not be allowed:
>> zarrcreate("myzarr.zarr/A/B/C", [100,100])
as it would be treating "myzarr.zarr/A/B/C" path as both a Zarr array and a Zarr group.
Not 100% sure if my understanding of the Zarr spec is correct though...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the zarrcreate entry point and compare the two nested-path examples against the linked Zarr v2 specification. Trace how existing .zarray and .zgroup markers are handled, then add coverage showing that a path cannot represent both an array and a group or contain an array below an array. Done means both conflicting operations are rejected consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- matlab
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100