-
Notifications
You must be signed in to change notification settings - Fork 86
Fix mapdamage_rescaling naming of output bam files
#719
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
Conversation
Use `${bam.basename}` (or `${base}`, which was already defined but not used) to strip the `.bam` extension of the original input file for the output of `mapdamage_rescaling`, so filenames won't turn up like this:
```
library_libmerged_rg_rmdup.bam_rescaled.bam
```
|
|
Just in time for a new patch release! Thank you!! |
|
No worries @jfy133, I have a few other ideas for improvements (which I should submit as issues), I wish I had the time/energy to stay awake for the NF hackathon and do those... |
|
Awesome! Feel free to bring them up in the slack channel if you want informal chat/feedback about them already |
Use
${bam.basename}(or${base}, which was already defined but not used) to strip the.bamextension of the original input file for the output ofmapdamage_rescaling, so filenames won't turn up like this:PR checklist
scrape_software_versions.pynf-core lint .).nextflow run . -profile test,docker).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).