Open rec3141 opened 7 years ago
I expect it is a BLAST thing, because I just tried the same thing you described and got more than 400 hits per query:
What version of BLAST do you have? A hacky way to find out which one Bandage is using (in case you have multiple versions installed in different places) is to type rubbish into the command line parameters field: Then when you search, the resulting error message should state the BLAST version.
I'm using 2.2.31+ and it works for me. If you're on an older version, perhaps try upgrading BLAST? If that doesn't work, I'm not sure...
Ryan
Thanks, I updated BLAST and can't reproduce it
Ok coming back to this, I'm now on BLAST 2.6.0+ and Bandage 0.8.1 and found the issue cropping up again. Here the same assembly is used as the database. In the first example the query is a full-length bacterial chromosomal sequence, in the second it has been split into records of 10kb each. The coverage of the assembly is much greater in the second instance, and it's not clear why. The files are attached. Any suggestions? Thanks
When trying to use a complete bacterial genome as the BLAST query against an assembled genome, Bandage only finds a maximum of 400 hits per query sequence. I don't know if this is a BLAST thing or a Bandage thing, but it would be useful to raise that to a much higher number. My workaround now is to split the query into artificial contigs so that no single contig is saturated.