-
Notifications
You must be signed in to change notification settings - Fork 41
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
Z-downsampling metadata #25
Comments
Just out of curiosity @will-moore @joshmoore, what are the "lightsheet changes?" |
Hi @ilan-gold. The next body of work is focused around having better support for large 3D volumes. We'll likely use the opportunity to make the first breaking changes to the metadata (0.1 --> 0.2) so if there's something that's needed (e.g. the way to detect the z-downsampled multiscale zgroup as you were asking in hms-dbmi/vizarr#71 (comment)) then it would be good to roll them into the "lightsheet changes". |
Gotcha @joshmoore, I know @will-moore and I talked on image.sc about scaling as well, derived from the reported physical size, so that would be great too in the next change. We are very interested in this 3D stuff as well so I'll keep my ear to the ground. |
The downsamplling is now specified using |
It's possible that we may generate multiple
"datasets"
for a given OME-Zarr Image, e.g. with and without down-sampling in Z. It could be useful to have a way to identify these.See hms-dbmi/vizarr#71 (comment)
"will there be any way to distinguish between the downsampled-in-z version of a dataset and the non-downsampled version? The shape of the zarr array, I presume? But will there be any metadata about it? Just curious........."
@joshmoore "One thing we could do at the moment (pre-lightsheet changes) would be to have a naming convention for the multiscales themselves. Another option would be to use the metadata for the method of the downsampling, but we’d need something well-defined to say “in-z".
The text was updated successfully, but these errors were encountered: