-
Notifications
You must be signed in to change notification settings - Fork 4
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
WaveorderWriter
is not compatible with napari-ome-zarr
reader
#94
Comments
It's possible that |
Possibly introduced in: |
First line of the traceback indicates the problem:
While |
Related: ome/napari-ome-zarr#39 |
Now implemented as czbiohub-sf/iohub#31. We can keep this issue until iohub is released and used by recOrder, and |
|
I first noticed this issue during a
recOrder
session when I tried to drag and drop a zarr store saved by a recOrder acquisition into napari. The layers and shape populated correctly, but the actual pixel values were set to zero.Digging further, I've realized that this is a
WaveorderWriter
issue. Here's a minimal example:results in this traceback:
It seems related to our naming convention of
Row_0/Col_0/Pos_000
. Do we need to change this convention, or change the metadata so thatome-zarr
can read our zarrs?I think this is reasonably important because there are lots of cases when I'd like to use the
ome-zarr
reader to split zarr's channels into layers (it's native behaviour) instead of therecOrder-napari
reader that opens as a single array (also convenient in some cases). It also causes confusion because the reader seems to work but has zeros---did the reconstruction get saved? (It does)The text was updated successfully, but these errors were encountered: