Make ancient DNA damage correction optional#459
Conversation
This PR is against the
|
|
alexhbnr
left a comment
There was a problem hiding this comment.
The skipping of the contig correction itself works well. However, when activating --skip_ancient_damagecorrection pyDamage doesn't export the files into a sample specific sub-folder any longer. The usual way was that pyDamage has sample-specific sub-folders in Ancient_DNA/pydamage/analyze and Ancient_DNA/pydamage/filter. At the moment, for every sample the same file is used and the results of the previous run sample are overwritten.
|
Fix applied, waiting from results on tests as discussed on slack. |
This makes the damage correction subworkflow optional, i.e. ytou can run just pyDamage, and optionally turn on damage correction using freebayes and bcftools.
@alexhbnr please can you test, and let me know if you would refer to have it opt in (rather than opt out).
Also note this does not yet include the hotfix in the patch for #449 , I will add that later as it requires more thinking due to the more complex inputs to bin refinement since domain classification has come in.
fixes #456
PR checklist
nf-core lint).nextflow run . -profile test,docker --outdir <OUTDIR>).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).