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
hi @AlexHenderson, try passing write_empty_chunks=False as a keyword argument to zarr.save.
Your code example is actually creating two separate zarr arrays: the first array is created with the zarr.zeros function, and it uses in-memory storage, because that's the default storage backend if none is specified. zarr.save will create a second array on the file system using one of the file system-based storage backends. That second array is a structurally identical copy of the first array, but write_empty_chunks is a runtime detail, it's not part of the array metadata, so that doesn't get automatically copied over when you create the second array.
you can actually skip the invocation of zarr.save by passing a store keyword argument to zarr.zeros, e.g.
Hi,
The example here https://zarr.readthedocs.io/en/stable/tutorial.html#empty-chunks for not writing empty chunks works fine. However, if I use zarr.zeros rather than zarr.open, empty chunks are still written to file.
./testlocation
now contains 101 files although fill_type is 0 by default in zarr.zeros.zarr.version = 2.18.2
python 3.12.4
installation via poetry
Not sure if this is a bug, or I'm doing something wrong.
Thanks,
Alex
The text was updated successfully, but these errors were encountered: