Closed will-moore closed 1 month ago
"endian"
is only required for multi-byte data types where endianness is applicable, so vizarr
is non-conformant in this case.
https://zarr-specs.readthedocs.io/en/latest/v3/codecs/bytes/v1.0.html#configuration-parameters
Thanks @LDeakin.
Hi @manzt - does this look right to you? Potential issue with zarrita?
I tried to create a sample image to illustrate the issue: I'm not getting the expected error in vizarr but the image still fails to display and applying the change to zarr.json
above seems to fix it (becomes viewable)
https://deploy-preview-36--ome-ngff-validator.netlify.app/?source=https://minio-dev.openmicroscopy.org/idr/v0.5/astronaut.zarr
Thanks
Yeah, this is a bug in zarrita.
The issue arises not because endian
is missing, but rather because the configuration
object is omitted entirely.
Fix now available, just need to bump in Vizarr.
Thanks @manzt - Sample image above is now displaying in vizarr at https://hms-dbmi.github.io/vizarr/?source=https://minio-dev.openmicroscopy.org/idr/v0.5/astronaut.zarr Closing...
The
zarr.json
I get from runningome2024-ngff-challenge
is missing aconfiguration
section from thebytes
codec within the sharding codec, and this prevents it from being viewed in vizarr, giving errors:I noticed that this IS found in the sample at https://deploy-preview-36--ome-ngff-validator.netlify.app/?source=https://uk1s3.embassy.ebi.ac.uk/idr/share/ome2024-ngff-challenge/0.0.5/6001240.zarr
It's also found in the spec at https://github.com/zarr-developers/zarr-specs/blob/main/docs/v3/codecs/sharding-indexed/v1.0.rst#configuration-parameters
Manually adding this in as follows allows the data to be viewed in vizarr: