1) Login to clio using the command “ssh obs@clio.mmto.arizona.edu -X -Y -C”

Make sure you have talked to the previous observer or email Phil Hinz to get the password.

2) Type “runclio” to start the various programs.

“runclio” is a link to mirkwood.sh in the Programs directory. This in turn is a shell script which runs mirkwood (the clio control program), ds9 (the image display program), Cliomotors.tcl (the filter control program), starnudger-Clio.tcl, (the telescope paddle control), statcurrent.tcl (the statistics display program), and transferfiles.sh(Backs up files to zero in Tucson). The programs as they should appear on your desktop are shown below

If any of the software components stop responding or crash, they can be restarted or rest using the GUI in the lower right hand of the display.

3) Initialize the camera by clicking “Init" on the Clio Camera Control GUI.

The button should turn from red to green.

4) Make sure the “AO/Tel. info in header” check box is clicked

NOTE: IF THIS IS NOT TURNED ON YOU WILL NOT HAVE TELESCOPE INFO IN YOUR FITS FILES

5) Check that the data directory is set to /home/obs/Data/n(year)(month(UTnight). As of October 2010, this should be automatic.

For example on the evening of October 7, 2010 I would set the directory to /home/obs/Data/n101008, since the UT data is 1008 starting at 5 pm on October 7. While other directories can be used, setting this is important for automatic file backup to Tucson. You can see the operation of this script in the terminal on the bottom of the screen. It will copy data in ten minute intervals. If there is concern about this script interrupting camera operations, this can be stopped at anytime simply by killing the terminal, but it should be restarted at the end of the night to ensure the data is backed up.