Difference between revisions of "CCC Workflow"

From WormBaseWiki
Jump to navigationJump to search
Line 1: Line 1:
 
*Yuling will perform CCC searches on each corpus.
 
*Yuling will perform CCC searches on each corpus.
 
**C. elegans search will coincide with SVM runs.
 
**C. elegans search will coincide with SVM runs.
***C. elegans source files will be here:http://textpresso-dev.caltech.edu/ccc_results/celegans/
+
***C. elegans source files will be here: http://textpresso-dev.caltech.edu/ccc_results/celegans/
 
**dictyBase search will be weekly or as often as Bob sends Yuling PMIDs to search.  
 
**dictyBase search will be weekly or as often as Bob sends Yuling PMIDs to search.  
 
***Bob adds new dictyBase papers on Mondays and will send a list of PMIDs to Yuling to run through the CCC pipeline on the subsequent Tuesday.
 
***Bob adds new dictyBase papers on Mondays and will send a list of PMIDs to Yuling to run through the CCC pipeline on the subsequent Tuesday.
 +
***dictyBase source files will be here:  http://textpresso-dev.caltech.edu/ccc_results/dicty/
 
**TAIR search will be...
 
**TAIR search will be...
  

Revision as of 20:04, 29 August 2013

  • Cronjobs will look for new source files on textpresso-dev and transfer them to the appropriate MOD directory on tazendra.
    • When new sources files are available, scripts will run to generate and populate the tables needed for the curation form.
    • Curators will get an email alert telling them that there is/is not new source data available for curation.
  • When new source files are generated the accession mappings file on textpresso-dev will be updated to create a new pmid_data file for the curation form.
  • New gpi files with updated gene - identifier mappings should be placed where??


Back to WormBase