-
Notifications
You must be signed in to change notification settings - Fork 836
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
ADDORREPLACEREADGROUPS and MERGEBAMALIGNMENT input/output file specificity fix. #8115
base: master
Are you sure you want to change the base?
ADDORREPLACEREADGROUPS and MERGEBAMALIGNMENT input/output file specificity fix. #8115
Conversation
…johnoooh/modules into bugfix/addorreplacereadgroups-prefixfix
…johnoooh/modules into bugfix/addorreplacereadgroups-prefixfix
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.
It looks like you are trying to revert the meta.yml to the older version, without the nested indentation for the channel structure?
@SPPearce Prettier wasn't run properly, it has been fixed |
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.
Can you check the stub and its test, because it looks like it isn't outputting any bam (might need def
removing from prefix
, but also looks like it was making output files with null
in the name before.
When using ADDORREPLACEREADGROUPS on an HPC with scratch enabled, the globbed *.bam copys both the input and output bam from scratch to the work directory. The output needed to be more specific. It is now ${prefix}.bam for the output so it now targets the output bam/cram instead of all files with the right file extension. For more details see the issue.
This should fix the issue for ADDORREPLACEREADGROUPS but be on the lookout for other modules where this occurs.
PR checklist
Addresses ##7792, but more modules could have issues.
versions.yml
file.label
nf-core modules test <MODULE> --profile docker
nf-core modules test <MODULE> --profile singularity
nf-core modules test <MODULE> --profile conda
nf-core subworkflows test <SUBWORKFLOW> --profile docker
nf-core subworkflows test <SUBWORKFLOW> --profile singularity
nf-core subworkflows test <SUBWORKFLOW> --profile conda