...
- Online CVS — /nfs/slac/g/glast/online/cvsroot
- Flight software — See the value of, e.g., CMX_I_VSC after you set the instance from cmx (see below).
The The second Linux machine will usually be lat-hobbit4 or lat-hobbit5 which have access to a LICOS installation and an abbreviated installation of flight software intended for use by LICOS Python scripts.
...
For definiteness this document assume that you're using lat-fangorn and lat-hobbit5.
Logging Logging in
From your home machine log in to lat-fangorn and lat-hobbit5 from separate terminal windows. Use SSH and make sure that X11 forwarding is enabled.
...
From Windows make two connections using Tera Term Pro SSH.
Setting up the environment
If If you have a .login, .cshrc, or .tcshrc file already set up in your home directory you should make sure that for the machines discussed here they either run the commands given below or do very little or nothing. It's very important to disturb PATH and PYTHONPATH as little as possible from the standard settings for LICOS work. For example, you must always use the Python interpreter installed in /usr/local/bin on lat-hobbit5 since it has required third-party software installed such as Qt. It's better to use .login rather than .cshrc or .tcshrc since the standard setup scripts don't check to see whether they've already been run, so establish the environment once and then let new processes inherit it. Of course you can't inherit aliases but luckily there aren't any you really need.
lat-fangorn:
| No Format |
|---|
setenv LD_LIBRARY_PATH
set interactive=${?prompt}
setenv GLASTROOT /afs/slac.stanford.edu/g/glast
source ${GLASTROOT}/flight/scripts/group.cshrc
cmx start
cmx set instance B0-x-y
|
where x and y are the major and minor release numbers for the LAT flight software version you need to use.
latlat-hobbit5:
| No Format |
|---|
setenv ONLINE_PACKAGES /usr/local
setenv ONLINE_EXT /usr/local/ext
setenv ONLINE_ROOT /usr/local/online
setenv ONLINE_SCRATCH ~/projects/LICOS/LAT06x/scratch
source ${ONLINE_ROOT}/LICOS_ETC/setup/setupLICOS.csh
|
...
| No Format |
|---|
xterm -title VSC -n VSC -geometry 92x35+000+000 & xterm -title SIU -n SIU -geometry 92x35+580+000 & xterm -title EPU0 -n EPU0 -geometry 92x35+000+492 & xterm -title EPU1 -n EPU1 -geometry 92x35+580+492 & |
...
| No Format |
|---|
xyplex lat-elf1
(You may have to type Enter to get the VxWorks prompt '-> '.)
reboot (Control-X will also work.)
(Wait for VxWorks to reboot and give you the '-> ' prompt again.)
^] (That's control-]. Wait for the telnet prompt 'telnet> '.)
quit
(You should be back in tcsh now.)
fmx xyplex /nfs/slac/g/glast/online/VSC/vsc.fmx --tag=mv2304 --target=lat-elf1
|
...
Bringing up the SIU (and starting the VSC scheduler)
You You can't be sure of what state the SIU was left in by the previous user so it's best to reboot it.
...
lat-hobbit5:
| No Format |
|---|
python (This should be /usr/local/bin/python.) from LICOS.scriptEngine.ScriptEngineConnector import ScriptEngineConnector vsc = ScriptEngineConnector("lat-elf1", None, None) vsc.start() vsc.bootSIU(0) (Don't exit python yet.) |
The call of start() should result in a message in the VSC terminal window saying that the VSC scheduler has been started. The call to bootSIU() produce messages in the SIU window to the effect that the SIB has been found and leave it in a VxWorks shell session. Now you can bring up the SIU in much the same way as you did the VSC.
...
| No Format |
|---|
vsc.mainFeedOn(siuId=1, pduId=1)
vsc.ssr(1)
vsc.powerOnEpuOnly(epuId=0, pduId=1)
vsc.powerOnEpuOnly(epuId=1, pduId=1)
(Wait 30 seconds)
vsc.bootEPU(0)
vsc.bootEPU(1)
|
...
Once you can get a VxWorks prompt on EPU0:
lat-fangorn(EPU0):
| No Format |
|---|
^] quit fmx xyplex /nfs/slac/g/glast/online/VSC/epu.fmx --tag=rad750 --target=lat-elf3 |
The procedure is the same for EPU1, only using its window and changing the name of the target to lat-elf4. .
Starting the proxies
| Wiki Markup |
|---|
The LICOS script engine doesn't connect directly to the VSC to get its telemetry. Instead it connects with up to three proxy servers, which in turn expose TCP ports for the script engine. A different set of ports is supposed to be used by each person so that several people can be running LICOS sessions on the same Linux machine at the same time. The set of ports is derived from the proxyPortBase parameter in the \[vsc] section of the VSC configuration file. You can get a standard VSC config file on lat-hobbit5 from $ONLINE_ROOT/LICOS_ETC/config/vsc_tb.cfg. Your personal value of proxyPortBase must be assigned by an Authority. |
| Wiki Markup |
|---|
The proxies also dump the telemetry they receive into files. Their locations can be controlled with parameters in the \[paths] section of the VSC config file. |
| No Format |
|---|
[paths]
# archive path is where the raw output of the proxies ends up
archive_path = /MY-WORK-AREA/scratch/stage
# ingest_path is where ISOC is expecting its Level 0 output
ingest_path = /MY-WORK-AREA/scratch/isoc
# lsf path is where LsfWriter and analysis engine have lsf data
lsf_path = /MY-WORK-AREA/scratch/lsf
|
Assuming you have your VSC config file in ./vsc.cfg you can start the proxy manager. You can then use its GUI to activate the proxies individually or collectively.
| No Format |
|---|
xterm -title Proxies -n Proxies -e ${ONLINE_ROOT}/LICOS/tools/proxy/ProxyManager.py \
--vscip lat-elf1 \
--config vsc.cfg &
|