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

expanded use of quality_control_report #1333

Closed
aclum opened this issue Nov 10, 2023 · 8 comments · Fixed by #1428
Closed

expanded use of quality_control_report #1333

aclum opened this issue Nov 10, 2023 · 8 comments · Fixed by #1428
Assignees

Comments

@aclum
Copy link
Contributor

aclum commented Nov 10, 2023

We have a need to indicate pass/fail for some of the WorkflowExecutionActivity subclasses. We already made quality_control_report but that currently only has Extraction as an applicable class. I would like to expand this slot to other PlannedProcess and WorkflowExecutionActivity classes.

I would also like to expand the slots on Class QualityControlReport. The current slots are 'status' and 'name'. JGI has a concept of failure_what failure_where, populated with controlled vocabulary.
ie
failure_where failure_what
Sequencing substandard run output
PMO assembly size below min threshold
multiple_failure_modes Sequencing_qPCR error;Sequencing_no data produced

We could model something similar where failure_where has a range of Activity or PlannedProcess classes (soon to be only PlannedProcess after the Dec schema refactor)

I'll open a draft pull request with some example data.

@aclum aclum linked a pull request Nov 10, 2023 that will close this issue
@aclum
Copy link
Contributor Author

aclum commented Nov 10, 2023

@ssarrafan
Copy link
Collaborator

@aclum appears to be active. I'll move to the next sprint but please remove if it's not being worked on.

@ssarrafan
Copy link
Collaborator

Last day of sprint. Removing from sprint, adding backlog label. Please update or add to next sprint if still active.

@ssarrafan ssarrafan added the backlog Issue not assigned to a sprint or not completed during a sprint. Needs to be reprioritized. label Dec 15, 2023
@aclum aclum removed the backlog Issue not assigned to a sprint or not completed during a sprint. Needs to be reprioritized. label Dec 20, 2023
@aclum
Copy link
Contributor Author

aclum commented Dec 20, 2023

This is in progress this week. Ive updated the modeling and need help from Brynn on the linkml rules, then the migration code needs to be written. This will likely span into January.

@aclum
Copy link
Contributor Author

aclum commented Dec 21, 2023

Brynn and Patrick confirmed there is a bug in the linkml rules, see linkml/linkml#1524. Patrick said he'd try and work on this on Friday. Will pause on this until January. Targeting a solution by the end of the first sprint in January so this can make it into the January end of month release.

@aclum
Copy link
Contributor Author

aclum commented Dec 21, 2023

To get the value_presence rules to work correctly I had to update linkml to 1.6.6 on Patrick's recommendation, then Patrick helped identify an issue where rules don't inherit to subclasses. Patrick will make a ticket for the linkml issue, this should be released in early January. Workaround would be to copy rules to each subclass but leaving for now since the next update to runtime would be end of January.

@aclum
Copy link
Contributor Author

aclum commented Jan 11, 2024

Patrick fixed the rules in linkml, i've updated the schema to use linkml 1.6.8 which made the linkml rules inheritance work as expected. Now the build passes.

@mbthornton-lbl we need a small bit of migration code to move quality_control_report.status to qc_status in the extraction_set collection. See example data in https://github.com/microbiomedata/nmdc-schema/blob/1427-try-to-fix-qc-report-pr-1334-in-new-branch/src/data/valid/Database-ReadQcAnalysisActivity-quality_fail.yaml. Please work off of branch 1427-try-to-fix-qc-report-pr-1334-in-new-branch which already as a draft PR #1428

@aclum
Copy link
Contributor Author

aclum commented Jan 12, 2024

Mark is reviewing the PR now. Hope to have this merged by EOD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
4 participants