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
* chore(deps): bump zarr to 3.0.0rc1
* fmt
* (feat): python fallack
* (fix): dtypes
* (fix): `object` dtypes + `v2` tests
* (fix): `object` dtypes + `v2` tests
* (fix): `object` dtypes + `v2` tests
* (fix): `object` dtypes in rust
* (fix): blosc support
* (refactor): handle `None` fill-value more gracefully
* fix: V2 codec pipeline creation
* fix: zfpy/pcodec metadata handling
* (fix): fall back for unsupported codecs
* (fix): our decode codec pipeline does not support vlen
* (fix): string dtype test to match zarr-python
* (chore): add note
* (fix): ruff
* (fix): rustfmt
* (fix): `pyi`
* (fix): try removing zarr main branch dep
* fix: use upstream implicit fill values
* fix: use upstream metadata handling
There is a lot of additional logic already taken care of by `zarrs`, like handling multiple versions of codec metadata.
* fix: cleanup fill value handling for string dtype
* Revert "fix: cleanup fill value handling for string dtype"
This reverts commit 6ff6c2b.
* fix: cleanup fill value handling for string dtype
* fix: fmt and clippy warnings
* fix: zarr-python 0 fill value handling
---------
Co-authored-by: Lachlan Deakin <ljdgit@gmail.com>
Copy file name to clipboardExpand all lines: README.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ You can then use your `zarr` as normal (with some caveats)!
21
21
22
22
## API
23
23
24
-
We export a `ZarrsCodecPipeline` class so that `zarr-python` can use the class but it is not meant to be instantiated and we do not guarantee the stability of its API beyond what is required so that `zarr-python` can use it. Therefore, it is not documented here. We also export two errors, `DiscontiguousArrayError` and `CollapsedDimensionError` that can be thrown in the process of converting to indexers that `zarrs` can understand (see below for more details).
24
+
We export a `ZarrsCodecPipeline` class so that `zarr-python` can use the class but it is not meant to be instantiated and we do not guarantee the stability of its API beyond what is required so that `zarr-python` can use it. Therefore, it is not documented here.
25
25
26
26
At the moment, we only support a subset of the `zarr-python` stores:
27
27
@@ -86,7 +86,7 @@ Chunk concurrency is typically favored because:
86
86
87
87
## Supported Indexing Methods
88
88
89
-
We **do not** officially support the following indexing methods. Some of these methods may error out, others may not:
89
+
The following methods will trigger use with the old zarr-python pipeline:
90
90
91
91
1. Any `oindex` or `vindex` integer `np.ndarray` indexing with dimensionality >=3 i.e.,
92
92
@@ -116,6 +116,9 @@ We **do not** officially support the following indexing methods. Some of these
116
116
arr[0:10, ..., 0:5]
117
117
```
118
118
119
-
Otherwise, we believe that we support your indexing case: slices, ints, and all integer `np.ndarray` indices in 2D for reading, contiguous integer `np.ndarray` indices along one axis for writing etc. Please file an issue if you believe we have more holes in our coverage than we are aware of or you wish to contribute! For example, we have an [issue in zarrs for integer-array indexing](https://github.com/LDeakin/zarrs/issues/52) that would unblock a lot of these issues!
120
119
121
-
That being said, using non-contiguous integer `np.ndarray` indexing for reads may not be as fast as expected given the performance of other supported methods. Until `zarrs` supports integer indexing, only fetching chunks is done in `rust` while indexing then occurs in `python`.
120
+
Furthermore, using anything except contiguous (i.e., slices or consecutive integer) `np.ndarray` for numeric data will fall back to the default `zarr-python` implementation.
121
+
122
+
Please file an issue if you believe we have more holes in our coverage than we are aware of or you wish to contribute! For example, we have an [issue in zarrs for integer-array indexing](https://github.com/LDeakin/zarrs/issues/52) that would unblock a lot the use of the rust pipeline for that use-case (very useful for mini-batch training perhaps!).
123
+
124
+
Further, any codecs not supported by `zarrs` will also automatically fall back to the python implementation.
0 commit comments