README web version of /home/usg/OPS/MTS/readme_xml/readme_77012602

Principal Investigator Email Address

• boehnhardt@mps.mpg.de

Estimated Total Execution Time (hours, including overheads)

• 5h57m

General Description

• Primitive Dust in Oort Cloud Comet C/2004 B1 (LINEAR)
  
  Run C: SOFI imaging
  
  This is a simple point-and-shoot imaging program on a comet, a moving target. Ideally,
   the program should be performed in parallel to our Spitzer observations of the comet
   scheduled between 15 - 25 May and 27 May - 3 June 2006.
  
  The filter sequence will be JHKJ. Sky offsets will be at different positions more
   than 300 arcsec away from the comet.
  
  IMPORTANT: At maximum two OBS (~1h duration each) should be executed per night.
   
  
  Comet coordinates (approx. RADEC typical for mid May 2006 are given in the OBs)
   and differential velocity are to be updated by the SM observer before execution
   of the OB. The rotator angle remains 0 deg.
  
  Here is a brief cookbook instruction for the OB execution:
  
  - select OB to be executed
  - open attached ephemeris file
  - enter RADEC coordinates for epoch closest in time to start of OB (ephemeris columns
   RA and DEC)
  - enter differential RADEC velocity for epoch closest in time to start of OB (ephemeris
   columns Vel_RA and Vel_DEC)
  - do not update rotator angle 
  - start OB

Waiver Requests

• No Waiver Request was submitted.

Critical Observing Condition Constraints

• Please perform only two OBs per night!
  
  Environmental conditions:
  Sky = CLR
  Seeing = n
  Moon = g

Time-Critical Aspects

• This run should be executed during two nights as close as possible in
   time to our Spitzer observations currently scheduled between 15 - 25 May 2006 (OBs
   labeled "night1" and/or "night3") and 27 May - 3 June 2006 (OBs labeled "night2"
   and/or "night 3"). We will communicate the exact date of the Spitzer observations
   as soon as they become available to us.

Special Execution Requirements

• The central part of the coma must not be overexposed. Since comets are
   notoriously unpredictable in their brightness, we can't guarantee for sure that
   the carefully chosen integration times in the OBs will be safe against saturation
   of the cometary coma. If saturation occurs, feel free to shorten the integration
   time appropriately.
  
  Please execute only two OBs per night!

Special Calibration Information

• none

ToO Information

• not applicable

ToO Activators List

• not applicable

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• not applicable

Source(s) of Pre-imaging

• ---(Empty)---

Pre-imaging sources not listed above

• ---(Empty)---

Do all your OBs comply with the instrument-specific requirements listed
 on the instrument-specific Phase 2 web page ?

• YES

If this is a pre-imaging run, did you select PRE-IMAGING for the Observing
 Category for each Observing Template ?

• N/A

Do all your finding charts comply with both the general and instrument-specific
 Phase 2 Web Pages ?

• N/A

If you submitted OBs for standard stars, did you specify the magnitude
 and spectral type of all standard stars in the OBs ?

• N/A

Have you included OBs for any calibrations that you need but which are
 not part of the Calibration Plan ?

• N/A

If you are observing Moving Targets, have you attached suitable ephemeris
 files to your OBs?

• YES

If you have preferences which OBs should be executed first, did you make
 use of the User Priority field in the OBs ?

• YES

If this is a run that requires coordinated observations with other facilities,
 did you give proper instructions in the Time-Critical Aspects Section ?

• YES