1. Setup the environment:
setenv ONLINE_PACKAGES /afs/slac.stanford.edu/g/glast/online/packages setenv CVSROOT /nfs/slac/g/glast/online/cvsroot setenv ONLINE_ROOT ${HOME}/glast setenv PYTHONPATH ${ONLINE_ROOT}:${ONLINE_ROOT}/LATTE/ext setenv LD_LIBRARY_PATH ${ONLINE_ROOT}/LATTE/ext
2. Get LATTE from cvs:
cvs checkout LATTEor, in case you want a specific tag:
cvs checkout -r P04-03-01 LATTEor, in case you checked out LATTE before and you want the latest greatest:
cd LATTE cvs update -dA
3. Compile the python code, compile and link the c++ and c code, build the user interface files, create the digest data, set links to the external libraries:
cd LATTE gmake
4. Load the VxWorks side as usual:
cd "/nfs/slac/g/glast/vxw000/GASU/fsw" < startup-ACD-P.vx
5. Start runcontrol, eg:
cd LATTE/start $ONLINE_PACKAGES/python/Python-2.3.4/python ./startupMainGUI.py --server lat-elf1 --schema ../repos/simpleAemSchema.xml --config runControl.cfg.sample
- ONLINE_PACKAGES contains all the external packages LATTE depends on (this variable is site dependent)
- CVSROOT contains the LATTE cvs repository (this variable is site dependent)
- ONLINE_ROOT points one directory above your LATTE location (this variable is user or teststand dependent)
- possible targets to gmake are lib, bin and clean; it's also possible to build a single sub directory, eg:
cd LATTE gmake simulator.clean- the VxWorks boot directory is site dependent
- the VxWorks script startup-ACD-P.vx is for ACD gasu primary side; other available scripts are startup-ACD-R.vx (for ACD gasu redundant side) and startup-ltem.vx (for TEM 0 connected to transition board)
- you can also run in local mode:
cd LATTE ./bin/i386-linux/ocsmanager [playbackfile]where playbackfile is the optional name of a file containing recorded events