DRAFT - Observing Plan for MJD 56328 (starting evening of February 04 2013)


Observer 1 Observer 2 Run Manager
March Rooney Nord

DECam Configuration and Setup

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

Almanac and Weather

Sunset: 20:47
Twilight Ends: 22:07
Twilight Starts: 05:48
Middle of night handover to community at 01:57
Moon Rise: 2:10
Moon Set: 15:37
Moon Illum.: 61%
Expected Weather: Clear

Plan and Goals for the Night

Observing Plan (Obs1)

  1. Afternoon calibration data:
    1. dome flats including u-band in case we get to the half-chip SNe observations.
  2. Calibration observations (Douglas Tucker):
    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).
    3. BEFORE taking/queuing the evening twilight standards tonight, do a quick check by running on observer2:
      source ~/dtucker/bin/setup_StdStarFieldPicker.csh --UT='2013/01/30 00:43' (replacing with the time the standards sequence will start)

      and, if SDSSJ0100-0000 does not appear in the resulting table, replace it with an observation of the E2-A prenight script
  3. Obstac (Eric Neilsen):
    1. If seeing is <1.3 arcsec, run in auto-mode to observe SPT-E mini-survey.
  4. Half-chip SN observations (Huan Lin):
    Exposures of each SN field taken with 1/2-chip shift from normal pointings, to reconcile the photometric systems. They can be done in poor seeing but should not have clouds. On the night these are done, you will need to take u-band dome flats and add u-band to the standards as well. These exposures are lower priority than obtaining the regular SN observations above. No need to re-center??? Huan will let us know if we should check centers or offset.
    1. E2 (only if there is time; check if not too low)
  5. SN observations (Masao):
    • old: If seeing is poor and we have thin clouds, we can do another visit of X2 griz.
    • *new [as of today's SNWG telecon]: priorities are *
      • s1/s2 fields [griz]
      • c1/c2 fields [griz]
      • x2 fields [griz]

Analysis/Support Plan (Obs2)

  • QuickReduce Work (see email)
    • From email from (A. Fausti): In addition to the global mean reported at the observing history, you can click on the corresponding exposure and look at the median and rms of the psf fwhm for each ccd, this info is available at the "Requirements" tab. For the exposure you mentioned 174023 the ccds with mininum and maximum fwhm values are
      • 9 (S21) 1.49 ± 0.08 and 60 (N29) 1.64 ± 0.06
      • which suggests a variation of 0.15 arsec across the focal plane. At the "FOV properties" tab there is a plot showing the median psf fwhm vs. the ccd number (attached)
      • I think it is a good idea to monitor ccd 18 (S19) I have noticed this large rms for some other exposures in the past - could you select this ccd tonight?
  • Centroids and Guiding

Notes from the 4PM Meeting and Additional Comments

  • 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.
  • No need to fine-tune the pointings for the SN exposures that will have the half-chip shifts.
  • Keep an eye on the wind speed, especially when the dome is facing upwind (usually North). Alistair noted winds easily inducing telescope motion (again you can watch the guider traces). Basic instructions: for winds > 5-8 mph, raise the wind blind to cover ~ 30% of the telescope. For winds >15 mph, close the louver windows in the dome as well.
  • See the SV "extended SV schedule" page for instructions on how soon you can begin standards and sky observations.

What other tasks could an idle Observer2 work on?

Discuss at SV mtg.
  • Centroids?
  • Which of Gary's SV tasks are the lowest-hanging fruit?
  • edit workflows for Observer2/1?

WorkFlow Decisions

(This kind of information is buried in various places; would be great to be in a clearer workflow page; it's here as a reminder.)

Seeing Policy

  • If seeing > 1.3 :
    • if not clear (no clouds): then SN
    • if clear : then do half-chips
  • if seeing < 1.3 : obstac

Wind Speed

  • if 5 < speed < 15 : 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)

End of Night

Detailed Afternoon Work

  1. restart sispi (beware multiple places for doing this); Note should do everything in the sispiuser@system1...
    1. Usually skip this step: First step: ssh to system1: bring up terminal, type ‘vncviewer system1:2’, asks your for password which is ‘vnc4sispi’. (This step might not be necessary!!)
    2. >> ‘setup SISPI’
    3. >> ‘shutdownSISPI DECam_20131231’ yesterday's date or go to architect console and click ‘Shutdown’ this is the instance of yesterday, should always be in the form of ‘DECam_’ then the date of the night before!
    4. clean up (note should see sispi@system1); ssh’s to machines and cleans up any ramdisk/processes that weren’t closed in the shutdown.
      1. >> cleanup_ramdisk
      2. >> cleanup_processes -k
      3. >> check_diskspace
    5. [probalby already here] cd ‘sispi/decam/architectures/ctio/’
    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 and ready then open a new SISPI GUI.
    7. Log-in to observer console as
      1. login: DECamObserver
      2. password XXXXXX
    8. Configure [in Observer Console]
  2. Take junk (zero) exposures ('2' as indicated below)
    1. turn on vsub
    2. ‘type=zero,object=junk,dtsqueue=none,count=5’.
    3. log this in Elog book
  3. Set up calibration exposures
    1. check with TelOps that the Flat screen is lined up
    2. >> Load Exposure Scripts [ Obs con]
    3. >> Select DECam Script
    4. >> find DECam/prenight_zeros_flats
    5. >> add
    6. >> GO
    7. log this in E-log book via Afternoon Exposure
      1. comment that r at 20s were removed

Detailed Night Work

  1. check center
    1. ask Telops for bright star
    2. take an exposure ... what kind?
    3. check center offset
      1. center EXPID [at observer 2 in kentools]
      2. re-center telescope if offsetx or offsety > 10 arcsec
  2. 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.
  3. Half-chip offset fields
    1. >> DECamScript
    2. use DES/SN-halfCCDoffsetSequence_E2_ugrizY
    3. >> submit
  4. SN fields
    1. go to field
    2. check center
      1. center <EXPID>
    3. add ra dec offsets in arcsec
    4. take exposure given these offsets
    5. repeat center check until within 10 arcsec x and y
    6. load SN exposure script