[User Story] Move QC validation to CG

ivadym commented 8 months ago

Need

As a Balsamic developer, I want to simplify the QC extraction and validation workflow, so that I can efficiently manage the increasing complexity of various workflow types, panels, and application tags.

Suggested approach

Move this logic to CG and start using the new status we have added to Trailblazer with RNAfusion (AnalysisStatus.QC).

Considered alternatives

Keep the QC checks in Balsamic while increasing the CLI complexity.

Deviation

No response

Risk assessment

[ ] Needed
[X] Not needed

Risk assessment link

No response

System requirements assessed

[X] Yes, I have reviewed the system requirements

Requirements affected by this story

Balsamic workflow should be refactored in CG

SOUPs

No response

Can be closed when

[ ] QC validation is removed from Balsamic
[ ] Balsamic QC validations is integrated into CG

Blockers

https://github.com/Clinical-Genomics/BALSAMIC/issues/1297

Anything else?

No response

pbiology commented 8 months ago

One thing to take into account here is Project Maven. The idea being that QC data should be collected from the pipelines and stored in a centralised database. From there CG would be then doing the QC checks. So it is quite similar as to what you are describing here.

ivadym commented 8 months ago

Today, we are generating the metrics_deliverables.yaml in Balsamic. The idea here is to move this logic to CG. It appears that Maven only requires the QC file, regardless of its source, so I don't think there is any overlap

Clinical-Genomics / BALSAMIC