What Software is needed and where?

There are six desktops. Each should run various pieces of software to succesfully operate the telescope and observe.

Each VNC window to mainz 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.

APF Telescope 1

  • eosDomeClient - started from a xterm on mainz

APF Telescope 2

  • TelescopeInterface - started from a xterm on mainz

APF Telescope 3

  • apfmon_gui & - started from a xterm on mainz
  • checkapf_obs & - started from a xterm on mainz, can be the same apfmon_gui

APF Instrument 1

  • apfmot_gui & - started from a xterm on mainz
  • apfmot_power_gui & - started from a xterm on mainz
  • ds9spec & - started from a xterm on mainz
  • autoload - started from a xterm on mainz, in ~/observing_scripts

APF Instrument 2

  • warsaw vncucam - start a xterm on mainz, ssh into warsaw, after running vncucam, if no UCAM interface, run ucam_launcher in an xterm

APF Instrument 3

  • dresden ds9guider & - start a xterm on mainz, ssh into dresden
  • dresden loadguideimage & - start a xterm on mainz, ssh into dresden
  • apfguide_gui - from a xterm on mainz
  • apfmidpoint - from a xterm on mainz

Table Of Contents

This Page