There are six desktops. Each should run various pieces of software to succesfully operate the telescope and observe.
Each VNC window to frankfurt has a name across the top. It will be APF, Telescope or Instrument, and a number from 1 to 3. Below I will list what each of these windows should be running and how to start that program.
- eosDomeClient - started from a xterm on frankfurt
- TelescopeInterface - started from a xterm on frankfurt
- apfmon_gui & - started from a xterm on frankfurt
- checkapf_obs & - started from a xterm on frankfurt, can be the same apfmon_gui
- apfmot_gui & - started from a xterm on frankfurt
- apfmot_power_gui & - started from a xterm on frankfurt
- ds9spec & - started from a xterm on frankfurt
- autoload - started from a xterm on frankfurt, in ~/observing_scripts
- warsaw vncucam - start a xterm on frankfurt, ssh into warsaw, after running vncucam, if no UCAM interface, run ucam_launcher in an xterm
- dresden ds9guider & - start a xterm on frankfurt, ssh into dresden
- dresden loadguideimage & - start a xterm on frankfurt, ssh into dresden
- apfguide_gui - from a xterm on frankfurt
- apfmidpoint - from a xterm on frankfurt