Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add initial data in ome.zarr format #4

Merged
merged 5 commits into from
Nov 20, 2020
Merged

Conversation

constantinpape
Copy link
Contributor

@joshmoore @tischi
I have added the data in the format we have discussed now and also uploaded it to the embl s3 (it's 11.3 GB in total).

I added one more thing to the metadata for the multiscale datasets:
there is a field scales that contains a list of the absolute downscaling factors for the individual zarr arrays in the multi-scale pyramid. I think there is no canonical way to specify it in the ome.zarr multi-scale format yet, but we will definitely need it for bdv.

@tischi
Copy link
Owner

tischi commented Nov 20, 2020

I think there is no canonical way to specify it in the ome.zarr multi-scale format yet, but we will definitely need it for bdv.

Does that mean I have to wait for this to be fixed before I can start trying things out?

@constantinpape
Copy link
Contributor Author

Does that mean I have to wait for this to be fixed before I can start trying things out?

No, you can just read the scales field from the multiscale metadata and pass it to bdv.

@tischi tischi merged commit 45941b3 into tischi:main Nov 20, 2020
@joshmoore
Copy link
Collaborator

$ ome_zarr info https://s3.embl.de/i2k-2020/em-raw.ome.zarr/setup0/timepoint0
https://s3.embl.de/i2k-2020/em-raw.ome.zarr/setup0/timepoint0/ [zgroup]
 - metadata
   - Multiscales
 - data
   - (1, 1, 2854, 3240, 3438)
   - (1, 1, 1427, 1620, 1719)
   - (1, 1, 714, 810, 860)
   - (1, 1, 357, 405, 430)
   - (1, 1, 179, 203, 215)
   - (1, 1, 90, 102, 108)
   - (1, 1, 45, 51, 54)

https://hms-dbmi.github.io/vizarr?source=https%3A%2F%2Fs3.embl.de%2Fi2k-2020%2Fem-raw.ome.zarr%2Fsetup0%2Ftimepoint0 also resolves. Having issues with napari that I'll look into.

cc: @will-moore

@constantinpape
Copy link
Contributor Author

@joshmoore just checking:
the snippet you posted means that you can correctly parse the data, right?

@joshmoore
Copy link
Collaborator

Yes, and the Javascript library can read it. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants