-
Notifications
You must be signed in to change notification settings - Fork 801
Qc optimization #1601
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
base: dev
Are you sure you want to change the base?
Qc optimization #1601
Conversation
- Set skip_dupradar=true (mostly pointless for bulk RNA-seq) - Set skip_qualimap=true (identified as slowest QC step) - Set skip_rseqc=true (7 resource-intensive modules by default) - Set skip_stringtie=true (additional assembly overhead) - Set skip_bigwig=true (coverage track generation overhead) Follows nf-core/proposals#71 to make QC steps opt-in rather than mandatory. Users can re-enable comprehensive QC via parameters when needed. Significantly reduces pipeline runtime and compute costs for standard bulk RNA-seq workflows. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: adamrtalbot <adamrtalbot@users.noreply.github.com>
Add comprehensive documentation for the performance-optimized QC defaults: - Add "Quality Control Configuration" section to usage.md explaining the v4.0 changes - Document which QC steps are now disabled by default and why - Provide clear commands to restore comprehensive QC when needed - Add guidance on when to enable extended QC analysis - Update all affected QC sections in output.md with proper admonition notes - Use consistent :::note syntax following nf-core documentation standards Updates changelog with breaking changes and performance improvements. Helps users understand the new defaults and migrate their workflows appropriately. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
|
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.
I have no objection to a bit of polar-bear saving, but I'd like a bit of explanation about why some of the options aren't widely useful. I also think it would make sense to leave them as flags but flip the sense.
|
||
Starting in version 4.0, several QC steps are disabled by default to improve pipeline performance and reduce compute costs for typical bulk RNA-seq analysis: | ||
|
||
- **`--skip_dupradar true`** - Disable dupRadar analysis (limited utility for bulk RNA-seq experiments) |
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.
Could you qualify the reasoning behind the 'limited utility' assertion please?
Starting in version 4.0, several QC steps are disabled by default to improve pipeline performance and reduce compute costs for typical bulk RNA-seq analysis: | ||
|
||
- **`--skip_dupradar true`** - Disable dupRadar analysis (limited utility for bulk RNA-seq experiments) | ||
- **`--skip_qualimap true`** - Disable Qualimap alignment QC (resource-intensive step) |
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.
Since we're flipping the sense of the flags (and we'd have to make a major version anyway), maybe these should be renamed instead? --run_qualimap
etc?
PR checklist
nf-core pipelines 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).