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

Principal Investigator Email Address

• Jerome.Bouvier@obs.ujf-grenoble.fr

Estimated Total Execution Time (hours, including overheads)

• 09:59:39

General Description

• This is a monitoring programme. These observations are coordinated with
   HARPS, X-SHOOTER SV time, 
  the Chandra X-ray satellites and the CFHT - the observations don't have to be simultaneous
    
  and there is flexibility in the requested seeing  (seeing constraint: 1.2).
  
  There are 41 OBs in total - 17 V2129Oph OBs - 4 Non-magnetic standard stars and
   20 associated 
  telluric calibration stars.
  
  The 17 V2129Oph OBs are time critical in that they should preferably be acquired
   over a period 
  of several nights  to monitor variability of a T Tauri star as it rotates. 1-2 exposures
   per 
  night would be ideal. If possible we would like 1-2 exposures of V2129 Oph per night
   over 13 nights 
  to ensure that we cover its 6.5 day period as evenly as possible.
  
  However ANY CRIRES spectra of our target will be of great value to the overall multiwavelength
  programme.
  
  **Time constraints**
  Any prior time constraints are removed, but we still have a preference to obtain
   1-2 exposures 
  per night, so that we can monitor variability over the T Tauri star's period.
  
  Please note that the OBs with names starting "Nonmag" can be executed at any time
   this period that the 
  seeing constraints are met.

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• We need the line at 2231nm to be observed extremely accurately

Time-Critical Aspects

• This is essentially a monitoring/imaging project. We need to sample the
   T Tauri star, V2129 Oph's rotation period (6.5days). 
  
  We require 17 observations spread more or less evenly over 7-13 nights (or longer
   if necessary) in this period.
  
  If two OBs can be executed each night a few hours separated from each other - this
   would be ideal but there is flexibility.
  These observations are coordinated with observations on HARPS, the Chandra X-ray
   satellite and the CFHT so while the time period is quite wide
  and there is some flexibility obtaining the OBs within 13 nights before 30 June
   is critical to the success of the larger multi-wavelength programme. 
  After 30 June the star is too close to the moon.
  
  The V2129 Oph OBs should be spread out as evenly as possible over a 7-13 day period
   but any CRIRES spectra at all of this system would be useful.
  The other constraints are quite relaxed so long as the S:N requirements are met.
  
  There are no strong time constraints on when the Nonmag OBs and their corresponding
   telluric frames are executed.

Special Execution Requirements

• ---(Empty)---

Special Calibration Information

• Telluric standards should be observed as possible after the related OB
   science frame.
  Each telluric OB has been numbered according to the science target OB it should
   follow :
  e.g., V2129Oph-1 OB2 should be followed by CAL_Tell1_v2129-1 if possible. If this
   telluric star is not ideal then two other possibilities
  have been listed (CAL_Tell2 and CAL_Tell3).
  
  The stars beginning "Nonmag..." only need to be observed once but the S:N requirement
   is quite strong as they will be used to calibrate the 
  magnetically sensitive lines.

ToO Information

• ---(Empty)---

ToO Activators List

• ---(Empty)---

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?

• NO

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