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

Principal Investigator Email Address

• ejehin@ulg.ac.be

Estimated Total Execution Time (hours, including overheads)

• 9.5

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 CRIRES run (A) that was allocated 9.5h. 
  Science OBs are provided for 9 different settings, covering 9 different species.
   Several OBs have been provided for the most important settings (H2O and HDO) to
   measure D/H ratio. 
  One telluric OB is provided for each setting (0.4") and a flux calibration OB (0.8")
   to be executed on each night contains all the settings.
  The slit width used is 0.4", AO on the nucleus is best if possible.
  
  The obseving strategy (exptime, settings to be done etc.) will be provided at the
   time of the trigger depending on the target.

Waiver Requests

• Waiver  accepted on Aug 26 to avoid submitting FCs (this prog. is a ToO).
  waiver  accepted on Aug 27 to use the wide slit (0.8") for the flux std star

Critical Observing Condition Constraints

• none, except it is a moving target

Time-Critical Aspects

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

Special Execution Requirements

• The detailed observing strategy (exptime, PA etc.) depending on the target
   will be sent during the ToO trigger.
  
  Please note :
  -------------
  
  - Science OBs are provided for 5 different settings, covering 5 different species
   (H20, HD0, HCN, C2H6 and CO). Several OBs have been made for the most important
   settings (H2O and HDO). One telluric OB is provided for each setting and the flux
   calibration OB to be executed on each night contains all the settings.
  
  - If seeing OK, AO loop can be closed on the comet itself (false nucleus should
   be quite sharp ~0.5").
  If it is not possible to close the loop on the comet, the observation can be perfomed
   without AO.
  
  - As many OBs as possible should be executed during the same night folowing ToO
   trigger informations. 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)

Special Calibration Information

• One flux OB should be executed each night. All the settings are included
   inside the CAL_Flux OBs. One CAL_flux OB has also been provided for the H20-HDO
   setting only as many of those OBs will be exected together the same night.
  We are using the wide slit for the flux std star (0.8").
  
  Telluric OBs have been provided for each setting and have to be executed after each
   corresponding science OB.
  
  A flat is attached to each science OB

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 the README file and the instrument comments of the telluric stars
 OBs include the required S/N/pixel of the spectrum of the telluric star, its spectral
 type and allowed spectral range?

• YES

Do any OBs include wavelength or flatfield calibrations?

• YES

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

• N/A

If the slit viewer guide star is different from the target, are the RA
 and DEC offsets accurate to within 0.05 arcsec and do they take into account the
 relative proper motion between the two objects?

• N/A

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

• N/A