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

Principal Investigator Email Address

• gregoryh@mpe.mpg.de

Estimated Total Execution Time (hours, including overheads)

• 0.8

General Description

• Observations of He I 10830 A emission.  The observations are ToO, to be
   triggered for when HST observations occur.
  
  On the finding chart, the target is marked with the red square and the arrow. The
   science target is a binary.  The primary science target is the NE target.  Please
   set the PA to 216/36 to get both the primary and secondary.  The OB includes two
   observations of TWA 3, with PA that differ by 180 deg.  
  
  The telluric standard should be taken immediately before or after this observation.
  
  The binary has a separation of 1.45 arcsec at a PA of 216.  The two objects are
   near-equal brightness, with J=8.22 and J=8.63, respectively.  The observer should
   easily resolve the pair.

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• None.

Time-Critical Aspects

• ToO, will be triggered when the HST observation of the object is sceduled.
    The CRIRES observation needs to occur within about 12 hours of the HST observation,
   and preferably closer in time.

Special Execution Requirements

• ---(Empty)---

Special Calibration Information

• ---(Empty)---

ToO Information

• HST will schedule observations during Period 84.  We will trigger a ToO
   1-2 weeks prior to the observation.  The CRIRES observation should occur very close
   in time to the HST observation to minimize the effect of variability.

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?

• N/A