There are two ways to start obstac: stand-alone, and using the SISPI architect. If obstac is will be used for automatic observation, or if it is configured to place targets directly on the SISPI/OCS queue, then the SISPI architect must be used.
In either case, the current version of the DB product on the CTIO nodes does not set up the environment variables correctly for obstac, so the following is needed before starting:
setup obstac export SISPI_OBSTAC_DB_HOST=$SISPI_DB_HOSTexport SISPI_OBSTAC_DB_NAME=$SISPI_DB_NAMEexport SISPI_OBSTAC_DB_USER=$SISPI_DB_WRITERexport SISPI_OBSTAC_DB_PORT=$SISPI_DB_PORTexport SISPI_OBSTAC_DB_WRITER_PASSWORD=$SISPI_DB_WRITER_PASSWORD
If obstac will be for simulation, or it is configured to use its own queue and interact with SISPI's only through exported text files, then it may be started independently of the architect.
To start obstac using the architect, make sure the architect's .INI file includes the obstac roles (see *Configuring obstac), and start the architect. The architect will then handle starting obstac.
If obstac will be run stand-alone, then use the obstac executable start_obstac:
setup obstac start_obstac
These commands will start the obstac web interface. Stopping the process (eg with a ctrl-c) will stop it.
Author: Eric H. Neilsen, Jr.
Date: November 21, 2010
HTML generated by org-mode 7.01 in emacs 23