-
Hello, I came across the BinSPreader tool and manuscript today while looking for ways to refine MAGs, and in particular thinking about how this may affect my dataset and the detection of MGEs in MAGs. I am interested in giving a try to this tool but the approach I followed before (vamp on samples assembled individually as vamb coders recommends) seems incompatible with BinSPreader. Basically, what I have tried before is to assemble samples individually, merge the contigs and get MAGs with vamb, metabat2 and maxbin2 that I analyze with DAS tool. However, the approach recommended by BinSPreader seems to need a single gfa file (I guess from a co-assembly). Is it possible (or even recommended) to run BinSPreader on different assemblies and MAGs obtained from them? What would be your recommendation in this case? Thank you, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Well, BinSPreader relies on assembly graph and in your case there is no single assembly graph to use for the refinement. I must also note that the co-binning procedure might lead to the high duplication ratios in MAGs especially if multiple strains are present. So, likely your only way is:
Alternatively:
|
Beta Was this translation helpful? Give feedback.
-
As I understand, you should be able to refine bins with binspreader for each sample individually. It doesn't matter which bin-workflow generated the contig-bin table, as long as you only have contigs from the sample. Or am I wrong? |
Beta Was this translation helpful? Give feedback.
Well, BinSPreader relies on assembly graph and in your case there is no single assembly graph to use for the refinement. I must also note that the co-binning procedure might lead to the high duplication ratios in MAGs especially if multiple strains are present. So, likely your only way is:
Alternatively: