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

Principal Investigator Email Address

• Dominique.Bockelee@obspm.fr

Estimated Total Execution Time (hours, including overheads)

• 04:59:40

General Description

• The goal of this DDT is to observe simultaneously on UT1 with CRIRES and
   on UT2 with UVES+FORS1 the bright comet 8P/Tuttle. Those observations will be done
   on two different nigths (the closest the 2 nights are in time, the best it is).
   
  CRIRES is run(A), UVES is run(B) and FORS1 is run(C). 
  The observations on both telescopes need to be coordinated (both telescopes available).
   The observation will last for 4 hours on each telescope (in parallel) starting from
   beginning of astronomical twilight (the comet is setting). 
  As the comet is also getting fainter, the soonest the observation are done, the
   better it is (before Feb 10 in any case).
  CLR or PHO weather and low humidity is important for the success of the observations.
  
  run (A) : On UT1 there are 6 OBs to execute consecutively each night :  2 science
   OBs (2 different settings A and B) of 1.5h + 3 telluric (before, between with the
   2 settings and after) and 1 flux std star (with both settings). The order of execution
   and other info are given in special execution requierements. 
  
  run (B) : On UT2 there are 2 OBs to execute consecutively each night with UVES :
   one science OB with DIC#1 (note that the blue setting is non std with 348nm central
   wavelength) and one science OB with the DIC#2. 
  
  run (C) : After the 2 UVES OBs are done there in each night one FORS1 LSS OBs with
   several offsets to executed + one "sky" OB to take a spectrum of the sky 30 min
   away in RA.
  
  NB : As the target is a fast moving object it is of course needed to update the
   coordinates and diff velocities in the OB before execution (using 5min by 5min ephemeris
   provided).
  
  This general description is the same for the 3 runs but the other subpanels (for
   instance special calibrations, special execution requierements) are specific for
   each instrument.

Waiver Requests

• A waiver request was approved for UVES on Jan 25 in order to :
  
  - be allowed to use the non std setting 348nm in the blue with DIC#1
  - to have long OBs (1h15min) and execute 2 OBs consecutively

Critical Observing Condition Constraints

• We need clear or photometric weather

Time-Critical Aspects

• This run is simultaneous with run(A) on UT1 ! 
  
  Both telescopes need to be available in service mode simultaneously for 4 hours
   in a row and since the beginning of the night. This needs to be coordinated between
   each telescope operators. But no need to start the OBs exactly at the same time
   (15 min delay is fine - CRIRES on UT1 might start earlier in twilight).
  
  As the comet is also getting fainter, the soonest the observation are done, the
   better it is (before Feb 10 in any case).
  
  The comet is setting so the OBs need to be started directly at the beginning of
   the night to have the 4 hours window. The comet OB can be started as early as middle
   of nautical twilight or about 00:20 UT.

Special Execution Requirements

• OB execution order
  ---------------------
  There are 2 OBs provided for each night (n1 and n2). The DIC#1 OB (MOV_8P_n1_DIC1)
   containing the bluest setting needs to be started first (at lower airmass). Then
   after the DIC#2 OB can be executed (MOV_8P_n1_DIC2).
  
  Note that no preset is needed for the second acquisition as telescope will be already
   on the target. Put telescope preset on False in the template and reacquire the target
   on the slit. It is good to update the diff tracking rates directly on the telescope
   panel for the 2d OB.
  
  
  Fast moving target !
  -------------------
  The coordinates *and* the differential tracking rates have to be to be updated in
   the OBs before execution. 2 min step ephemeris have been provided. The position
   angle is also given in the last column and needs to be updated in the acquisition
   template (close to 75 deg) once per night.
  
  Be carreful with the change of date in UT ! Few minutes after the night starts there
   is a change of date in UT.
  
  Please check that the comet stays in the narrow slit. If it is moving out rapidly
   there is a problem (probably error in the diff tracking rates) It would be good
   to update the diff tracking rates for the 2d OB (that can be done directly and in
   any time on the telescope panel with the help of the TIO) because diff tracking
   velocities are changing with time.
  
  Dont use the secondary guiding with UVES on the comet! It was not working and producing
   problems during our previous attempts.
  If the comet is going out of the slit DONT TRY to put it back using the telescope
   offsets from the AUTOGUIDING PANEL. This is confusing the telescope it seems and
   the target will never get back in the slit. But what you can do is to do small offsets
   directly from the telescope side with the help of the TiO (if the comet is completely
   out of the slit few arcsec, you can do a pause - please write down how many minutes
   it was stoped and try to compensate for it by increasing total exptime).
  
  Choice of guide star
  -------------------
  Warn the TiO about the choice of the guide star, to not take it too close to the
   center of the field of view neither to close to the edge. The comet is moving mostly
   towards the south so a good GS would be to the South of the field.

Special Calibration Information

• - It would be appreciated if a flux std star could be observed as part
   of the std calibration plan with our 2 settings (DIC#1 348-580nm and DIC#2 437-860nm)
   in the morning twilight (no time in the evening twilight) or in an other clear night.
  
  - for the daytime calibration we need 10 bias and 10 blue flats (normal and deuterium)
   instead of the 5 usual flats. This in order to increase the S/N.

ToO Information

• ---(Empty)---

ToO Activators List

• ---(Empty)---

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• ---(Empty)---

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

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

• YES

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

• N/A