Hi! I'm running mOTUlize 0.3.2 with mOTUlize.py --threads 6 --fnas allbins/*fa -o motu_allbins --checkm allbins_checkm_out.tsv --keep-simi-file and seem to be "losing" bins. I start off with 962 bins, but somewhere between starting and getting the output I lose 208 of the bins. The remaining 754 bins are clustered into 310 mOTUs, and I have no clue what happened. I've also run the same command on a previous set of bins, and then 3 bins were lost (but easy to just "add back"). What could be happening? I have been unable to check the fastani-output because --keep-simi-file doesn't seem to work (do I need to specify an output name?).
Thanks for this software!
Hi,
regarding the --keep-simi-file I think yes, you need to specify an output filename after the flag. That worked for me.
Don't know though what might have been the reason for the other issue unfortunately...
Hi! I'm running
mOTUlize 0.3.2
withmOTUlize.py --threads 6 --fnas allbins/*fa -o motu_allbins --checkm allbins_checkm_out.tsv --keep-simi-file
and seem to be "losing" bins. I start off with 962 bins, but somewhere between starting and getting the output I lose 208 of the bins. The remaining 754 bins are clustered into 310 mOTUs, and I have no clue what happened. I've also run the same command on a previous set of bins, and then 3 bins were lost (but easy to just "add back"). What could be happening? I have been unable to check the fastani-output because--keep-simi-file
doesn't seem to work (do I need to specify an output name?). Thanks for this software!