Table of Tasks (annotated)

An idea for describing the critical path workflow for all parties. We expect the Run Manager to start his duties around lunch time and to be around for the first half of the night. The observers should be in the console room for the 4 pm meeting.

Task Observer 1 Observer 2 Run Manager TelOps Time Links to information
Lunch X X X X 1-2pm
Address Questions/Comments from Previous Night X 2pm check desops email list
check various systems (diskspace, etc.) X 2:30pm
perform data quality assessment X 2:30
Make Plan X 2:30pm email plan to desops:
Restart SISPI (X) X 3 pm
Organize Roles X X X 3:30pm
Set up O1 station (X) X 3:45 pm
4pm Meeting X X X X 4pm
Set up O2 station X (X) 4:30pm
Check Dome closed X 4:30 check with telops or go outside
Zeros/Flats/Calib X 4:45 pm In order to end before we go to dinner
Check Flat Quality X 5pm
Note: flatCheck will check all available flats
help: what range of counts is OK for each band?
Start Night Summary and Report X 5:15pm
submit afternoon checklist (elog) X 5:30 (when calib ends)
Open Dome (make sure vsub is off; X about an hour before sunset; when sun = 20deg altitude ask telops to open dome
Dinner X X X X 6 - 7pm
Load Standard star Scripts X X X 7pm
Load bad exposure scripts X 7:15pm ????
Watch sunset! X X X X 7:30-8pm
turn Vsub on; Hit GO to execute flush script loaded earlier X sun at -10 degrees
set z trim X
Check Zeropoints X X
Run Standards X After zeropoint check
Run Observations; don't forget to hit Go! X X (when standards finish)
Submit start of observing checklist (elog) X
(AM Calibrations: only if necessary) X
Submit Night Summary and CTIO Report X sun at -14 deg
makes sure to click "textile format" if your report is in that markup
end of night checklists X X 6am
Conclude Night X
Watch sunrise in a state of sleepless delerium

Table of Things to check periodically

Task Observer 1 Observer 2 Run Manager TelOps Frequency Links to information
Telemetry X 1hr ???
Humidity (FCM) X 30min If above 1%, alert RM
Exposure Queue X 30min Are the exposures taken consistently
Check Image Health, Compare to QR, KT X X 1hr if bad, alert RM
Compare QR and KT PSF X 1hr if bad check, guider;
Wind X 30 min
Humidity (outside) X 30min if above 70% prepare to close dome; check with Telops
Guider X 30min

Table of Checklists and things to log in order of performance

Checklist/Forms/Logs Where to log Observer 1 Observer 2 RM
Afternoon Checklist E-Log; afternoon checklist X
List of calibrations E-log; decam logbook X
start of observing checklist E-log; X
Zeros E-log; decam logbook (X) X
Pointing/centering e-log; decam logbook (X) X
Standards e-log; decam logbook (X) X
Obstac start e-log; decam logbook (X) X
SISPI/TCS issues e-log; decam logbook X
Image quality e-log; decam logbook X
End of Night Check list e-log; end of night checklist X (X)
Night Sum e-log; synopses; and additional cmd line run X (X)
CTIO Night Report website X (X)

List of altitudes when it's okay to do things (a matter of safety and timing).

  • -5 sun altitude evening twilight : absolute earliest to turn on vsub, no need to do it at that point
  • -10 sun altitude evening twilight : earliest to do centering.
  • -12 sun altitidue evening twilight : standards (do 3 exposures for focusing update)
  • - XX sun altitidue morning twilight : latest for
  • - XX sun altitidue morning twilight : latest for

Guider Test


  • where is star flat field information?
  • set GCS image_directory to what?
  • where do we set up dither?
  • where do we set guider exposure mode (exposure control?) ?


  • bad seeing is ok, but need to be able to detect enough stars per CCD
  • need a few minutes
  • dither by 1 arcmin
  • multiple filters at each loc.


  • set exposure type to "guider"
  • set GCS image_directory
  • take a few images in star flat field in guider exposure mode
  • go to engineering ops page for more instructions: from sv wiki
  • set proposal id to something new 2013A-9999 (engineering prop id)

Instructions from email:

For these guider-astrometry tests, we need the exposures to be in one of the star flat fields, because these are places where we have high-quality astrometric positions for stars outside the DECam science FOV.
Twilight might be worth a try - we need to have a few dozen good-S/N stars per CCD to get this job done. When we solve for astrometry on the science array we have hundreds of stars per chip, but we could live with lower accuracy here.
Bad seeing is ok but again we need to be able to detect and measure enough stars per CCD.

On Oct 23, 2013, at 3:17 PM, Thomas Diehl <> wrote:

If we get a chance - for a few minutes - a useful test would be to take a few images in a
star field (like the ones we use for star flats) with the guider exposure mode. Ideally with
multiple filters if there is enough time and dithered by 1' or so as described in the
instructions. It's very important that you set the GCS image_directory before doing this.
There is no script so it has to be done manually. The exposure sections allows you to choose
"guider" for the exptype and you can enter offsets for the dither. With this data, Gary can
find the astrometric solution and this will give us the location of the guider CCDs with arc
sec precision. We don't' have this right now and it's needed before we can try the guider in auto mode.
Tom: Don't know if conditions will permit tonight.
Tom: Bad seeing but can get guide stars?
Klaus Honscheid: Maybe this could be done during twilight?