-
Notifications
You must be signed in to change notification settings - Fork 16
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
feat: update multiqc to 1.22.3 #1441
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #1441 +/- ##
========================================
Coverage 99.48% 99.48%
========================================
Files 40 40
Lines 1932 1933 +1
========================================
+ Hits 1922 1923 +1
Misses 10 10
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Fantastic work ⭐
Co-authored-by: Vadym <vadym.ivanchuk@scilifelab.se>
…C into update_multiqc
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.
💯
Quality Gate passedIssues Measures |
Thanks a lot for the review @ivadym ! ❤️ |
I will pull down the multiqc container to confirm it's still working, then squash and merge |
Description
The new version of multiqc supports picard mimicked reports from Sentieon tools: MultiQC/MultiQC#2110
This should solve this issue: #1290 where an ugly solution was implemented in the Dedup rule to make MultiQC accept dedup-stats from Sentieon dedup.
It may also allow us to move away from Picard to generate our QC reports and instead use the Sentieon tools which should be faster and enable us to clear away some rules for a more streamlined and less messy workflow.
Added
Changed
Removed
Documentation
Tests
I downloaded the new multiqc docker (v1.22.3 of multiqc) as a singularity image and placed in a separate develop cache which I then used in my tests along with the updated align_qc.sif container which doesn't contain multiqc anymore
Ensure that we get all QC metrics in deliverables as before
NOTE: regarding multiqc version
As of 2024-04-31 it seems that there's a bug in multiqc or a feature, I don't know, but the latest version 1.22.1 does not pick up the relatedness score from somalier which kind of blocks this feature at the moment. But I have opened up a bug report in multiqc repo: updated multiqc no longer reports relatedness from somalier MultiQC/MultiQC#2596 and have tried downgrading the version to 1.18 which seems to be working.
As of 2024-06-05 They solved the bug and I have tested the latest version 1.22.2 which does pick up Somalier results, but I discovered that it also does not manage to pick up the Picard WgsMetrics results, which v1.18 does. So I will return to that older version. I opened a bug report CollectWgsMetrics from Picard not picked up in latest version MultiQC/MultiQC#2607
As of 2024-06-22 they are supposed to have solved the bug with version 1.22.3
Verified successfully for WGS T+N, and TGA-UMI T+N all metrics in the deliverables file are still there as in version 15.0.0
Feature Tests
Pipeline Integrity Tests
.hk
file)Clinical Genomics Stockholm
Documentation
User Changes
Infrastructure Changes
Checklist
Important
Ensure that all checkboxes below are ticked before merging.
For Developers
For Reviewers
conditions where applicable, with satisfactory results.