Hi Alan,
Binsanity highly relies on differential coverage to cluster so having only 1 bam file would be problematic. In Binsanity-wf you have 3 major steps.
1. Initial clustering using differential coverage
2. Evaluation via CheckM of bins
3. Refinement of bins using tetranucleotides and GC%
When you only have one sample that initial step where you cluster with differential coverage won't work very well. Assembly methods can vary depending on style. Co-Assemblys work, or you could do something like
this to merge individual assemblies using cd-hit and minimus2. You could even do a subsampled assembly. The key is you want some small overlap or similarity between samples for the differential coverage binning to successfully work. In general in terms of clustering with any method (whether it is Binsanity, CONCOCT, Metabat2, etc.) more samples leads to better binning. BinSanity excels when you have atleast 4-5 samples, but accuracy decreases with less.
My advice for working with one sample is to adjust preferences. In Binsanity-wf there is the flag `-p` which is the preference for the initial clustering. The default for this is -3. Change this to -2. Then change the `--refine-preference` flag to -15. The larger the preference in this case the more sensitive Affinity Propagation is to creating clusters, meaning it will ultimately produce more clusters the higher it is. Unfortunately defaults aren't always optimal for every data type :(
I hope that was helpful!