Page History

The "Über" test stand is located in the northwest corner of the Dataflow Lab in building 84 (immediately to your right if you enter through the door with the combination lock). This test stand has a VSC crate (host lat-elf1), and SIU (lat-elf2), EPU0 (lat-elf3) and EPU1 (lat-elf4). Look here for a more detailed description of the available hardware. Ignore the information about boot flags; I've never managed to get the Über to autoboot.

In order to use the Über with LICOS you'll need to log in to two Linux machines. The first will usually be lat-fangorn or lat-hobbit1 which have access to the Online CVS repository and to a full installation of LAT flight software.

• 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 with cmx (see below).

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.

...

• • LICOS_Scripts — Test script library
• Flight software — /usr/local /bin, /usr/local/ext/bin, /usr/local/ext/python

...

[paths]
# archive path is where the raw output of the proxies ends up
archive_path = /MYYOUR-WORK-AREA/scratch/stage

# ingest_path is where ISOC is expecting its Level 0 output
ingest_path  = /MYYOUR-WORK-AREA/scratch/isoc

# lsf path is where LsfWriter and analysis engine have lsf data
lsf_path = /MYYOUR-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.

lat-hobbit5:

...

_*IMPORTANT:* Make sure that the source code number in the \[tlmdb] section is 79. This identifies the source of any telemetry you save in the ISOC archive as coming from a test run and not from the real spacecraft._

Assuming you have your VSC config file in ./vsc.cfg you can start the proxy manager using the command below. You can then use its GUI to activate the proxies individually or collectively.

lat-hobbit5:

^D                       (Exit your Python session and get back to the shell.)
xterm -title Proxies -n Proxies -e ${ONLINE_ROOT}/LICOS/tools/proxy/ProxyManager.py \
    --vscip   lat-elf1 \
    --config  vsc.cfg &

Running the script engine

There is yet more configuration to do before you can run the script engine. First, you need to create a file called runId.cfg which looks like this:

[RunIdData]
runid = 0

[MachineData]
machineid = ???

The run ID is just a counter that gets incremented every time you start a run with the script engine (see below). The machine ID is another number you'll have to get from an Authority; it identifies you as the source of any telemetry that you save in the ISOC raw data archive.

You will also need to make a scriptEngine.cfg file; I've attached a template to this Confluence page. The important parts are the first two sections:

[paths]
appdir = $ONLINE_ROOT/LICOS_Scripts/seApps

runiddir = /YOUR-WORK-AREA

reportdir = $ONLINE_SCRATCH/reports
logdir    = $ONLINE_SCRATCH/logs

exportdir   = $ONLINE_SCRATCH/exports
snapshotdir = $ONLINE_SCRATCH/snaps
datadir     = $ONLINE_SCRATCH/data

reposdir    = $ONLINE_ROOT/LICOS/repos

[logging]
lognbl = 0
loglevel = DEBUG
loghost = localhost

ONLINE_SCRATCH is an environment variable that you should define as /YOUR-WORK-AREA/scratch. You will need to make the directory scratch and its subdirectories reports, logs, exports, snaps, and data. The runiddir parameter tells the script engine where to look for your runId.cfg file.

In the \[logging] section you will normally run with logging disabled (lognbl = 0). If you set it to one then the logging files will be written to the logs directory. 
*_IMPORTANT:_ At present this seems to have the side effect that only one instance of the script engine at a time can run on the host machine, so do it only when you must, e.g., test script V&V.*

...