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

Principal Investigator Email Address

• andres.carmona@unige.ch

Estimated Total Execution Time (hours, including overheads)

• 10.5h

General Description

• Standard long-slit spectroscopy observations of T Tauri stars in the NIR
  
  The goal of the project is to detect H2 emission at 2 micron and CO emission at
   4.7 micron
  towards the sources.
  
  We use three wave settings (27/1/n, 25/-1/n, 25-1/i) for the three H2 lines searched
   (2.12, 2.22, 2.24 micron)
  and two wave settings (12/-1/i,11/-1/n) for searching the CO lines at 4.7-5.0 micron
   .
  
  
  The observations are performed with AO in the NGS mode.
  The stars themselves are the AO guide stars.
  
  We use a 0.4" slit, and we employ the AutoNodOnSlit template.
  
  The observations are performed with the slit oriented in the direction of the 
  binary pair in the cases of SZ_Cha and HR4796A (see finding charts)
  
  The observations of each star are splitted in several OB's, 
  in general one for each order observed.
  For example, the OB SZ_33_CO_order11  corresponds to the observations 
  of CO for the star SZ_33 using the order 11/-1/n.
  
  When no order is specified, that means that we observe all the settings
  of the H2 or CO observations within one OB.
  
  OB's splitting is done for avoiding OB's with duration longer than 1h.
  
  Observations of telluric standards are required inmmediatelly preceding or following
   the
  science observations. OB's for these observations are included as well.
  They are named as CAL_ where  is the name of the OB
   to whom the calibration 
  belongs
  
  We strongly suggest to perform the observations of the H2 OB's of the same star
   during the same night.
  We strongly suggest to perform the observations of the CO OB's of the same star
   during the same night.
  
  Lamp calibration observation is performed for the wave-ID's 27/1/n and 12/-1/i,
   11/-1/n. 
  The wave-ID's 25/-1n and 25/-1/i will be calibrated with telluric emission lines.
  
  
  NOTES:
  *A waiver for changing from the wave-ID 12/1/n to the wave-ID 12/-1/i was accepted
  *The target coordinates of SZ Cha are corrected from those written the proposal.

Waiver Requests

• A waiver was accepted for changing the wave-ID 12/1/n for the wave-ID
   12/-1/i

Critical Observing Condition Constraints

• No critical observing conditions. 
  However, for the faint target SZ 33 observations at low airmass are preferred.

Time-Critical Aspects

• Observations of this run (A) should be performed from april to may.
  The velocity shift of the targets is necessary for the detection of the CO lines
   at 4.7 micron

Special Execution Requirements

• Observations of this run (A) should be performed from april to may.
  The velocity shift of the targets is necessary for the detection of the CO lines
   at 4.7 micron
  
  We strongly suggest to perform the observations of the H2 OB's of the same star
   during the same night.
  We strongly suggest to perform the observations of the CO OB's of the same star
   during the same night.

Special Calibration Information

• Observations of telluric standards are required inmmediatelly preceding
   or following the
  science observations. OB's for these observations are included as well.
  They are named as CAL_ where  is the name of the OB
   to whom the calibration 
  belongs

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?

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

• YES