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
This already works implicitly through adata subset in.h5ad -o out.zarr, which proves copy_store_contents handles every backend pair. A dedicated, discoverable command is what's missing.
Plan
Thin converter over storage.copy_store_contents.
Keep the source's chunking and compression by default; add --rechunk and --compressor for zarr targets.
Write consolidated metadata for zarr targets.
zarr v3 by default from an h5ad source (existing behaviour); follow the source format for zarr → zarr.
Refuse -o - and output == input.
Tests
All six pairings of h5ad / zarr2 / zarr3.
Open the result with anndata.read_zarr / read_h5ad under the integration marker.
Perf guard: one read per chunk, no full materialisation.
Implemented in #33, with one part deferred: --rechunk. Chunking is carried over from the source, and the copy already sizes its reads by bytes (32 MiB) rather than by source chunks, so a badly chunked source is read efficiently anyway. Rewriting the chunk layout is a separate option that can follow when someone needs it. --compression is in (none/gzip/lzf for h5ad, none/gzip/zstd/blosc for zarr), and consolidated metadata is written for zarr outputs.
Activity
adata convertto and from h5ad/zarr #20Claptar commentedon Oct 14, 2026
Implemented in #33, with one part deferred:
--rechunk. Chunking is carried over from the source, and the copy already sizes its reads by bytes (32 MiB) rather than by source chunks, so a badly chunked source is read efficiently anyway. Rewriting the chunk layout is a separate option that can follow when someone needs it.--compressionis in (none/gzip/lzffor h5ad,none/gzip/zstd/bloscfor zarr), and consolidated metadata is written for zarr outputs.