Gp2protein report: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Redirected page to Defunct) |
||
Line 1: | Line 1: | ||
# | #REDIRECT [[Defunct]] | ||
[[Category:Annotation Archived]] | [[Category:Annotation Archived]] |
Latest revision as of 18:46, 4 March 2020
Redirect to:
This page describes how the gp2protein report is generated by go-production
For more details on the gp2protein file, see the gp2protein page
- GOC gp2protein report
cvs: org/util/cron/go/gp2protein_report.pl
This needs to be moved to the regular go cvs, out of SGD.
steps:
login to goad as mysql [mysql@goad load]$ pwd /share/godev/golite/load
mkdir gpReport (where report files will be generated)
scp the script gp2protein_report.pl to gpReport/ (or in any official place via cvs co)
#test run, no email send out and email content to stdout mysql@goad gpReport]$ perl gp2protein_report.pl -log ../gp2protein_fail.log -user goadmin -pssd hoot1Nov -sock /db0/mysql/admin/golite/mysql.sock -reportdir . > temp.report
# real run with -dosend, will send report emails to mods mysql@goad gpReport]$ perl gp2protein_report.pl -log ../gp2protein_fail.log -user goadmin -pssd hoot1Nov -sock /db0/mysql/admin/golite/mysql.sock -reportdir . -dosend
take all report files from gpReport directory and deposit into goc cvs which is accessible from web. http://www.geneontology.org/internal-reports/gp2protein/
We need to put this in a cron job as well