Open sbesson opened 2 years ago
I agree: chunks
should be deprecated in favor of storage_options
.
FYI - thoughts on moving storage_options
to parse_url()
instead of write_multiscale()
- which would mean that we keep chunks
keyword - see #282
See conversation at https://github.com/ome/ome-zarr-py/pull/161#discussion_r800575583
The
storage_options
keyword introduced in 0.3.0 should support setting thechunks
to the Zarr dataset. This option also gives the extra flexibility of being able to set different chunk sizes for each resolution. The explicitchunks
keyword could be deprecated in an upcoming0.x.0
release of theome-zarr
library.