Difference between revisions of "New GO Progress Report Script"
|Line 26:||Line 26:|
Revision as of 21:37, 6 March 2014
GO is now requiring quarterly progress reports, with the first one due at the meeting this month (2014-03-16).
We've been wanting to provide a more details progress report for GO for some time now, so this is a good opportunity to do that.
Here's one idea for C. elegans manual annotations:
Input files (available on tazendra in home/acedb/ranjana/GO/Progress_Reports/Test):
- Ignore all lines with IEA evidence code, ECO:0000256, in Column 6
- Replace UniProtKB identifiers in Column 2 with WBGene ID using gp2protein.wb
- Remove (i.e. ignore for further reporting) any resulting lines that are exact duplicate lines of annotation
- Total number of unique annotations, i.e. unique lines.
- Total number of unique WBGenes.
- For each unique value in qualifier Column 3 count number of annotations for a given evidence code in Column 6 and number of annotations with an entry in Column 11. In other words, for each col3, I'd like to know the total number of different col6 and then also for each col3, the total number of different col6 that additionally have an entry in col11.
- Sort results according to unique entries in Column 10 (i.e., each contributing group).
- Also report on any lines where the UniProtKB identifier cannot be converted to a WBGene, i.e. where there is no mapping between a UniProtKB identifier and a WBGene according to the gp2protein file.
The goal is to have a report that shows, for each group contributing manual annotations to C. elegans genes, how many genes they;ve annotated, how many annotations they've made, what is the breakdown by ontology and evidence code, and how many of those annotations have an annotation extension.
For an idea of the kind of table I'm hoping to be able to produce, here's a link to Zfin's progress report from December 2013:
Back to [Gene Ontology]