I have a list of proteins in fasta format (say goodProteins.fasta). I first make a compatible database using NCBI's formatdb v 2.2.18:
formatdb -i goodProteins.fasta -p T -o T
This gives me a number of files (.psq, .pin, .phr, .psi, .psd).
Then, I run NCBI's blastall :
blastall -F 'm S' -v 100000 -b 100000 -z 67924 -e 1e-5 -p blastp -d goodProteins.fasta -m 8 -o blast.out -i goodProteins.fasta
This starts the blast but then proceeds to give me errors such as
[NULL_Caption] ERROR: SeqPortNew: lcl|5579_goodProteins.fasta start(384) >= len(363)
[NULL_Caption] ERROR: SeqPortNew: lcl|5579_goodProteins.fasta start(404) >= len(363)
[NULL_Caption] ERROR: SeqPortNew: lcl|5579_goodProteins.fasta start(433) >= len(363)
[NULL_Caption] ERROR: SeqPortNew: lcl|5579_goodProteins.fasta start(453) >= len(363)
[NULL_Caption] ERROR: SeqPortNew: lcl|5579_goodProteins.fasta start(472) >= len(363)
[NULL_Caption] ERROR: SeqPortNew: lcl|5579_goodProteins.fasta start(491) >= len(363)
I have uploaded all the data files at http://www.filedropper.com/datatar so anyone can reproduce the errors.
I found this A: Some Questions About Using Orthomcl To Find Orthologs Within Many Species to a related question, but I don't see any spaces in my id's.
Don't think it's directly the problem here but (for clarity if nothing else) you shouldn't really name your BLAST database the same as your query. Also
makeblastdb
might be a better choice to build your db, I think formatdb is no longer supported.Ben, I don't think your comment is relevant because
formatdb
is the correct command withblastall
(this isn't BLAST+) andblastall
will just look for those file extensions listed in the question.hbw, the SeqProtNew errors are usually related to using multiple, or incorrectly formatted, databases in my experience. Try using "-A F" when creating the database, and reconsider whether you need to use the "-z" option with
blastall
.Yep, it's still a depreciated program though and, like I said, different names are good for clarity if nothing else (e.g. goodProteinDB + the random blast extensions).
using
makeblastdb
, the errors apparently disappear. I guess I will simply upgrade to 2.2.27 (that is BLAST+, right?).