README web version of /home/usg/OPS/MTS/readme_xml/readme_75019700
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
General Description: The aim of the program is to derive the velocity
curve of
the spectroscopic binary HD166734 which has a period of 34.5 days. We would like
to have 20 observations of the spectrum of this star well distributed in phase.
The best configuration would be one observation every two nights during 40
consecutive days. However, ESO Service Mode is not supporting such time
constraint. Therefore, we hope that 20 observations distributed at
random (but always separated by a minimum of one full night without
observation) will lead to a similar phase covering. We prepared 20
observing blocks numbered from HD166734_01 to _20. They are all
identical and represent one observation. One observation is made of
two Science Exposures of 1450 sec each followed by a wavelength calibration
exposure of 60 sec. The whole observation takes about one hour (with overheads).
Please execute one OB each night when you have the possibility to do so.
The ONLY constraint: a MINIMUM two-day separation between two observations.
Waiver Requests
Critical Observing Condition Constraints
Time-Critical Aspects
Special Execution Requirements
Special Calibration Information
ToO Information
ToO Activators List
Is this a Pre-imaging run ?
Pre-imaging Requirements
Source(s) of Pre-imaging
Pre-imaging sources not listed above
Do all your OBs comply with the instrument-specific requirements listed
on the instrument-specific Phase 2 web page ?
If this is a pre-imaging run, did you select PRE-IMAGING for the Observing
Category for each Observing Template ?
Do all your finding charts comply with both the general and instrument-specific
Phase 2 Web Pages ?
If you submitted OBs for standard stars, did you specify the magnitude
and spectral type of all standard stars in the OBs ?
Have you included OBs for any calibrations that you need but which are
not part of the Calibration Plan ?
If you are observing Moving Targets, have you attached suitable ephemeris
files to your OBs?
If you have preferences which OBs should be executed first, did you make
use of the User Priority field in the OBs ?
If this is a run that requires coordinated observations with other facilities,
did you give proper instructions in the Time-Critical Aspects Section ?
Did you set 'New Preset' flag in all acquisition templates to 'True'?
If you use any lamp, did you check that it should never be left on at
the end of any OB?
Last creation of page: Tue Oct 6 15:40:06 2009
If you have comments, please contact usd-help@eso.org