Observing Plan for the August 15, 2013 Engineering Night

Proposal Id: 2013A-9999
Exposure Scripts: Most of the exposure script for this night are available in ~DECamObserver/ExposureScripts/engineering_20130815
(from the Observer Console GUI select Exposure Control --> Load Exposure Script --> Choose File)

(Late) Afternoon

Full set of zeros and dome flats
Script: DECam_prenight.json (note that this is a (standard) DECam script. From the the Observer Console GUI select Exposure Control --> Load Exposure Script --> Select DECam Script then choose DECam/DECam_prenight.json in the dialog window)

Filter Baffle Tests

no instructions. Alistair has a plan


Instructions from Gary

Getting high stellar density for the star flats means doing this in the first half of the night since the Galactic plane is down very low in the 2nd half of the night.  
Here are two possible starting positions for the star flat sequence:

   RA=19:00:00  DEC=-50:00:00 (sets at about 02:00 local time)
   RA=20:40:00  DEC=-35:00:00 (less preferred but usable until about 03:30 local time)

Would you or someone else be able to script a sequence that starts at this position and then takes a series of exposures with the offsets in the attached file? 
The 1st and 2nd columns in the file give the *differential* offset with respect to the previous pointing, i.e. just what you need to give to the TCS. 
We could have such a script for each of the g, r, i, z, and Y filters.  I think it's ok to shorten the sequence to 30s per exposure.  
There are 22 exposures in the sequence, so 5 x 22 x (30+30)s = 110 minutes to do this whole thing.
If we can't do this before the setting time of the above fields, then we can do it just about anywhere that is visible at the time as all high-latitude fields are 
going to be similar to each other.

The 5 scripts can be found in the engineering_20130815 folder. They are named Starflat<filter>.json_
These are relative scripts which means the telescope has to be moved to the field manually (and moved back to the starting position between scripts unless Gary's offsets add up to a closed path)

SN Pointing Studies

First we need to test the SISPI code modifications under manual control (architect_console and observer_console GUIs)
  • Test 1: Extra focus/alignment exposure using wait=autocorrect
  • Test 2: AOS trim compensation using compensate_trim=true
  • Test 3: Switch to AOS-1 mode using aos_mode=SN

Once the code works reliable run the three sn_test scripts from the engineering_20130815 directory


2 exposures, z band, 30 seconds, the first has wait=autocorrect set and the target coordinates, the second is a regular exposure at the same position.
The target coordinates are RA 20:30:00, DEC -5:00:00 if the test is run around 11

slew telescope 1hr west of target, run script
slew telescope 10 degrees north of target, run script
slew telescope 1hr east of target, run script
slew telescope 10 degrees south of target, run script
repeat if time permits
(we don't have a scriptable slew command (something to add to the to do list). I expect asking to operator to move between scripts is faster than adding dummy exposures just to move the telescope)

compensate_trim and aos_mode tests

run sn_test_baseline.json - 30 second, z filter, regular exposures at HA -2, -1, 0, +1, +2 and DEC -5, -10
run sn_test_compensate.json - same sequence but with compensate_trim=True
run sn_test_aosmode.json - same sequence but with aos_mode=SN


Confirm that the new version of obstac runs
Test SN trigger (Eric will provide details)

Image Quality

Run the RXJ2428_.json script to take 1 focus/alignment +10 90 seconds i-band exposures of this cluster.
Best (lowest airmass) to run this around 2 - 3 am local time.

Regression Script

Regression_Observation_All_Absolute.json is a version of the standard script that uses absolute coordinates for every exposure. It can be found in the engineering_20130815 folder.

Regression_Observation_All_Compensate.json is a version of the standard script that uses the compensate_trim=True flag for the exposures with the long slews. It can be found in the engineering_20130815 folder.

There won't be enough time to run these scripts to completion. It's okay to abort one or both of them.