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

Principal Investigator Email Address

• ejehin@ulg.ac.be

Estimated Total Execution Time (hours, including overheads)

• 11.0h

General Description

• This is a ToO program to target the first bright new comet (mv=6.0) that
   will be observed by the Herschel IR space telescope (one target). Three VLT spectrometers
   will be used : UVES on UT2 and CRIRES and FORS2 on UT1. The observations will be
   trigered at the same time for the three instruments to be executed as close as possible
   (the same night is best or within a few days) to the Herschel observations. 
  
  This README is for the UVES run (C) that was allocated 11h.
  There are 2 settings, one with the DIC#1 (bluest setting) and the other with the
   DIC#2 in order to cover the full visible wavelength range. We are using a narrow
   slit (0.44"), a given slit position on the sky (comet tail PA) and the ADC.
  Precise instructions (exptime, slit PA, etc.) for OB execution will be provided
   at the time of the trigger.

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• Airmass should be < 1.6 for DIC#1 as we are interested by faint features
   close to the atmospheric cutoff at 310nm.

Time-Critical Aspects

• The UVES OBs need to be executed as close as possible (same night is best
   or within a few nights) to the Herschel observations and if possible to FORS2 and
   CRIRES OBs on UT1.

Special Execution Requirements

• The detailed observing strategy (exptime, PA etc.) depending on the target
   will be sent during the ToO trigger.
  
  Please note :
  -------------
  
  - There are 2 series of OBs one with DIC#1 (346+580) and one with DIC#2 (437+860),
   with a slit width of 0.44". A fixed position of the slit on the sky will be used
   (PA will be provided during trigger), the ADC is used.
  DIC#1 setting is the most important setting and there are many more OBs for that
   setting.
  
  - As many OBs as possible should be executed during the same night. As most of the
   observations will be done consecutively (one target only) it is not needed to send
   a complete preset each time the OB is executed.
  
  - The coordinates *and* the differential tracking rates have to be to be updated
   in the OBs before the 1rst execution. 5 min step ephemeris will be provided at the
   time of the trigger. The position angle (PA) will also be given to be updated in
   the acquisition template.
  
  - Please check that the comet stays in the narrow slit. If it is moving out rapidly
   there is a problem ( most probably error in the diff. tracking rates)
  
  - secondary guding can be used on the comet false nucleus (not on an offset star)

Special Calibration Information

• - We have attached a wave calibration to each OB in order to get the best
   wavelength calibration needed for our projet. The exptimes have been taken from
   daytime calib with the same slit width. No wave calibration for 860 nm setting.
  
  - 2 OBs have been provided to observe a flux standard star using the same setting
   and a 5.0" slit. They should be done once during a night when the comet is observed.
  
  - for the daytime calibration we need 10 blue bias and 10 blue flats (normal and
   deuterium) instead of the 5 usual flats. This in order to increase the S/N in the
   blue setting.

ToO Information

• The ToO target will be a bright new comet (mag 6) that will be observed
   by Herschel IR space telescope.
  The date of observation will be know about one week before the trigger.

ToO Activators List

• ejehin@ulg.ac.be 
  manfroid@astro.ulg.ac.be
  hutsemekers@astro.ulg.ac.be

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

• YES

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 specified the S/N ratio at given wavelength in the User Comments
 field of each OB?

• 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?

• N/A

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 ?

• YES

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

• N/A