-
-
Notifications
You must be signed in to change notification settings - Fork 329
Confused about Zarr2 to Zarr3 conversion #3024
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
Comments
hi @Fafa87, sorry to hear the confusion here and thanks for writing this up as an issue. What you initially tried (using |
Oh, then let me add more info about the datasets: Zarr: data (original Zarr2):
After conversion:
Running sum using dask breaks:
--> |
I just wanted to leave a trace about my experience with Zarr2 to Zarr3 conversion (including shards).
Basically I wanted to check the new Zarr version - all for the sharding feature.
The idea was just to grab some Zarr2 array that I have and convert it to Zarr3 with x2 / x4 sharding to test the performance.
Well, it took a while because first thing that I did was just to:
It worked and I got working Zarr3. So easy.
Then I thought there is a sharding parameter there so I will just fill it (with x4 shards) in and get sharded Zarr3:
It worked not - although it looked like it did. When I showed info_complete() I got information that compression factor got from 1.4 to 5 and it was susicious. It turned out that most of the files are just empty. Then I wanted to compute sum() of all pixels and it failed with some error about encoding / compression - so I went into that dead-end.
Finally I got to the point that the correct (is it?) the way to do it is to create a new empty array and copy the data:
Is there a guideline for people of how to convert their Zarr2 datasets to new Zarr3 with sharding?
For me I did not find anything on that - the only thing is the legacy (?): https://github.com/ome/ome2024-ngff-challenge
The text was updated successfully, but these errors were encountered: