Alistair Miles

@lindstro thanks for the information, very helpful. Apologies if I have not fully understood the details in your comment, but you are right to say that zarr partitions an array...

Many thanks @lindstro, very nice clarification. > Of course, one could use zfp as a black box codec with zarr to (de)compress large chunks, but my question had to do...

Thanks @lindstro, very interesting. FWIW Zarr was designed primarily as a storage partner to the Dask array module, which implements a subset of the Numpy interface but as chunked parallel...

Sounds cool! On Wed, 16 Jan 2019 at 01:57, jakirkham wrote: > We could look at Netlify . This not only would > allow building the docs, but previewing the...

Hi folks, took a brief look into this, here's the options (I think)... The current LZ4 codec in numcodecs does [the simplest possible thing](https://github.com/zarr-developers/numcodecs/blob/7c07db404ecdf780cc0ac37e0b2d04660ef852fc/numcodecs/lz4.pyx#L53), which is to add a 4...

Yes SGTM. Can you say which are the right switches? I can poke around in the settings, but not always obvious. On Fri, 30 Nov 2018 at 01:29, jakirkham wrote:...

Awesome, thanks @jakirkham.

Hi @sofroniewn, I haven't thought about this deeply but I imagine the codec could be modified to be aware of the expected number of dimensions in each array, and then...

> You may find it easier to flatten the arrays and keep track of array shapes separately and reshape on reading :-) Btw don't mean this to sound discouraging, happy...

On Fri, 6 Sep 2019 at 15:49, Nicholas Sofroniew wrote: > @alimanfoo thanks for thinking about this. > If you could do it in the codec with guaranteed 2D arrays...