Daytime Checkout Before Every Run

No mechanism moves and no lamps required

  1. Check conking. Log into hqcronserver as user esi. Verify that ESI numbered accounts to be used during the next run have been conk-ed by using conk-check esi to check the conk date. Manually initiate conking on unconked accounts by logging into hqcronserver as esi and running 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 esiserver as user esieng . Issue the uptime command to check how long the computer has been up. If more than 7 days, request a reboot from sysadmin. Repeat this check for esiserver2.
  3. Check disk space. Log into esiserver as user esieng.
  4. Check disk speed. Log into esiserver as esieng. Check the speed of the disks using the command 
    	~esieng/scripts/run_test_disk_io_speed
    Check the logfile in ~esieng/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 ESI RAID array and seek assistance from sysadmins; this test is completely independent of the ESI software and simply tests the time required to write data to disk.
  5. Check image acquisition sequence speed (7 minutes). Bring up the ESI software from esiserver as esieng. Check the speed of the image acquisition sequence by running the script 
    	~esieng/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 ~esieng/log/test_goi_time.log, which looks like this: 
    # date                  disk            n       erase   wcrate  wdisk   total
# ----                  ----            -       -----   ------  -----   -----
2010-Jun-06 17:19       /sdata700       5       11.44   38.96   4.16    60.66  
2010-Jun-06 17:24       /sdata701       5       11.45   39.79   3.04    59.63  
2010-Jun-06 17:29       /sdata702       5       11.44   39.28   4.24    60.81  
2010-Jun-06 17:34       /sdata703       5       11.46   39.84   3.74    60.48  
2010-Jun-06 17:39       /sdata704       5       11.44   39.81   4.31    61.03  
2010-Jun-06 17:44       /sdata706       5       11.44   39.81   3.77    60.43  
2010-Jun-06 17:49       /sdata707       5       11.43   39.54   3.75    60.31
    Compare the time required to complete various phases to what it took in the past. If problems are seen, check software and hardware:

Mechanism moves required, no lamps

  1. Check safety. Phone the summit and verify that ESI is available for moving motors, including opening the ESI hatch
  2. Start software. Log into esiserver as esieng and launch the instrument software.
  3. Home motors.

    NOTE: This will open and close the ESI hatch. Ensure summit personnel near ESI are aware.

    1. Click the Start Here button on the ESI dashboard window to access the Setup/Options panel.
    2. Click the INITIALIZE INSTRUMENT button to get the INITIALIZE INSTRUMENT panel.
    3. Click the button reading Yes, I Really Want To Initialize ESI! to start homing motors.
    4. Wait while homing completes (about three minutes).
    5. Verify that all stages home properly. If a stage again fails to home, you may need to enlist the help of summit personnel to fix it.
    Note: if you encounter trouble, you can try to execute the initialization from the command line using this syntax: 
    /opt/tcl803/bin/tcl /kroot/bin/ktrun /kroot/data/esi/Tests/ESIinit
  4. Check CCD shutter. In an xterm on esiserver, issue the command 
    	cycle_shutter -100
    to verify that the shutter will open. You will initially see errors reported, but the final lines should read: 
    setting cshutter = open (wait)
setting cshutter = close (wait)
  5. Check CCD bias.
  6. Check triple wheel renishaw encoder voltages (3 hours).

Mechanism moves and lamps required

  1. Check safety. Phone the summit and verify that ESI is available for moving motors, including opening the hatch.
  2. Start software. Log into esiserver as esieng and launch the instrument software.
  3. Home motors.

    NOTE: This will open and close the ESI hatch. Ensure summit personnel near ESI are aware.

    1. Click the Start Here button on the ESI dashboard window to access the Setup/Options panel.
    2. Click the INITIALIZE INSTRUMENT button to get the INITIALIZE INSTRUMENT panel.
    3. Click the button reading Yes, I Really Want To Initialize ESI! to start homing motors.
    4. Wait while homing completes (about three minutes).
    5. Verify that all stages home properly. If a stage again fails to home, you may need to enlist the help of summit personnel to fix it.
    Note: if you encounter trouble, you can try to execute the initialization from the command line using this syntax: 
    /opt/tcl803/bin/tcl /kroot/bin/ktrun /kroot/data/esi/Tests/ESIinit
  4. Check internal lamps.
  5. Check focus settings (2 hours for full, 40 minutes for quick).

Daytime checkout Occasionally

Mechanism moves and lamps required

  1. Check CCD parameters. [TBD]
    Don't perform these tests yet; scripts to be written to automate. Below is a list copied from DEIMOS.
  2. Check guider.
  3. Focus guider. Use this procedure to acquire and analyze focus sequences for each of the ESI TV filters. To check the full complement of filters requires 1-2 hours from start to finish, but the R-band filter can be checked in a few minutes.
    Approximate TV focus offsets (from R-band)
    TVFILNAM Focus Offset TVFOCRAW (2021-10-07)
    R0-2000
    B0-2000
    V0-2000
    I-43-2043
    Clear+680-1320
    ND_1+260-1740

Nighttime Checkout

These procedures are run at night to calibrate the instrument.
  1. Check throughput (procedure for DEIMOS, not ESI) Note: would useful to have 3 or 4 chosen standards spaced in RA such that at least one is always accessible