Adding GO:IDs to the BLAST hits
2
0
Entering edit mode
7.5 years ago
EVR ▴ 610

hi,

I am new to Gene Ontology analysis. I am working on non-model organism. I have list of de-novo-assembled transcripts and their corresponding BLAST hits. Now I would like add all the GO IDs associated with with that BLAST hits. How can I do that without using BLAST2GO as it is commercial now. Kindly guide me. Thanks in advance

Gene Ontology BLAST • 3.8k views
ADD COMMENT
2
Entering edit mode
7.5 years ago
Farbod ★ 3.4k

Dear Tom, Hi

Of course you have mentioned "without using commercial Blast2GO", but the annotation and GO assignment procedure can be done with Blast2GO basic (free) version.

If your blast is in xml format (-outfmt 5), you can import your transcript sequence first and then import blast result on the same project Blast2GO and then run the annotation and mapping and GO assignment and after that export the .annot result freely from Blast2GO.

Then you can manipulate this file and use it in WEGO.

Trinotate would be one of your another choices.

~ Best

ADD COMMENT
0
Entering edit mode
7.5 years ago

When I call the mapping step on Blast2Go (v4) I get the following information displayed, under two titles; 'Mapping Configuration'-'Mapping the Blast Hits of each sequence with Gene Ontology Terms'.

Blast2GO performs different mapping steps to link all Blast Hits to the functional information stored in the Gene Ontology database. Therefore Blast2GO uses different public resources provided by the NCBI, PIR and GO to link the different protein IDs (names, symbols, GIs, Uniprots, etc.) to the information stored in Gene Ontology database

It could be difficult to find the exact steps they use but I am able to find same GO annotations Blast2GO finds for my few sample BLAST searches using UniProt REST queries alone:

ADD COMMENT

Login before adding your answer.

Traffic: 1409 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