Background

This document describes the process of handling DEIMOS observing configuration requests. It is intended for use by the DEIMOS support astronomer.

Procedure

Receive config

Observers submit instrument configuration requests using the online run configuration form. This generates an email to the support astronomer; for example:

    From: NFS Anonymous Access User <nobody@www2.keck.hawaii.edu>
    To: deimos@keck.hawaii.edu
    Subject: DEIMOS config form for Engineering
    Date: Thu, 5 Jun 2008 16:40:37 -1000 (HST)

    PI Name = Engineering
    PI Email = foo@b.com
    Date = 2008-07-06
    Observing Requests = 

    Longslit     = 1
    Multislit    = 
    Imaging      = 1
    SLITMASK1 = Long0.7  BC =4318 
    SLITMASK2 = LVMslits  BC =4817 
    SLITMASK3 = indef  BC= NONE 
    SLITMASK4 = indef  BC= NONE 
    SLITMASK5 = indef  BC= NONE 
    SLITMASK6 = indef  BC= NONE 
    SLITMASK7 = indef  BC= NONE 
    SLITMASK8 = indef  BC= NONE 
    SLITMASK9 = indef  BC= NONE 
    SLITMASK10 = indef  BC= NONE 
    SLITMASK11 = GOH_X  BC =487 
    GRATING1 = indef
    GRATING2 = Mirror
    GRATING3 = 600ZD
    GRATING4 = 1200G
    FILTER1 = R
    FILTER2 = GG400
    FILTER3 = GG455
    FILTER4 = GG495
    FILTER5 = OG550
    FILTER6 = indef
    FILTER7 = indef
    ----------------------------------------------
    WARNINGS: Multislit mode was not requested, but a multislit mask was requested.

Save this email for future reference.

Run checknerds2

The SA runs the checknerds2 command to record the receipt of the slitmasks and configuration form.

First you see the menu:

    gwirth@kapoho:~% checknerds2

    DEIMOS Observer checklist for 12-Jun-2008 

                                               Days Num  Config       Slitmask    
    PI                        FirstNight  ID   Till Msgs Status       Status      
    Tonry                      4-Jul-2008 11309   22    0 received     none        
    Tonry                      5-Jul-2008 11311   23    0 received     none        
    Engineering                6-Jul-2008 11313   24    0 
    Yamada                    29-Jul-2008 11359   47    0                          
    Yamada                    30-Jul-2008 11361   48    0                          
    Tonry                     31-Jul-2008 11363   49    0                          

    Enter ID number to change (return to quit):

In this case, enter 11313 to edit the entry for the Engineering night. The next prompt is:
```
    Enter Number of reminder messages sent [0]:
```
Just press Enter to skip.
The next prompt is:
```
    Enter Cfile status []: 
```
Enter received to indicate that the configuration was received.
The next prompt is:
```
    Enter Slitmask status []: 
```
Enter either received if slitmasks are specified, or none if only longslits are requested.
Repeat these steps for any addition night in a multinight observing run.
Press Enter again to quit the program.

Create Configurations

At least one day prior to the DEIMOS run, edit the SIAS to put the configuration on the schedule.

Go to the SIAS web page.
Select the starting date of the run. NOTE: for the first day DEIMOS is on the telescope, you should enter the configuration at least one day prior to the run so that the summit staff can complete the task in advance.
Click on Add and select DEIMOS Config change.
You will be shown the default DEIMOS configuration for that date based on previous entries in SIAS. Edit this entry to reflect DEIMOS configuration information from the config form. See note below about slitmask changes.
Click on Create to save the task on SIAS.

Note About Slitmask Entries

A useful routine can help ensure that slitmask information is properly entered onto SIAS; however, it can only be run after the DEIMOS has been recongfigured on the day prior to the run you want to edit. To use it:

Log into polo as dmoseng.
Type the command masklist followed by slitmask names or barcodes.
The script will:
- Read the barcodes for the current DEIMOS slitmask configuration.
- Convert any mask names you provided into barcodes (and warn if unable to do so).
- Generate a new slitmask configuration accounting for any requested masks which are already loaded.
The resulting output can be pasted directly into the appropriate place in the SIAS.

Here is example output from the script:

    [66] dmoseng@polo: masklist xlh84 xlh85 xlh86 GOH_foo
    WARNING: interpreting guiname xlh84 as barcode 4729
    WARNING: interpreting guiname xlh85 as barcode 4728
    WARNING: interpreting guiname xlh86 as barcode 4758
    WARNING: interpreting guiname GOH_foo as barcode 487
    Slitmask  2: xlh84 BC=4729
    Slitmask  3: xlh85 BC=4728
    Slitmask  4: xlh86 BC=4758
    Slitmask  5: 5003.W BC=4790-no change
    Slitmask  6: 5100.E BC=4795-no change
    Slitmask  7: 5105.E BC=4780-no change
    Slitmask  8: 5134.E BC=4830-no change
    Slitmask  9: 5135.E BC=4840-no change
    Slitmask 10: LVMslits BC=4817-no change
    Slitmask 11: 6243.W BC=4843-no change
    Slitmask 12: GOH_foo BC=0487-no change

Note that mask 487 (GOH_foo) was already in DEIMOS and thus it was marked as -no change. The lines starting with Slitmask can all be cut and pasted into the SIAS entry for that day.