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.

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

3.9. "well" metadata #38

Open
dstansby opened this issue Nov 22, 2024 · 1 comment
Open

3.9. "well" metadata #38

dstansby opened this issue Nov 22, 2024 · 1 comment

Comments

@dstansby
Copy link
Contributor

For high-content screening datasets, the metadata about all fields of views under a given well can be found under the "well" key in the attributes of the well group.

The well dictionary MUST contain an images key whose value MUST be a list of JSON objects specifying all fields of views for a given well. Each image object MUST contain a path key whose value MUST be a string specifying the path to the field of view. The path MUST contain only alphanumeric characters, MUST be case-sensitive, and MUST NOT be a duplicate of any other path in the images list. If multiple acquisitions were performed in the plate, it MUST contain an acquisition key whose value MUST be an integer identifying the acquisition which MUST match one of the acquisition JSON objects defined in the plate metadata (see #plate-md).

The well dictionary SHOULD contain a version key whose value MUST be a string specifying the version of the well specification.

For example the following JSON object defines a well with four fields of view. The first two fields of view were part of the first acquisition while the last two fields of view were part of the second acquisition.

https://ngff.openmicroscopy.org/0.4/index.html#plate-md

@dstansby
Copy link
Contributor Author

it MUST contain an acquisition key whose value MUST be an integer identifying the acquisition which MUST match one of the acquisition JSON objects defined in the plate metadata (see #plate-md).

This will need implementing in whichever parent structure the well metdata sits under

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant