Closed TCLamnidis closed 11 months ago
still need:
output.md
Citation is there already given it is already used for damage rescaling! https://github.com/nf-core/eager/blob/631f18efa4147d0b787245ed8dda041d00ebf6fd/README.md?plain=1#L249
Added mapDamage to Default Pipeline Steps in README. Standardised tool name to mapDamage
across all docs (as the name is in the GH repository of the tool)
Will wait for mapdamage module to be added to multiqc, then should be ok to merge
Should add a big fat warning top of the readme sayi g maximum NDC aversion of 22.10.6
Regarding the Bowtie read groups, the suggested edits would also need to be propagated to the bwa job. Specifically:
TODO: MultiQC does not pick up the mapdamage outputs locally, even though they are correctly published within the work directory and the module is activated. Have to check what is wrong.
I think that's everything!
@ltcrod Please have a look at the RG information for the mappers. Let me know if anything would be better implemented differently.
Linting works with nf-core v1.14. only failures are about template matching.
Closes #1020. Closes #1017. Clsoes #1031.
PR checklist
scrape_software_versions.py
nf-core lint .
).nextflow run . -profile test,docker
).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).