-
Notifications
You must be signed in to change notification settings - Fork 0
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
Allow customisable tag operations per MR model #354
Allow customisable tag operations per MR model #354
Conversation
Using 2 manufacturers for testing
…be-customised-per-mr-model
…be-customised-per-mr-model
So we can use it to access the tag operation files from other modules
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.
Thanks for working on this Milan, looks good - some suggestions here and there, happy to chat if morning me hasn't made much sense
projects/configs/uclh-nasogastric-tube-project-ngt-only-full-dataset.yaml
Outdated
Show resolved
Hide resolved
Co-authored-by: Stef Piatek <s.piatek@ucl.ac.uk>
Convert to list during config loading before pydantic validation. This avoids having to specify the base tag operations as list even if there is just a single file.
Keeping it simple
…be-customised-per-mr-model Merging in changes and resolving conflicts from #356
…be-customised-per-mr-model
Started adding unit test for |
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.
Looking good, thanks for this Milan. Mostly some file naming suggestions
Co-authored-by: Stef Piatek <s.piatek@ucl.ac.uk>
…icom-tag-operations-to-be-customised-per-mr-model
TagOperations
merge_tag_schemes
so it can handle manufacturer overridesFixes #292