DRAFT - Observing Plan for MJD 56329 (starting evening of February 05 2013)


Observer 1 Observer 2 Run Manager Run Manager Trainee
March Casas Nord Rooney

DECam Configuration and Setup

SISPI Configuration File sv.ini
Proposal ID 2012B-0003
Image Processing (Calibration) NCSA
Image Processing (First Cut) NCSA

CTIO Report Information


PROPOSAL 2012B-0003
SEEING SOURCE The Telescope I used

Late Afternoon Checklist

In E-log; form = late afternoon checklist
Item description example
Observers Observer names BNord, MMarch
Running SISPI instance name DECam_<date instance started> DECam_20130205
Afternoon Calibration Script Name find under SelectDECam script DECAM/prenight_zeros_flats
Execute daily procedure empty n/a

Beginning of Night Checklist

In E-log; form = Beginning-of-night Checklist
Item description example
Observers Observer names BNord, MMarch
Time Evening Twilight Ends time when sun half sets see almanac below
Time Morning Twilight Begins time when sun half rises see almanac below
SISPI Interlocks failed which piece of SISPI didn't work or caused red buttons Hexapod
Check if Afternoon Calibration was completed ask Run Manager yes/no
RASICAM ok? open up rasicam webpage adn look for errors n/a
skip the rest

Almanac and Weather

Sunset: 20:46
Twilight Ends: 22:06
Twilight Starts: 05:48
Middle of night handover to community at 01:58
Moon Rise: 3:09
Moon Set: 16:39
Moon Illum.: 22%
Expected Weather: Clear


Plan and Goals for the Night

Main Questions (duplicated below):

  1. What if seeing > 1.3 and airmass for SN fields is too high (> 2)? What should be observed? ALL obstac, as much as possible.
  2. When should AOS be turned on? (Before calibrations? or just before first obs?): We'll do it at the beginning of the night
  3. Nord needs sispi@observer2 password to run Nightsum got it from Eric, thanks!
  4. There is an "End-of-Night" Form in the E-log. Do we fill this out? Didn't find a policy on this last night. No

