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

Principal Investigator Email Address

• rmennick@astro-udec.cl

Estimated Total Execution Time (hours, including overheads)

• 8

General Description

• This program is aimed to search for discrete absorption components (indicative
   of outflows) in the wings of the Paschen-beta line of a sample of relatively bright
   (J= 7-10 mag) galactic interacting binaries in two random epochs (per star) of their
   long photometric cycles. The OBs use the standard CRIRES setup with the reference
   wavelength at 1288.7 nm. Expected S/N ratios  in this wavelength are around 200
   for all program objects. Two telluric calibration OBs are necessary; one with an
   A0 star and other with a G1 star. Due to time limitation, some stars are planned
   to be observed only once, not twice as the others. In all OBs we use the same target
   as the AO guide star. As our objects are intrinsically variable, we provide only
   a rough estimate for the B-V color for them in the acquisition template. We use
   B-V= 0 since the dominant spectrum in these binaries is typically around A0.

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• NA

Time-Critical Aspects

• NA

Special Execution Requirements

• We ask for splitting our OBs in two broad observing epochs. Those OBs
   labeled with A can be observed preferently at the beginning of the observing season
   and those labeled B should be observed
  preferently at the end of the observing season. This in order to maximize the coverage
   of the long photometric cycles of our objects (typically 150-250 days). However,
   we can be flexible in this point, allowing for instance differences of 3 or 4 months
   between two OBs for the same star. The ideal case is with the longer possible time
   delay (5 or 6 months).
  
  The Cal-Telluric-Hip088154 OB should be observed just before or after the V393Sco-A
   OB
  The Cal-Telluric-Hip31446 OB should be observed just before or after the AUMon-A
   OB
  
  New comments added on April 30, 2009 concerning type "B" OB execution:
  
  Cal-Telluric-AUMon-B OB should be observed just before or after the AUMon-B OB
  Cal-Telluric-HD50526-B OB should be observed just before or after the HD50526-B
   OB
  Cal-Telluric-V393Sco-B OB should be observed just before or after the V393Sco-B
   OB
  Cal-Telluric-V356Sgr-B OB should be observed just before or after the V356Sgr-B
   OB
  
  We decided no to execute the OBs:
  LPAra-B
  DQ-Vel-B
  HD170582-B
  GKNor-B
  DPV074415-B
  Cal-Telluric-HD

Special Calibration Information

• NA

ToO Information

• NA

ToO Activators List

• NA

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?

• N/A

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