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

Principal Investigator Email Address

• Heike.Rauer@dlr.de

Estimated Total Execution Time (hours, including overheads)

• 09:59:30

General Description

• The goal of this run is to obtain high resolution reference spectra of
   comet Temple1 which is the target of the NASA Deep Impact spacecraft.
  
  This program is time critical : all the observations must be done in June (within
   one month before the impact, scheduled for July 4) and if possible all the OBs executed
   as close as possible to each other. 
  
  Precise coordinates, differential tracking rates and the position angle must be
   updated (using the ephemeris) before starting the OBs (see execution requirements)
  
  There are 6 OBs (3 per setting) of 1h40m each. We are using two settings and the
   OB names reflect this, ex :
  
  MOV_DI_dic1_1 : DIC#1 346+580 and
  MOV_DI_dic2_2 : DIC#2 437+860 
  MOV_DI_dic1_3
  MOV_DI_dic2_4
  ...
  
  as well as the order we would like to have them executed (it is indeed better to
   alternate the OBs to have DIC1, DIC2, DIC1, etc.). Please then respect the OB priorities.
  
  Note that the Slit width = 0.44" always and the
  Slit is fixed on the SKY + ADC 
  PosAng = to be determined for each observation (see ephemeris)
  
  See execution requierements for other technical details

Waiver Requests

• A waiver request has been submitted to allow exptimes longer than 1h.
  Approved February 21 by O.Hainaut

Critical Observing Condition Constraints

• As we are particularly interested by the very blue region, high airmasses
   (>1.7) should be avoided

Time-Critical Aspects

• All the OBs should be executed in June (within one month before the Impact,
   the 4th of July). 
  Due to the moon constraint (g) and the comet visibility, the best period to execute
   the OBs is from June 01 to June 15. There are 5hrs available per night (within the
   airmass constraint) so it is possible to execute 2 OBs per night.
  
  Note that if possible it is better to execute as many OBs as possible close in time
   and finish the program as soon as possible once started (to avoid intrinsic variations)

Special Execution Requirements

• As our target is a moving object, the following quantities need to be
   updated in the OB before execution :
  
  1) the precise coordinates (those in the OBs are just indicative)
  under the columns : R.A._(ICRF/J2000.0) and _DEC
  
  2) the additional tracking velocities (already given in arcsec/s)
  under the columns : dRA*cosD and d(DEC)/dt
  NB : if the comet is moving with respect to the slit during the exposure, 
  this means that the diff. tracking was not properly entered !
  
  3) the Position Angle (to have the slit along the comet tail)
  under the column : PsAng (given in degrees and measured fron N-->E)
  
  These quantities are to be taken from the provided - 10min steps- ephemeris
  
  
  Important Notes: 
  -----------------
  
  - The acquisition should be done (and slit put) on the center of light of the 
  comet (diffuse and slightly elongated object of mag V~9-10).
  SecondaryGuiding is done with the blue camera.
  
  - As the comet is a moving object secondary guiding from slitviewer
  images cannot be done on an offset star (but is possible on the comet 
  nucleus if round enough) ! 
  
  - The ephemeris are given by step of 10 minutes (comet moving by about 10 arcsec
   / 10 minutes). Be Carreful about the date (given in UT time!).
  
  - Dont skip the acquisition if you execute 2 OBs (DIC1 and DIC2) consecutively (the
   dichroic setting is done from the acquisition template)

Special Calibration Information

• none

ToO Information

• none

ToO Activators List

• none

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• none

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 ?

• N/A

If you need secondary guiding, are there suitable objects within 30 arcsec
 from your target ?

• N/A