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

Principal Investigator Email Address

• lbarrera@umce.cl

Estimated Total Execution Time (hours, including overheads)

• 02h49m

General Description

• Science 
  ======= 
  
  ------------------- Please communicate about this program to:  lbarrera@umce.cl
   (PI) AND 				tubiana@mps.mpg.de AND boehnhardt@mps.mpg.de! ------------------- 
   
  
  Program: VRI filter imaging of the ROSETTA target comet 67P/Churyumov-Gerasimenko
   to monitor the dust environment of the comet while it is approaching the Sun. The
   main goal of the monitoring is the detection of distant activity of the comet. 
   In principle a simple point-and-shoot program on a MOVING TARGET. A sequence of
   5 OBS (34min/OB) is to be executed during March 2008. Most likely only one OB per
   night can be performed due to the limited visibility window of the comet (morning
   sky low over the horizon). It is acceptable to extend the OB into morning twilight
   by about 10 min. The object is located in the Milky Way, so the background will
   be very crowded. 
  
  - Object visibility: in late Feb. to March 2008 the comet is visible only at low
   elevation late in the morning sky (see the ephemeris file). It is thus required
   to point it in time, i.e. at the latest 35min before start of morning twilight.
    
  
  - Special note: large offsetting amplitudes at the beginning of each science template
   (change of guidestar is ok, also guide probe vignetting of the lower CCD).  
  
  - Blind acquisition, i.e. object identification is not necessary, though easily
   possible (by blinking). Please check telescope pointing through DSS image!  
  
  - Ephemeris provides in 10min time steps for the daily visiblity window of the comet
   at Paranal  
  * RADEC positions (hh mm ss.ss, sdd mm ss.s) 
  * RADEC velocities (arcsec/s) 
  * Airmass 
  * Vis. Brightness (mag) 
  * distance comet-moon TOM (deg) 
  * moon phase (%)  
  
  Cook instructions for OB execution: 
  =================================== 
  - select OB for execution (check time constraints) 
  - check requirement for environmental conditions (CLR, moon phase/distance) 
  - in OB enter RA and DEC from target ephemeris (fields RA and DEC) that are closest
   in time to the expected start time of the OB 
  - in OB enter differential velocity in RA and DEC (fields VEL_RA and VEL_DEC) from
   target ephemeris that are closest in time to the expected start time of the OB 
  - perform preset and start R filter offset exposures
  - change of guide star is no problem, also not vignetting of lower CCD

Waiver Requests

• no applicable

Critical Observing Condition Constraints

• CLR conditions are required!

Time-Critical Aspects

• In late Feb. to March 2008 the comet is visible in the late morning sky
   low at the eastern horizon. In order to get the OBs performed in time before the
   sky gets bright, it is important to point the comet low and in time (the latest
   35min before start of twilight). It is acceptable to extend the OB execution max.
   10min into morning twilight.

Special Execution Requirements

• Not applicable.

Special Calibration Information

• According to FORS calibration plan

ToO Information

• Not a ToO program.

ToO Activators List

• Not applicable.

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• Not aplicable.

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 ?

• N/A

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

• N/A

If you have prepared your finding charts with tools other than FIMS,
 do they comply with the specifications on the FORS1 Phase 2 web page ?

• N/A