Blast Against Swissprot Db
2
3
Entering edit mode
13.9 years ago
Bdv ▴ 320

Hi I downloaded the swissprot database and used the command formatdb and then tried blastx against this database, I used the command: megablast -b 1 -T T -i....results.html I received results but with no links. When I blast against the nr or nt databases there are links there in the result file. What could be the reason for that? Thanks!!

blast uniprot • 7.6k views
ADD COMMENT
1
Entering edit mode

But is it the right way to blast against the swissprot? to create the db with formatdb? so you suggest to use a script which adds the link? I need to parse the result html file to some table whith the hits and descriptions, to make it readeble...

ADD REPLY
0
Entering edit mode

please, comment after my answer, don't create a new thread.

ADD REPLY
0
Entering edit mode

why do you use two accounts to connect on biostar ?

ADD REPLY
4
Entering edit mode
13.9 years ago

It's because NCBI blast has been integrated with the Entrez database. Most sequences here have a unique number called gi linking to an unique record in the NCBI-Entrez Database.

When you're running your local BLAST, the engine doesn't know anything about the database that was created with formatdb, there is no meta-information.

In the case of swissprot, I guess the URL can be easily created from the FASTA header of each sequence because it should contain an accession number. e.g. the URL for Q04637 is http://www.uniprot.org/uniprot/Q04637

ADD COMMENT
2
Entering edit mode
13.9 years ago

First you have to format your database following is the command for formatting

formatdb -i swissprot -p T -o T

Then you can perform blast

blastall -p megablast - d swissprot -i (here input your filename with extension) -o result.txt

this time it will create your result in result.txt file in bin folder.

Hope this will help you.

ADD COMMENT

Login before adding your answer.

Traffic: 1667 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6