Administrivia

1. Check conking.
   • Log into hqcronserver as user lris.
   • run conk-check lris
   • Verify that LRIS numbered accounts to be used during the next run have been conk-ed within the last 21 days.
   • If accounts require conking, manually initiate conking log into hqcronserver as lris and run the following command:

     	autoconk -f -m m -M M

     where m is the first account number to conk and M is the last.
2. Check rebooting.
   • Log into lrisserver as user lriseng .
   • Issue the uptime command to check how long the computer has been up.
   • If more than 7 days, request a reboot from sysadmin.
   • Be sure to run testAll when rebooting is done to verify that daemons came back up properly.
3. Check disk space.
   • Log into lrisserver as user lriseng.
   • run df
   • If one of the data diks is more than 50% full, we need to clean data from the disk.
   • Run datadirs all, check the output, and verify which directories need to be cleaned.
   • Confirm that the directories that need to be cleaned have been backed up by KOA before deleting files.
4. Check disk speed. Log into lrisserver as lriseng. Check the speed of the disks using the command

   	~lriseng/scripts/run_test_disk_io_speed

   Check the logfile in ~lriseng/log/test_disk_io_speed.log and see whether current I/O speed is in line with previous values. If not, then suspect a problem with the LRIS RAID array and seek assistance from sysadmins; this test is completely independent of the LRIS software and simply tests the time required to write data to disk.
5. Check image acquisition sequence speed. Bring up the LRIS software from lrisserver as lriseng using the background menu (LRIS Control Menu -> Start All LRIS Control). Check the speed of the image acquisition sequence by running the command

   	~lriseng/scripts/run_test_goi_time

   For each data disk, this will acquire 5 spectral-mode bias images and compute the time to write to disk. Check the resulting output in ~lriseng/log/test_goi_time.log, which looks like this:

   # date			disk		n	erase	wcrate	wdisk	total
   2006-Apr-11 19:43	/sdata1001	10     	8.44   	55.84  	1.54   	71.35  
   2006-Apr-11 19:54	/sdata1002	10     	8.44   	55.90  	1.54   	71.40  
   2006-Apr-11 20:06	/sdata1003	10     	8.44   	55.76  	1.48   	71.30  
   	  

   Compare the time required to complete various phases to what it took in the past. If problems are seen, check software and hardware:
   • unusually long erase time may indicate a problem with the CCD controller or deiccd keyword library
   • unusually long wcrate time may indicate a problem with the CCD controller
   • unusually long wdisk time could be a problem with the gathering of keywords or the write_image daemons
   • abnormally long total time could indicate a problem with lickserv2

Daytime Checkout

1. Check safety. Phone the summit and verify that LRIS is available for moving motors and rotating.
2. Start software. Log into lrisserver as lriseng and launch the instrument software.
3. Check CCD shutter. In an xterm on lrisserver, issue the commands

   cycle_shutter blue

   to verify that the blue shutter will open.
   Note that for now there is no way to open/close the red shutter via keywords.
   
4. Checkout instrument.
   Note: Currently grism and grating movements fail frequently. Move grism to clear and grating to mirror first before
   running the checkout script. Otherwise the checkout script will likely fail at the first try.
   Acquire an image on each side of LRIS using the

    lris_checkout

   command. Inspect the resulting images to ensure that they look correct. This script will try to power up the instrument and guiders and restart the GUIs. So please select the most suitable answers. If the monthly checkouts have been started as described here, then we can proceed without repowering the instrument and guiders. Also there would be no need to restart the GUIs.
   
5. Check internal lamps.
   • As lriseng@lrisserver, execute the script ~lriseng/scripts/test_lamps script, which will:
     • Insert any available longslit mask.
     • Insert 1200G at 7800A plus OG550 filter
     • Configure CCD for spectroscopy
     • Acquire 1s exposures on each lamp after 30s warmup (180s for some lamps). The scripts turns one lamp at a time.
   • Verify that you get light from each lamp by checking for a spectrum on the corresponding image.
   • Whether or not lamps are working, recommend asking summit staff to perform visual inspection of the lamps while "ON" in order to verify that all are working. It is common to have one of the pair of lamps burn out and not know it for months!
6. Adjust science CCD bias. (Optional)
   • As lriseng@lrisserver, execute the following ssh lriseng@vm-k1guiserver "xterm -e lrizzi/calculateVidoff.py" script, which will:
     • connect to a python server for LRIS
     • Take a blue bias
     • Calculate the new bias offsets needed for a flat image
     • Determine if new voltage offsets are needed and ask if they should be changed.
   • if changes are made to the vidoff keywords, look at their values with: show -s lrisblue VOFFSET0 VOFFSET1 VOFFSET2 VOFFSET3.
   • Edit the content of ccdbiasb as lrisdev@lrisserver by using emacs /kroot/src/kss/lris/lris_sh/procs/ccd/ccdbiasb
   • commit the changes by issuing
     • lrisdev@vm-svnclient
     • cd ~/svn/manuka/kss/lris/lris_sh/procs/ccd
     • make install
     • svn commit -m "LRIS: modified ccdbiasb" ccdbiasb
7. Checkout stages. (Optional)
   • Execute the checkout_lris command on lrisserver to verify that all movable stages are working well.
8. Check CCD parameters. (Optional)
9. Check guider.
   • Login to k1server as k1obs
   • go to: cd magiq/lris
   • execute the command: ./rununstickOffsetGuiderIQL
   • this command resets the galil (ignore the error message), and then moves the IQL in and out
   • It will then ask you to confirm that the IQL is moving by providing you with the expected and measured encoder position
   • if the measured encoder positions are within 50 counts of the expected ones, answer yes, otherwise answer no
   • if you answer no, the procedure will be repeated
   • Note that if you do NOT reset the galil with this procedure, all the other offset guider motors might be disabled (filter for example)