Possibility non-initial merge BAMs not sent to downstream bamtrim etc. steps?

nf-core / eager

A fully reproducible and state-of-the-art ancient DNA analysis pipeline

https://nf-co.re/eager

MIT License

140 stars 80 forks source link

Possibility non-initial merge BAMs not sent to downstream bamtrim etc. steps? #893

Closed jfy133 closed 2 years ago

jfy133 commented 2 years ago

Reported by Rodrigo on 7th June 2022 - check private messages

jfy133 commented 2 years ago

Recap:

In one run, ran libraries that both required and did not require initial BAM merging. While the BAMs were correctly generated (latter in markdiplicates folder, former in additional_merging/intial), the latter (non-bam merged) didn't seem to be sent down to the downstream steps

jfy133 commented 2 years ago

Aaaaand after testing, I find out I entirely made that up in my head... thinking @RodrigoBarquera wanted to do that within eager, but in fact did he does manually. So this isn't a real issue.