IO and compression

Loading, decoding, encoding, saving and reopening acquisitions belong here. A fast decoder is not a complete load measurement: retain storage/cache state, original counts, transfer, first usable products and peak memory separately.

Start here

• HDF5 and QEM loading campaign: full-data CUDA, Python MPS and native Swift/Metal evidence, with unresolved cases retained.

• CUDA count codecs: compression speed and memory accounting.

• IO reports: dated measurements and rejected approaches.

• Reproduce loading checks: maintained runners and required private inputs.

Contracts and related guides

Read load/decode/bin for the operation, IO API for public calls, and methodology for cold, cached and prepared timing definitions. Conversion verification belongs to IO; shared cross-backend rules live in parity.