We are attempting to automate the 61“ using RTS2. This wiki page should give the basics of how to run RTS2

The version of RTS2 on kuiper is a fork from the main rts2 version. it can be cloned from https://github.com/srswinde/rts2. The only real differences from the main rts2 repo is a few updates to the Azcam driver and some scripts for convenience.

Currently RTS2 runs on the bigpop computer. You will need sudo privileges on bigpop to run RTS2. To run it log into bigpop and type

sudo service rts2 start

and then sudo service rts2 status

to make sure all the RTS2 processes started. It should look something like this:

The current user interface is a ncurses based tool called rts2-mon. To start it simply type rts2-mon in a shell. It will look

It is separated into three sections and a menubar. To access the menubar use F9. The most important menu items are System → exit to exit rts2-mon and States→on, states→off. RTS2 will not automatically start observing unless you set its state to on.

The three main sections of the rts2-mon are the driver list on the left side the variable list on the right and the logger messages on the bottom. To access each or the main sections use the tab key. Whichever section is active will have highlighted borders.

The driver list on the left side gives you a list of the drivers and services currently run by RTS2. You can scroll through them using the up and down arrows.

As you scroll through the driver list the variable list on the right side will update. Each variable listed is associated with the highlighted driver or service. Most of the variables are read only but the variables that have a “W” next to the name are editable.

The logger at the bottom is the real time log of each diver or service.