Proposal for cron tabs (Archived): Difference between revisions

From GO Wiki
Jump to navigation Jump to search
No edit summary
Line 2: Line 2:


===PAINT GAFs===
===PAINT GAFs===
*The PAINT inferences for each family are submitted into: http://cvsweb.geneontology.org/cgi-bin/cvsweb.cgi/go/gene-associations/submission/paint/
The PAINT inferences for each family are submitted into: http://cvsweb.geneontology.org/cgi-bin/cvsweb.cgi/go/gene-associations/submission/paint/
These inferences are then parsed by a script and annotations are split by taxon_id and these GAFs are submitted to -
These inferences are then parsed by a script and annotations are split by taxon_id and these GAFs are submitted to -
http://cvsweb.geneontology.org/cgi-bin/cvsweb.cgi/go/gene-associations/submission/paint/pre-submission/
http://cvsweb.geneontology.org/cgi-bin/cvsweb.cgi/go/gene-associations/submission/paint/pre-submission/
(Each group should be picking up annotations from this pre-submission directory and incorporating them into their own MOD DB and GAFs).
<br>(Each group should be picking up annotations from this pre-submission directory and incorporating them into their own MOD DB and GAFs).
Now that more curators are doing PAINT annotations, inferences are being checked into CVS mroe often. Currently the conversion to these GAFs happens when they are requested. We need to generate the taxon specific GAFs on a more regular basis. It was agreed on the Ref.genome call that it is sufficient to generate these GAFs once a month. <br>
Now that more curators are doing PAINT annotations, inferences are being checked into CVS mroe often. Currently the conversion to these GAFs happens when they are requested. We need to generate the taxon specific GAFs on a more regular basis. It was agreed on the Ref.genome call that it is sufficient to generate these GAFs once a month. <br>
<b>Requests</b><br>
<b>Requests</b><br>
**The script that generates these should be put on a cron tab.  
*The script that generates these should be put on a cron tab.  


**In addition, when these files are generated and checked into CVS, an email should be sent to the each group.
*In addition, when these files are generated and checked into CVS, an email should be sent to the each group.


===MF-BP inferences===
===MF-BP inferences===

Revision as of 12:15, 25 March 2011

Setting up Crob Tabs for generating PAINT and MF-BP GAFs

PAINT GAFs

The PAINT inferences for each family are submitted into: http://cvsweb.geneontology.org/cgi-bin/cvsweb.cgi/go/gene-associations/submission/paint/ These inferences are then parsed by a script and annotations are split by taxon_id and these GAFs are submitted to - http://cvsweb.geneontology.org/cgi-bin/cvsweb.cgi/go/gene-associations/submission/paint/pre-submission/
(Each group should be picking up annotations from this pre-submission directory and incorporating them into their own MOD DB and GAFs). Now that more curators are doing PAINT annotations, inferences are being checked into CVS mroe often. Currently the conversion to these GAFs happens when they are requested. We need to generate the taxon specific GAFs on a more regular basis. It was agreed on the Ref.genome call that it is sufficient to generate these GAFs once a month.

Requests

  • The script that generates these should be put on a cron tab.
  • In addition, when these files are generated and checked into CVS, an email should be sent to the each group.

MF-BP inferences

and again the script is run manually.
Requests

    • Can the location of these files be moved to a NEW directory under the gene-associations directory?
    • Can this script also be put on a Cron tab
    • An email sent out to groups when a new file is checked in?