You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a few significant changes in this planned release worth highlighting for end users. Along these lines it would be useful to have a blogpost to provide a bit more details on what was implemented and any behavior changes users should expect. Here are a few big things that stick out to me (though feel free to call out others). Would suggest that we write maybe a short blurb (maybe a paragraph) on each of these and then combine them together. Thoughts? 🙂
Zarr arrays now support NumPy-style fancy indexing with arrays of integer coordinates. This is equivalent to using zarr.Array.vindex. Mixing slices and integer arrays is not supported.
For empty chunks:
One of the advantages of the zarr format is that it is sparse, which means that chunks with no data (more precisely, with data equal to the fill value, which is usually 0) don't need to be written to disk at all. They will simply be assumed to be empty at read time. However, until this release, the zarr library would write these empty chunks to disk anyway. This changes in this version: a small performance penalty at write time leads to significant speedups at read time and in filesystem operations in the case of sparse arrays. To revert to the old behavior, pass the argument write_empty_chunks=True to the array creation function.
Activity
jni commentedon Jan 27, 2022
Ok, suggestions:
For fancy indexing:
For empty chunks:
Happy to edit as needed! 😊
jakirkham commentedon Apr 12, 2022
This was done in PR ( zarr-developers/blog#6 ). Closing...