You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are gearing up to release a large timelapse dataset that has been converted to ome-zarr format. We saved the data with multiscale zoom levels but this reader constantly defaults to most compressed scale level. Can I hardwire napari reader to always use highest resolution level? What is the optimal way to fix this issue? The issue occurs every time I switch to volumetric display mode in napari. Specific error message is "Multiscale rendering is only supported in 2D. In 3D, only the lowest resolution scale is displayed".
The text was updated successfully, but these errors were encountered:
I built this ome zarr napari data loader which loads a csv of ome zarr filepaths via fire argument and uses bioio package for loading the volumetric image data. Bioio uses full resolution scale as default to load images if not specified. Maybe it would be good to make the default pixel scale a configurable param.
I'm wondering if this issue is, or will be, solved and released ? I've tested the napari-ome-zarr plugin to open a simple multiscale 2D image and, as described in the first message, only the lowest resolution level was read.
So far, I wasn't able to tell napari to read higher resolution levels nor to choose at the import which resolution level to get. Do you know if there is anything to do to read the others levels ? any config to check ?
We are gearing up to release a large timelapse dataset that has been converted to ome-zarr format. We saved the data with multiscale zoom levels but this reader constantly defaults to most compressed scale level. Can I hardwire napari reader to always use highest resolution level? What is the optimal way to fix this issue? The issue occurs every time I switch to volumetric display mode in napari. Specific error message is "Multiscale rendering is only supported in 2D. In 3D, only the lowest resolution scale is displayed".
The text was updated successfully, but these errors were encountered: