@@ -17,14 +17,14 @@ multi-resolution 3D stacks are organized in the following N5 hierarchy:
│ │ ├── s1
│ │ ┊
│ │
│ ├── timepoint00001
│ ├── timepoint1
│ ┊
│
├── setup01
├── setup1
┊
```
Each 3D stack is stored as a dataset with path formatted as `/setup%02d/timepoint%05d/s%d`.
Each 3D stack is stored as a dataset with path formatted as `/setup%d/timepoint%d/s%d`.
Here, `setup` number is flattened index of channel, angle, tile, illumination, etc.,
`timepoint` is the index of the time point, and `s` is the scale level of the multi-resolution pyramid.
...
...
@@ -38,7 +38,7 @@ that specify downsampling scheme and datatype, which are the same for all timepo
`downsamplingFactors` specifies power-of-two downscaling factors for each scale level (with respect to full resolution `s0`, which always has `[1,1,1]`).
`dataType` is one of {uint8, uint16, uint32, uint64, int8, int16, int32, int64, float32, float64}.
> TODO: Additional metadata (for example identifying `setup03` as channel 3, tile 124, etc.) could be replicated from the XML.
> TODO: Additional metadata (for example identifying `setup3` as channel 3, tile 124, etc.) could be replicated from the XML.
The idea would be that parts of a dataset can be used independent of BDV, without the XML.