Observing Plan (Obs1)

  1. Afternoon calibration data
  2. Calibration observations (Douglas Tucker): Standard Stars
    1. Attached (FebStds.txt) is a list of night-by-night suggestions for the rest of the DES time, assuming the normal evening twilight times and a single standard star field just before middle-of-the-night switchover.
    2. Currently, we are observing 3 standard star fields in evening twilight -- at least one and preferably more in SDSS Stripe 82 -- and one more just before switchover. For the 3 standard fields observed during evening twilight, one should be at low airmass (<1.25), one at medium airmass (1.25-1.65), and one at high airmass (1.65-2.10).
      and, if SDSSJ0100-0000 does not appear in the resulting table, replace it with an observation of the E2-A prenight script
      1. back to grizY, not ugriz (we don't need u's because chip offsets are done)
    3. See the SV "extended SV schedule" page for instructions on how soon you can begin standards and sky observations.
  3. Obstac (Eric Neilsen):
    1. If seeing is <1.3 arcsec, run in auto-mode to observe SPT-E mini-survey.
  4. SN priority observations (Masao):
    • c3 fields [griz]
    • x2 fields [griz] (Please do X2 only if seeing is consistently >1.3". This visit won't be useful for spectroscopic targeting, but we can get one last point in the tails of the light curves.)

Analysis/Support Plan (Obs2)

  • QuickReduce Work (see email from A. Fausti)
  • Centroids and Guiding (see requests from K. Honscheid, T. Diehl)
    • please keep an eye on the guider traces and try to estimate the rate at which oscillations appear vs declination of the target. We would like to see how the horseshoe damper motor upgrade is influencing tracking issues.
  • Monitor PSF and Guider


WorkFlow Decisions

Seeing Policy

  • If seeing > 1.3 :
    • if not clear (clouds):
      • if SN fields up (airmass < 2): then SN
      • if SN fields down : then obstac
    • if clear : then do half-chip offsets
  • if seeing < 1.3 : obstac

Wind Speed

  • if 5 < speed < 15 : raise wind screen to 30%
  • if speed > 15 : close louver


  • SN fields only
    • if off by 10 in either direction: shift coordinates, don't recenter (getting offsets via kentools)


Detailed Workflow

Below, we show the detailed workflow for each part of the n ight
  • >> = buttons to hit
  • $ = prompt


Workbench Setup

  1. restart sispi (beware multiple locations are involved in this);
    1. Should be in (this step is often already complete)
      1. $ ssh sispi@system1.VNC to system1:
      2. >> open terminal in system1
      3. $ vncviewer system1:2
      4. $ enter password (ask RM)
    2. $ cd ‘sispi/decam/architectures/ctio/’
    3. $ setup SISPI
    4. $ shutdownSISPI DECam_<date of instance>
      1. alternative for this step: go to architect console and click ‘Shutdown’
    5. clean up
      1. $ cleanup_ramdisk
      2. $ cleanup_processes -k
      3. $ check_diskspace
    6. start sispi ( ‘ ONLY DO THIS IS THE SISPIUSER terminal!); Windows will start popping up after a few minutes.
      1. $ architect -c sv.ini
        1. Wait till all the PanView windows are up
        2. >> then open a new SISPI GUI, using the DES logo in the main menu bar
    7. Log-in to observer console
      1. >> login: DECamObserver
      2. >> password: ask RM
    8. Setup System Control
      1. >> System Control
      2. >> Enter Observer names
      3. >> Enter Proposal ID: 2012B-0003
      4. >> SAVE (will propagate remaining info that's greyed out)
    9. >> Configure [in Observer Console]
  2. Setup Observer 2 Terminal (can happen simultaneous to the above)
    1. check speed of machine; kill processes if necessary
    2. >> open terminal
    3. start kentools
      1. $ observer
      2. test previous exposure
        1. $ load
        2. $ seeingall
        3. $ center


Initial Calibrations

  1. Take junk (zero) exposures ('2' as indicated below) (to clear out hot pixels)
    1. >> Observer Console
    2. >> System Setup
    3. >> Turn VSub On [on far right side]
    4. >> Exposure Control
    5. >> Manual
    6. >> Enter in field: type=zero,object=junk,dtsqueue=none,count=2
    7. E-log default (Obs2 request Expids from Obs1)
      1. vsub on
      2. Zero/Junk Exposures:EXPID range
  2. Set up calibration exposures
    1. check with TelOps that the Flat screen is lined up
    2. >> Load Exposure Script [ Obs con]
    3. >> Select DECam Script
    4. >> Choose "DECam/prenight_zeros_flats"
    5. >> ADD
    6. >> GO
    7. Edit Queue
      1. remove 20s r-band exposures, because they are over-exposed
        1. click on an exposure and hit the delete button
    8. E-log: Use Afternoon Checklist (get expid range from Obs1, or from looking at Obscon on personal machine)
      1. comment that r at 20s were removed
      2. comment that we're using uband because the half-chip offsets are being used
      3. comment Expids (get from ObsCon or Obs1)

NIGHT (starting after dinner after sunset)

  1. turn on AOS ( ???:
    1. init_pid 2
  2. indicators to start nighttime observations
    1. Sun angle < -9.7 deg
    2. TelOps gives bright star or ask telops when the sun angle
  3. check center
    1. take an exposure of the bright star
      1. >> Exp form
      2. >> enter: type = object; time =10; count = 1; filter = r (?)
      3. >> add
      4. >> go
    2. check center offset [Obs 2]
      1. center EXPID [at observer 2 in kentools]
      2. re-center telescope if offsetx or offsety > 10 arcsec
        1. tell TelOps and Obs1 the new center
        2. wait for slew to complete
        3. repeat center check
    3. E-log the full list:
      1. Bright Star: expid, filter
      2. Offset RA, Offset Dec
      3. Bright star: expid, filter
      4. Offset RA, Offset Dec
      5. etc.
  4. choose standards
    1. >> source ~/dtucker/bin/setup_StdStarFieldPicker.csh
    2. >> --UT='2013/01/30 00:43'
      1. (replacing with the time the standards sequence will start)
      2. if SDSSJ0100-0000 does not appear in the resulting table, replace it with an observation of the E2-A prenight script
    3. >> Choose File
    4. >> go to DECamObserver/ExposureScripts/FEB2013Standards_uband
      1. use the u-band because the half-chip sets use the uband
    5. Choose the fields here based on having run the above decamStdFieldsTimeDate script and teh requirements there.
    6. >> add
    7. >> Go
    8. go to the second in this sequence and re-do for each of hte three standards fields.
    9. E-log: all standards at once
      1. Standards field (including u-band?):
      2. script name for each field
      3. expid range for each field
      4. airmass for each field (get from ICS or OBS1)
  5. Half-chip offset fields
    1. >> DECamScript
    2. use DES/SN-halfCCDoffsetSequence_E2_ugrizY
    3. >> submit
    4. E-log:
      1. Half-chip Offsets
      2. Field: Field Name
      3. Filters: filters
      4. Expids: Expid List
  6. SN fields
    1. go to field via slew script
      1. >> Load Exposure Script
      2. >> Select DECam Script
      3. >> choose DES/XX-slew.json
    2. wait for slew to finish
    3. check center (OBS2)
      1. center <EXPID>
    4. add ra dec offsets in arcsec
      1. >> Exposure Control
      2. >> set RA to DeltaRA
      3. enter offsets in arcsec
    5. select field script
      1. DES/sv_sn_XX_griz.json
    6. >> submit
    7. >> ADD
    8. >> go (if necessary)
    9. set slew for next field (just as above)
    10. repeat center check until within 10 arcsec x and y
    11. E-log for SN fields
      1. SN field
      2. Field: Fields
      3. Filters: filter
      4. Expids: Expid list
      5. repeat SN exposure if available
    12. End-of-Night Standards
      1. >> Observer Console
      2. >> Load Exposure Scripts
      3. >> DECamScript
      4. >> Choose File: DES/postnight_flats_zeros.json
      5. >> submit
      6. >> add?
    13. E-log for EON standards
      1. EndofNight standards
      2. Field: Field Name
      3. Filters: filter names
      4. Expids: expid list
      5. repeat to put all E.o.N standards in one log

End of Night

  1. CTIO Night report (
    1. log in to page
      1. login: astronomer
      2. password: ask RM
  2. Turn off AOS
    1. init_pid 1
  3. Make Night Sum
    1. (
    2. fill out logbook with tags, Synopsis_Night, Synopsis_Problem, Synopsis_Engineering (no need to fill out end-of-night checklist)
    3. Make and Publish Nightsum
      1. log into observer2 as user sispi
      2. set up the environment:
        $ setup nightsum
      3. run the makesum script:
        $ cd ~sispi/nightsum-reports
        $ makesum
      4. The step above will create a dir named nightsum-<MJD>. Check the results by pointong your browser to
      5. Go to the logbook and make changes as needed. Repeat the makesum step until you are happy with the results.
      6. Then, publish the results so it shows up on the web server on
        $ cd ~sispi/nightsum-reports
        $ pubsum