-
Notifications
You must be signed in to change notification settings - Fork 7
omero fields optional #87
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
base: main
Are you sure you want to change the base?
Conversation
ported from ome/ngff#297
Automated Review URLs |
| - `min` (float) Should correspond to the minimum pixel intensity for that channel. | ||
| - `max` (float) Should correspond to the maximum pixel intensity for that channel. |
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.
| - `min` (float) Should correspond to the minimum pixel intensity for that channel. | |
| - `max` (float) Should correspond to the maximum pixel intensity for that channel. | |
| - `min` (float) Default setting for lower bound for values of `start` field. | |
| - `max` (float) Default setting for upper bound for values of `end` field. |
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.
I used "should" here because I want it to be clear that this is not enforced: The file isn't invalid if you don't quite get this correct. E.g. if you use a down-sampled resolution, or just the middle Z-section to calculate the min/max then it may not actually be the "Maximum pixel intensity for that channel"
Co-authored-by: Johannes Soltwedel <38459088+jo-mueller@users.noreply.github.com>
Co-authored-by: Johannes Soltwedel <38459088+jo-mueller@users.noreply.github.com>
Fixes ome/ngff#192
ported from ome/ngff#297