Fix #452: publishDir collisions between PRESTO_PARSE_CLUSTER and PRESTO_PAIRSEQ_CLUSTERSETS#453
Conversation
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.5.1. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
There was a problem hiding this comment.
Pull request overview
Fixes output overwrites caused by publishDir collisions between PRESTO_PARSE_CLUSTER(_UMI) and PRESTO_PAIRSEQ_CLUSTERSETS in the PRESTO UMI subworkflow.
Changes:
- Update
PRESTO_PAIRSEQ_CLUSTERSETSpublishDirto a dedicated subdirectory to avoid collisions. - Add an
Unreleasedchangelog entry documenting the fix.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
conf/modules.config |
Moves PRESTO_PAIRSEQ_CLUSTERSETS published outputs under 05-parse-clusters/pairseq/ to prevent overwrites. |
CHANGELOG.md |
Adds an Unreleased “Fixed” entry for the collision fix. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
ggabernet
left a comment
There was a problem hiding this comment.
@tgelafr-pfzr Thank you for providing this fix!
Co-authored-by: Gisela Gabernet <gisela.gabernet@gmail.com>
Closes #452, fixing collisions between publishDir locations of
PRESTO_PARSE_CLUSTER_UMIandPRESTO_PAIRSEQ_CLUSTERSETSPR checklist
nf-core pipelines lint).nextflow run . -profile test,docker --outdir <OUTDIR>).nextflow run . -profile debug,test,docker --outdir <OUTDIR>).CHANGELOG.mdis updated.