Using the cyx.ome.zarr OME-NGFF sample from https://github.com/ome/ome-ngff-prototypes, the image is incorrectly detected as multi-Z
Series count = 1
Series #0 :
Resolutions = 3
sizeX[0] = 1024
sizeX[1] = 512
sizeX[2] = 256
Image count = 4
RGB = false (1)
Interleaved = false
Indexed = false (false color)
Width = 1024
Height = 930
SizeZ = 4
SizeT = 1
SizeC = 1
Tile size = 1 x 256
Thumbnail size = 128 x 116
Endianness = intel (little)
Dimension order = XYCZT (uncertain)
Pixel type = uint16
Valid bits per pixel = 16
Metadata complete = false
Thumbnail series = false
-----
Plane #0 <=> Z 0, C 0, T 0
Plane #2 <=> Z 2, C 0, T 0
Plane #3 <=> Z 3, C 0, T 0
while the data is expected to be multi-channel
{
"multiscales": [
{
"axes": [
{
"name": "c",
"type": "channel"
},
{
"name": "y",
"type": "space"
},
{
"name": "x",
"type": "space"
}
],
"datasets": [
...
Additionally the optimal tile size is set as 1 x 256 as opposed to 256 x 256 as defined in the .zarray
% less ~/Desktop/embl/cyx.ome.zarr/s0/.zarray
{
"chunks": [
1,
256,
256
],
This becomes even more critical when using data of higher dimensionality e.g. the tile size for tcyx.ome.zarr from the same series of samples is set to Tile size = 1 x 1. This causes severe performance issues in clients using the optimal tile size like the OMERO min/max calculation process during the import phase.
Using the
cyx.ome.zarrOME-NGFF sample from https://github.com/ome/ome-ngff-prototypes, the image is incorrectly detected as multi-Zwhile the data is expected to be multi-channel
{ "multiscales": [ { "axes": [ { "name": "c", "type": "channel" }, { "name": "y", "type": "space" }, { "name": "x", "type": "space" } ], "datasets": [ ...Additionally the optimal tile size is set as
1 x 256as opposed to 256 x 256 as defined in the.zarrayThis becomes even more critical when using data of higher dimensionality e.g. the tile size for
tcyx.ome.zarrfrom the same series of samples is set toTile size = 1 x 1. This causes severe performance issues in clients using the optimal tile size like the OMERO min/max calculation process during the import phase.