-
Notifications
You must be signed in to change notification settings - Fork 2
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
bdv attribute-hierarchy proposal #8
base: main
Are you sure you want to change the base?
Conversation
The top level zarr group contains metadata that describes | ||
|
||
* What attributes are present in the zarr store | ||
* Whether attributes are stored in the directory hierarchy as a group or |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can someone explain this distinction?
|
||
|
||
```json | ||
"hierarchy" : { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if I understand this correctly, this is basically a novel JSON representation of a zarr hierarchy. why not use ZOM for this?
@d-v-b this document is not complete (writing things down now before I forget) and I expect many of your questions will be answered if you wait a little. but your questions will be helpful as i flesh this out |
``` | ||
|
||
The `tile` and `angle` attributes are stored as part of the zarr | ||
hierarchy, while channel and time dimensions are stored |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that the end of the sentence is missing here.
Notes from today's meeting with @krokicki and @StephanPreibisch