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
Originally posted by ilan-gold November 12, 2024
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 a combination of "advanced indexing" or "vectorized indexing" along axes 0, 1 and basic indexing on axis 2. Looking at the code this is not supported (yet).
@dcherian So I guess I don't really mind one way or another whether it's supported, it's more that I would like to know what is supported and is not somehow. Is there some document somewhere or the like? I would expect "we replicate numpy indexing" to be the answer but it apparently is not.
Discussed in #2485
Originally posted by ilan-gold November 12, 2024
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?The text was updated successfully, but these errors were encountered: