Large singleton contigs should qualify as bins
Issue #62
resolved
According to Ed Kirton:
If a very large contig isn’t clustered with any other contigs, MetaBAT would place it in the unbinned file, however it should be considered a bin by itself.
Actions: Investigate if this is still the case and fix if so.
Comments (2)
-
reporter -
reporter - changed status to resolved
no longer an issue with metabat2
- Log in to comment
I do not see any evidence of this in metabat2, except in the case of issue # 68 where contigs are filtered because of low depth.
Running the CAMI high data set with different values for --minClsSize always leaves no contigs that are larger than minClsSize in the unbinned output file, and many bins with only 1 contig.