Trevor Manz

@normanrz I removed the zarrita -> zarr.js adapter stuff and now we have a pure zarrita pixel source for viv. This should allow better composition with the rest of zarrita...

I'm running into some issue with the plates but once I get that resolved I'll merged and make a release (v0.4).

Ok,then similarly i'll keep vizarr in a prerelease state.

So currently https://hms-dbmi.github.io/vizarr points to whatever is on `main` (so that should be fine). We then cut versions under https://hms-dbmi.github.io/vizarr/v0.1, etc. I'm very open to other ideas for versioning /...

Hi there. I worked with @lauradmartens on this the other day and we came up with a proof of concept https://github.com/kaizhang/SnapATAC2/compare/main...manzt:SnapATAC2:split-reads This seems to work well for our use case:...

> @trevormanz has also been interested in the idea of a server-backed zarr store. Yes! Thanks for tagging me. I made [`simple-zarr-server`](https://github.com/manzt/simple-zarr-server) to expose any Python Zarr store (MutableMapping) over...

> Aside: Do you use websockets? I see it in the CLI help string but could not immediately find it in the source. We should chat. It doesn't, oops! I...

I think it makes sense to add filters to `numcodecs.js` (that's where they live for `zarr-python`, and they implement the codecs interface). However, currently zarr.js doesn't support using filters. That...

This is a great question, and the short answer is I'm not sure. I created this library for https://github.com/gzuidhof/zarr.js/ and wanted pure ESM implementations of different codecs. Originally I'd seen...

Hmm, I believe missing chunks should raise a `KeyError`, and then the client library is responsible for creating the filled chunk (rather than the store creating an empty chunk on-demand).