Hi everyone, First of all thank you for the nf-cor...
# mag
s
Hi everyone, First of all thank you for the nf-core teams for making these pipelines. I find them very pedagogical which is nice for beginners like me 🐣. My question is on the gtdb_min_completeness and max_contamination. I'm using the 5.1.0 version and looking at the nextflow_schema.json file, i see these parameters are based on the Busco analysis. I was wondering if it was possible to change this to base the min completeness and max contamination evaluation on another binqc_tool, like checkm2 ? Sorry if that question was answered already, I couldn't find it on the github issues or in this slack canal.
j
Hi Simon, More recent versions of mag supports this :)
I think since 5.2
But we may have forgotten to update the parameter docs 😅
Right @Jim Downie ? Since we added support for running all the QC tools, the filtering parameters just takes the maximum/minimum value from any of the bins?
j
I think that's how we ended up implementing it, yeah
👍 1
So that you get the subset of bins passing that would meet the threshold for any of the binQC tools
👍 1
j
Thanks for confirming, I'll make an issue to update the docs
j
I think also though that previously we did use the CheckM/CheckM2/BUSCO score, depending on what tool was actually selected?
j
I don't remembe rnow 😅 possibly
But the parameter docs definitely says just BUSCO which problem why the confusion
👍 1
s
Hello, thank you for your answers ! I didn't try running gtdb after checkm2 based on the documentation but I'll try it and see if it works !
I can confirm that it works on v5.1.0 with checkm2 !