SITCOMTN-001: Operations Manual for Dome Seeing Monitor

  • Michael Reuter

Latest Revision: 2019-11-07

1   The LSST Dome Seeing Monitor

The LSST Dome Seeing Monitor (DSM) is an instrument for measuring the seeing within an enclosed environment, such as a telescope dome.

2   Using the Monitor UI

The DSM laptop contains the software to run the monitoring user interface (UI). It is installed within a miniconda environment. To setup the environment for running the UI, perform the following from a terminal.

conda activate dsm

The UI is configured via one of the files contained in the /dsm/dsm_ui_config directory. This directory is a clone of this GitHub repository and contains the standard configurations for the DSM. To run the default configuration of the UI, do the following from a terminal (after running the steps above.).

smm_ui -c /dsm/dsm_ui_config/default.yaml

2.1   Installing a New UI Version

Should it become necessary to install a new version of the UI, you must switch into the dsm service account by first doing the following.

sudo su -s /bin/bash dsm

Next, perform the steps to setup the environment and then run the following.

pip install -U spot_motion_monitor

If a new version is available, it will be installed.

3   Installing a Development Version

If it becomes necessary to install a development version of the UI, first create a directory called git in your home directory. Next, cd into that and execute the following.

git clone

If you intend to commit changes back to the repository and have the privileges to do so, clone the repository this way.

git clone

Next change into the directory of the clone and checkout the branch that you want to run. Example is shown below.

cd spot_motion_monitor
git checkout -t origin/tickets/SE-1302

Once on the correct branch, perform the following steps to run the UI.

conda activate dsm_dev
python build_ui
rsmm python scripts/

The rsmm wrapper sets up the environment to correctly execute the program. The CLI options from smm_ui are all available in this mode. The third step is only necessary when changing branches. The last step is necessary on subsequent executions of the UI.