Replies: 1 comment 1 reply
-
A lot of the indexing code in 3.x is derived from indexing code in 2.x, so if something worked in zarr-python 2 it should work in 3. I would guess that what you are seeing is very likely a bug, and I don't think we have good docs for indexing in 3.x, sorry about that! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am not entirely clear about what is supported and what isn't in zarr indexing, especially in v3. I understand https://zarr.readthedocs.io/en/stable/tutorial.html#advanced-indexing as "the API is different because we explicitly implement oindex but otherwise the behavior should be the same as numpy."
In other words, it seems "coordinate indexing" ->
vindex
(or just normal bracket shortcutting on the array directly) and "orthogonal indexing" ->oindex
.But other than these things, I'm not sure I understand what is and isn't supported. For example
This is on zarr v3
3.0.0b1
. Is this a bug? Is there any good documentation on this?Beta Was this translation helpful? Give feedback.
All reactions