Jeremy Maitin-Shepard
Jeremy Maitin-Shepard
One minor drawback I see with the inner-to-outer order used by fsspec is that it would be challenging to support completion since the user would need to type the parts...
For HTTP by itself there would be no reason for a `#part` suffix --- the `#fragment` part isn't sent to the server --- it is just for interpretation by the...
Regarding GCS use of "#version" syntax, I see that is documented for the gsutil tool, though I'm struggling to find any documentation of that for the gcsfs fsspec driver. That...
I'm not talking specifically about HTTP, but I am thinking in terms of how web browsers behave, since they are the most prominent user of "URL" syntax. There is RFC...
> I was assuming that this URL syntax would only work for V3, in which every array or group will have a `zarr.json`. Addressing V2 in a backwards-compatible way is...
Thanks for this proposal. It seems like it may make sense to specify the stride in units of elements rather than chunks. Then this would more generally also cover downsampling.
@hailiangzhang As I mentioned at the meeting today, it would be very helpful if you can provide some mathematical formulas or pseudocode that describes which cumulative sums you are storing....
> Meanwhile, just to make sure we are on the same page, in this formula you listed above `Ai(i, j, k) = A(i * ci, j, k)`, is `i`, `j`,...
Independent of these details, I think it is clear now that this exists as an additional layer entirely on top of zarr itself. I'm still interested in learning more about...
A more precise specification of this proposal would definitely help, as the current proposal does not seem to indicate precisely what calculated values are stored. To me, a zarr extension...