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

Principal Investigator Email Address

• pedro.figueira@unige.ch

Estimated Total Execution Time (hours, including overheads)

• 9.9

General Description

• This program aims at determining high-precision RV of TW Hya in order
   to solve the discussion of a putative planet around it.
  The observations must be done in a sequential way, in the order: HD108309 (RV std)
   -- TW Hya -- HD96146 (tel. std) and with no gaps in between the different OB's,
   so that the instrument setting remains unchanged and the calculus of relative RVs
   can be meaningfull. There are 9 sequences, numbered from 0 to 8. Only one sequence
   (comprising the 3 OB's aforementioned) can be done per night and the 9 OB's are
   to be done in consecutive nights, if possible. As we are aware of the difficulty
   of schedulling observations in consecutive nights, we ask only for a sequence of
   4 observations done in strictly consecutive nights, so that one putative orbital
   period is covered. All the other points can be scattered.
  We would like to note that this program is well-suited for bad-seeing periods: a
   big PSF in the sky reduces guiding and photocenter illumination errors, by sacrificing
   some expendable photons.
  Please send an e-mail to the PI every time this program is performed so that we
   can observe the same targets with a visible wavelength specrograph (CORALIE) in
   a roughly simultaneous fashion (few days apart).

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• This program should be done at the worst seeing conditions possible, in
   order to reduce photocenter-induced errors. Still, aware that the astronomer on
   duty has to manipulate programs following diverse constraints, I leave this as a
   recomendation more than an absolute need.

Time-Critical Aspects

• This program has no time-critical constrains other than the observation
   at low airmass.

Special Execution Requirements

• The observations must be done in a sequential way, in the order: HD108309
   (RV std) -- TW Hya -- HD96146 (tel. std) and with no gaps in between the different
   OB's, so that the instrument setting remains unchanged and the relative RVs are
   meaningfull. There are 9 sequences, numbered from 0 to 8. Only one sequence (comprising
   the 3 OB's aforementioned) can be done per night and the 9 OB's are to be done in
   consecutive nights, if possible. As we are aware of the difficulty of schedulling
   observations in consecutive nights, we ask only for a sequence of 4 observations
   done in strictly consecutive nights, so that one putative orbital period is covered.
   All the other points can be scattered.

Special Calibration Information

• The observations must be done in a sequential way, in the order: HD108309
   (RV std) -- TW Hya -- HD96146 (tel. std) and with no gaps in between the different
   OB's, so that the instrument setting remains unchanged and the relative RVs are
   meaningfull. There are 9 sequences, numbered from 0 to 8. Only one sequence (comprising
   the 3 OB's aforementioned) can be done per night and the 9 OB's are to be done in
   consecutive nights, if possible. As we are aware of the difficulty of schedulling
   observations in consecutive nights, we ask only for a sequence of 4 observations
   done in strictly consecutive nights, so that one putative orbital period is covered.
   All the other points can be scattered.
  The telluric standard is included in the OB's and the information relative to it
   is made clear in the "User Comments" field.

ToO Information

• This program has no ToO.

ToO Activators List

• This program has no ToO.

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