Pull Request

Description

This adds optionally opening zarrs with Tensorstore, which can be up to 10-40x faster than opening Zarrs encoded with ocf_blosc2. This comes with a size penality, in that Zarrs are then around 28% larger, but since speed of reading Zarrs is a large bottleneck for us, probably worth the tradeoff. In either case, the tensorstore backend can be ignored, as Tensorstore only supports limited compression algorithms.

Fixes #224
Fixes #198

How Has This Been Tested?

Unit tests

• Yes

If your changes affect data processing, have you plotted any changes? i.e. have you done a quick sanity check?

• Yes

Checklist:

• My code follows OCF's coding style guidelines
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I have checked my code and corrected any misspellings