More DAQ metadata fields and new Image Process metadata field.#67
Open
YooSunYoung wants to merge 6 commits into
Open
More DAQ metadata fields and new Image Process metadata field.#67YooSunYoung wants to merge 6 commits into
YooSunYoung wants to merge 6 commits into
Conversation
This was referenced Jul 17, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #55
Implemented
Normalized/ob/sample
This is implemented as a
result_typeinImageProcessMetadata.Processing steps [list of strings]
This is implemented as a
processing_stepsinImageProcessMetadata.PI name [dict: name, email and orcid]
Local contact [dict: name, email and orcid]
Team members [list of dicts: name, email and orcid]
Experiment number
This is implemented as a experiment identifier
Not Implemented
I added
descriptionfield in the ExperimentIdentifier schema. Users can encode which run type it was in that description.But keeping track of parents/children relation between dataset should be done by the cataloguing system.
Because it is not guaranteed that the user of the data has access to the parents/related files locally but it is always guaranteed that they have access to the related dataset if they are on the catalouging system.
The file should carry the minimum indicator for quick checking and shouldn't be considered the source of truth.
This can be encoded as a detector type, no?
I'm not sure if this is useful metadata. If it's physically meaningful to the image, it can be included in the coordinate.
Same as the sample/motor position