Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add axes field to multiscale metadata #46

Merged
merged 11 commits into from
Aug 24, 2021
Merged

Add axes field to multiscale metadata #46

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
bba6940
Update latest to 0.2
constantinpape Apr 26, 2021
6b8a868
Add axes field to multiscales metadata
constantinpape Apr 26, 2021
a345247
Merge remote-tracking branch 'ome/main' into spec-v03
constantinpape Apr 26, 2021
9c57396
Fix version numbers
constantinpape Apr 26, 2021
e60ec27
Allow for less than 5d
constantinpape May 5, 2021
cf76570
Add _ARRAY_DIMENSIONS requirement for compatibility with xarray
constantinpape May 17, 2021
af7b947
Minor formulation tweak
constantinpape May 17, 2021
c46d9d5
Store the current latest as 0.3
joshmoore Aug 24, 2021
47fa3dc
Revert some latest changes and add changelog
joshmoore Aug 24, 2021
3e9908c
Merge branch 'main' into spec-v03
joshmoore Aug 24, 2021
a981f98
Add Constantin as editor
joshmoore Aug 24, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion latest/index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,8 @@ multiple levels of resolutions and optionally associated labels.
│
├── .zgroup # Each image is a Zarr group, or a folder, of other groups and arrays.
├── .zattrs # Group level attributes are stored in the .zattrs file and include
│ # "multiscales" and "omero" below)
│ # "multiscales" and "omero" (see below). In addition, the group level attributes
│ # must also contain "_ARRAY_DIMENSIONS" if this group directly contains multi-scale arrays.
│
├── 0 # Each multiscale level is stored as a separate Zarr array,
│ ... # which is a folder containing chunk files which compose the array.
Expand Down Expand Up @@ -218,6 +219,8 @@ to the current zarr group. The "path"s MUST be ordered from largest (i.e. highes
It MUST contain the field "axes", which is a list of dimension names of the axes.
The values MUST be unique and one of `{"t", "c", "z", "y", "x"}`.
The number of values MUST be the same as the number of dimensions of the arrays corresponding to this image.
In addition, the "axes" values MUST be repeated in the field "_ARRAY_DIMENSIONS" of the top-level group for the arrays containing
the multiscale data. This ensures compatibility with the [xarray zarr encoding](http://xarray.pydata.org/en/stable/internals/zarr-encoding-spec.html#zarr-encoding).
constantinpape marked this conversation as resolved.
Show resolved Hide resolved

It SHOULD contain the field "name".

Expand Down