GOstat GO term format "GO:00003567" or "3567" ?
1
0
Entering edit mode
@bannistersc-7464
Last seen 8.7 years ago
Austria

Hi All,

Sorry if this is too basic, I have read through a bunch of forum posts already but I don't find an answer to this.

I want to run GOstat to calculate GO term enrichment in Differentially expressed genes (DEGs) vs. a background gene Universe which = the reference transcriptome. [I work with a non-model organism].

I have GO annotations from Blast2GO for my DEGs, exported in GOstat format - which formats the GO term IDs without the "GO:00.." prefix. eg:  "3567" - versus "GO:0003567" which is how they usually appear.

Because of this I formatted the GO terms in my data.frame that contains the GO terms and evidence codes for the gene Universe the same way.

However, in the Vignette for GOstats with unsupported model organisms the example shows the GO terms in the goframeData data.frame with the usual "GO:00.." format.

Now I'm confused as to how I should have my GO terms formatted for the GOstats to work?  I haven't yet tried to run the HyperG test yet because I want to be sure I have all the input files I need first.  Can anyone please tell me which format the GO terms need to be in? If it weren't for the exported format of the Blast2Go lists I probably wouldn't have even thought about this.

Cheers

Steph

 

GOstat format input files • 1.5k views
ADD COMMENT
0
Entering edit mode
@bannistersc-7464
Last seen 8.7 years ago
Austria

I seem to have answered my own question via experimentation.  The GO terms do need the usual "GO:00..." format.  I'm still confused though as to why the GOterms that are exported from Blast2Go in GOstat format do not have this format? does anyone know why?

Cheers

Steph


 

ADD COMMENT
0
Entering edit mode

I assume you are talking about this blast2go? If so, questions about their output should be directed to them, not us.

ADD REPLY

Login before adding your answer.

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