@@ -8,7 +8,7 @@ Introduction
88
99The bfio package is designed to make it easy to process arbitrarily sized images
1010in a fast, scalable way. The two core classes, :doc: `/Reference/BioReader ` and
11- :doc: `/Reference/BioWriter `, can use one of three different backends depending
11+ :doc: `/Reference/BioWriter `, can use one of five different backends depending
1212on the file type that will be read. Usually, the proper backend will be selected
1313when opening a file. For cases where bfio fails to select the proper backend, the
1414``backend `` parameter can be passed to the constructor. The following backends
@@ -20,10 +20,14 @@ are available in ``bfio``.
20202. ``backend="bioformats" `` can be used to read any
2121 `any format supported by Bio-Formats <https://docs.openmicroscopy.org/bio-formats/8.0.1/supported-formats.html >`_.
2222 The BioWriter with java backend will only save images as OME tiled tiff.
23- 3. ``backend="zarr" `` can be used to read/write a subset of Zarr files following
23+ 3. ``backend="zarr" `` can be used to read/write a subset of Zarr v2 files following
2424 the `OME Zarr spec <https://ngff.openmicroscopy.org/latest/ >`_.
25+ 4. ``backend="zarr3" `` can be used to read/write Zarr v3 files following
26+ the `OME Zarr spec <https://ngff.openmicroscopy.org/latest/ >`_.
27+ 5. ``backend="tensorstore" `` provides optimized reading/writing for both OME Tiff
28+ and OME Zarr (v2 and v3) files with enhanced performance.
2529
26- The advantage to using the ``python `` and ``zarr `` backends are speed and
30+ The advantage to using the ``python ``, `` zarr ``, `` zarr3 ``, and ``tensorstore `` backends are speed and
2731scalability at the expense of a rigid file structure, while the ``bioformats `` backend
2832provides broad access to a wide array of file types but is considerably slower.
2933
0 commit comments