-
Notifications
You must be signed in to change notification settings - Fork 705
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
Assorted fixes to MultiQC usage #1352
Conversation
|
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.
Overall good!
The RNASEQ
workflow is very overloaded, I am tempted to break things into subworkflows! 🤔
Agreed- I've already done that with the contentious preprocessing subworkflow ;-). But not now.... |
Co-authored-by: Adam Talbot <[email protected]>
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.
a pure thing of beauty
Thanks @maxulysse @adamrtalbot ! |
This PR does a number of things related to issues identified in the MultiQC reporting:
trimmed
,raw
that were causing difficulties in the general stats.There is a persistent issue with versions not being displayed, caused by MultiQC/MultiQC#2750, so we'll wait for resolution there before a merge.Now resolvedDifferences between this and the current release can be seen in the attached reports.
multiqc_report_3_14.html.zip
multiqc_report_branch.html.zip
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).