Closed will-moore closed 3 years ago
Export was successful:
cat 6001240.zarr/.zattrs
{
"_creator": {
"name": "omero-zarr",
"version": "0.0.11.dev22+g541c88e"
},
"multiscales": [
{
"axes": [
"c",
"z",
"y",
"x"
],
"datasets": [
...
and for the 0-th resolution:
"shape": [
2,
236,
275,
271
],
but still considering how to test reading while blocked on https://github.com/ome/napari-ome-zarr/issues/6
cc: @constantinpape
Using https://github.com/hms-dbmi/vizarr/pull/104 if you can serve you data in a CORS-friendly manner then you can view at: https://deploy-preview-104--vizarr.netlify.app/?source=http://localhost:8000/path/to/image.zarr
For serving CORS, I use this little python script:
With https://github.com/ome/napari-ome-zarr/pull/9 and fix described in https://github.com/ome/ome-zarr-py/pull/89#issuecomment-879789276
I can open data exported with this PR in napari
Data exported today, using this branch:
Thanks, @will-moore !
To test, try exporting 2D, 2D, 4D and 5D images.
Z, C & T dimensions where size=1 should be ignored, and not included in the exported v0.3 OME_NGFF. Also the
.zattrs
multiscales
should list the used dimensions asaxes
, e.g:"axes": ["t", "c", "y", "x"]