Training new Browser Staff: Difference between revisions
From genomewiki
Jump to navigationJump to search
mNo edit summary |
|||
| Line 9: | Line 9: | ||
* email for UCSC and SOE | * email for UCSC and SOE | ||
* key card | * key card | ||
* copy .tcshrc | * copy .tcshrc and .bashrc from one of us (both are needed to run scripts) | ||
* coy .hg.conf and .hg.conf.beta from someone, so you can run hgsql and scripts that use it. | |||
* check out a copy of the kent source tree | * check out a copy of the kent source tree | ||
* set up nightly cron to update kent source tree | * set up nightly cron to update kent source tree | ||
Revision as of 19:39, 20 February 2010
Some ideas about how to train new QA Engineers...
(see also: Getting Started)
Logistics
- get a computer
- get a login
- email for UCSC and SOE
- key card
- copy .tcshrc and .bashrc from one of us (both are needed to run scripts)
- coy .hg.conf and .hg.conf.beta from someone, so you can run hgsql and scripts that use it.
- check out a copy of the kent source tree
- set up nightly cron to update kent source tree
- build your own sandbox
Tools
- vi (vimtutorial) -- or other editor
- mysql
- CVS (or git, if we git it) tutorial: http://www.soe.ucsc.edu/research/compbio/cvsdoc/cvs-tutorial/cvs_tutorial_toc.html
Browser
- Open Helix tutorials
- ASHG hands on tutorial
Data
- Jorge's data flow PowerPoint presentation
Training person-to-person (in rough chronological order)
- machine layout
- data flow
- using cvs: day to day commands, and cvs reports/pair review process
- trackDb.ra and trackDb table
- make docs
- pushQ
- QAing a "normal" track (using the checklist, perhaps)
- joinerCheck
- static docs
- makefiles
- /usr/local/apache vs. the cvs tree
- hgcentral
