Page History

...

• VSC/LAT ordinary telemetry (housekeeping),
• VSC/LAT diagnostic,
• Science.

Wiki MarkupThe LICOS script engine _et al._ connect with some or all of the proxies using TCP port numbers determined by the proxyPortBase parameter in the \ [vsc\] section of the VSC configuration file. 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. You can get a standard VSC config file on lat-hobbit5 from $ONLINE_ROOT/LICOS_ETC/config/vsc_tb.cfg.

IMPORTANT: Your personal value of proxyPortBase must be assigned by an Authority.unmigrated-wiki-markupAuthority.

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.

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

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

# lsf path is where LsfWriter and analysis engine have lsf data
lsf_path = /YOUR-WORK-AREA/scratch/lsf

...

*_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. You do have to start the ones your script needs telemetry from before you launch the script engine.

...

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.

Wiki MarkupIn 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 it seems that only one instance of the script engine at a time can run on the host machine with logging enabled, so do it only when you must, e.g., for test script V&V.

...