You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I imagine this is more a case of me not fully understanding how DAS Tool works, rather than a problem. I assumed that the *allBins.eval output file would list all bins that were used as input. However, for all of my runs it lists less bins than I used as input in my *_contigs2bin.tsv files. The bins that weren't included are all very low quality according to checkm2, so I was wondering if there is a quality control step prior to including bins in the evaluation file? Perhaps bins aren't included in the file if they have no unique_SCGs?
If this is the case, is there an output from DAS_tool that lists what bins were discarded? I have had a look but I can't see anything.
Thanks for your help,
Laura
The text was updated successfully, but these errors were encountered:
Hi,
I imagine this is more a case of me not fully understanding how DAS Tool works, rather than a problem. I assumed that the *allBins.eval output file would list all bins that were used as input. However, for all of my runs it lists less bins than I used as input in my *_contigs2bin.tsv files. The bins that weren't included are all very low quality according to checkm2, so I was wondering if there is a quality control step prior to including bins in the evaluation file? Perhaps bins aren't included in the file if they have no unique_SCGs?
If this is the case, is there an output from DAS_tool that lists what bins were discarded? I have had a look but I can't see anything.
Thanks for your help,
Laura
The text was updated successfully, but these errors were encountered: