Logging on to kuiper kuiper is a pc running linux, where the observer is expected to use IRAF to display, examine and process the images obtained and transferred from the instrument computer, bigccd. Filter wheel commands and guider mirror positioning are also done from kuiper. username: bigobs password: on the white board the home directory is /home/bigobs to define a number of useful tasks: cl < mont4k.tasks (in an IRAF window) to observe with the Mont4k, you need several processes operating on kuiper (all may be initiated from the command line in separate terminal windows): 1) dataserver - accepts the images sent from bigccd and displays them 2) galilserver - communicates with the galil that moves the filter wheel 3) filter wheel gui - the interface used to see which filter is in the beam, and to change filters and optionally, 4) watcher - automatically converts incoming extended fits images to normal fits images, saving the originals in a subdirectory called raw. When kuiper first comes up, destroy any windows that automatically pop up (e.g., make sure that there are no ds9 windows open). Type dataserver in a terminal window. Dataserver brings up a ds9 window. Since the dataserver process is generally not running when you first login, you will have to kill any existing ds9 windows before starting dataserver (you must never have more than one ds9 window) - check to see if dataserver is running: ps -ef | grep server - if dataserver is not one of the existing processes, kill any ds9 window by clicking on the X in the upper right corner of the ds9 window and try starting dataserver again Galilserver needs to be running before the filter gui will work. If galilserver was not one of the processes shown with ps -ef | grep server - open a terminal window by right-clicking on the background and selecting "Open Terminal" - ping the galil network to see if it is up ping biggmc after a few lines, type -c; if the network is up, you should see a phrase saying "0% packet loss" - if the network is not up, you generally get "100% packet loss" - if it terminates and you get the bigobs% command line prompt, you need to see if the network connection to the galil is up, by typing ping biggmc after a few lines, type -c; generally, if it isn't working, you get 100% packet loss (ie no connection). If that happens: - kill any filter wheel gui window - go up to the dome, unplug the galil power cord and the two subsidiary cables/transformers next to it (the network connection and media converter); replug in the main power cable first, then the other two. You will hear the filter motor changing position to orient itself - go around to the other side, where you will see the red LED displaying "LOAD". (If no red LED, turn on the LED power switch.) The filter wheel always comes up in LOAD position, and the filters will respond to commands, but the filters may not be centered correctly in the beam unless it says "RUN #", where # is a number from 1-6 showing the filter position. When it says "LOAD", move the switch from the run position to the load position and back, until the LED says "RUN #". - back downstairs, retype "ping biggmc" in the terminal window and if the network connection is OK, then "galilserver". If either doesn't start, unplug and replug again. - type "galilserver" in the Terminal window; if everything is working well, then the last line of output should say "waiting for connection from clients"; also, when galilserver is running, you will see the existing galilserver process when you type ps -ef | grep server - start the filter gui from any terminal window using the command fw-gui The filter gui should pop up. If the filter gui window dies, or disappears, recheck galilserver, plug and unplug as before. Sometimes you only need to plug and unplug the two secondary plugs, not the main power cord. Whenever you have to unplug and replug the main galil power cord, you always have to change the filter switch from Run to Load and back to Run. - Minimize the terminal window (where you typed "galilserver", but don't kill it; you can always open it up if you want to see any galilserver error messages => hereafter, you can use the compound command (in any window) ps -ef | grep server ; ps -ef | grep gui to verify that all three necessary processes exist Move your windows to place them where you like them. If you resize the iraf windows, type stty xgterm so that iraf readjusts itself to the new window size. Within an IRAF window, start the mosaic reduction package by typing mscred This allows you to use the mdisplay and mexamine commands. Make yourself a data directory and move to it, for example mkdir green/23sep05 cd green/23sep05