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

Principal Investigator Email Address

• luca@mpa-garching.mpg.de

Estimated Total Execution Time (hours, including overheads)

• 1.3

General Description

• In this run we take high-res spectra of a common proper motion pair composed
   of G dwarf primary and M dwarf secondary. 
  All observations are done with the UVES red arm centred at 860 nm, at the highest
   resolution achievable (image slicer-3, slit 0.3 arcsec).
  
  For the M dwarf secondary, we link its OB (NLTT45791) to that of a telluric standard
   with similar coordinates (CAL_NLTT45791) to ensure both stars will be observed at
   similar airmasses and close in time. 
  
  The S/N reported in the Instrument Comments is that expected from a single exposure
   with the requested time, computed using the UVES Exposure Time Calculator.

Waiver Requests

• A waiver request (submitted at 12:36:05 27 January 2009) has been approved
   to change the central wavelength of the UVES red arm from 600nm (standard setting,
   with image slicer-3) to 860nm (standard setting, with image slicer-3) for all our
   observations.

Critical Observing Condition Constraints

• No critical observing conditions constraints apply.

Time-Critical Aspects

• Ideally the observation of the telluric standard should be done at the
   same (or as close as possible) airmass of the science target. Since it is not know
   the exact date and time when observations will be carried, it is impossible to decide
   beforehand which order, i.e. science--telluric target or telluric--science target,
   would be better.
   
  If possible, when the observations will be executed, please optimize the order in
   which observe the two targets so as to ensure that both science and telluric star
   will be observed at similar airmasses.

Special Execution Requirements

• The observations in this run have been split in three OBs: one for the
   G dwarf (total execution time 18 minutes) and the other two (linked together) for
   the M dwarf + telluric standard (total execution time 1 hour). 
  
  Since the abundance measured in the G dwarf will be used to calibrate that in the
   M dwarf, ideally the two targets should be observed under identical conditions.
   Notice that telluric, M and G dwarfs are separated by few arcminutes only and the
   overheads computed via P2PP are most likely overestimated. It would be much appreciated
   if you could observe the G dwarf in the same night as the M dwarf + telluric.

Special Calibration Information

• We have submitted OB for observing a telluric standard which must be linked
   to the observation of the M dwarf so as to ensure that both science and telluric
   star will be  observed at similar airmass and close in time. The OB for the M dwarf
   is called NLTT45791 and the linked OB with the telluric is called CAL_NLTT45791.
   We have also specified in User Comments and Calibration Requirements that these
   two blocks must be linked together.
  
  In the User Comments of the OB CAL_NLTT45791 the V magnitude and the spectral type
   of the telluric are also given. For the telluric we ask 2 exposures to ensure we
   reach a good S/N in the extreme red and to avoid saturation at shorter wavelength
   where this star emit most of its flux. Please avoid saturation or the opposite,
   under-exposure of the red part.

ToO Information

• ---(Empty)---

ToO Activators List

• ---(Empty)---

Do all your OBs comply with the instrument-specific requirements listed
 on the instrument-specific Phase 2 web page ?

• YES

Do all your finding charts comply with both the general and instrument-specific
 Phase 2 Web Pages ?

• YES

If you submitted OBs for standard stars, did you specify the magnitude
 and spectral type of all standard stars in the OBs ?

• YES

Have you specified the S/N ratio at given wavelength in the User Comments
 field of each OB?

• YES

Have you included OBs for any calibrations that you need but which are
 not part of the Calibration Plan ?

• YES

If you are observing Moving Targets, have you attached suitable ephemeris
 files to your OBs?

• N/A

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 ?

• N/A

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

• N/A