README web version of /home/usg/OPS/MTS/readme_xml/readme_76016500
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
The programme consists of simple UVES observations of the runner up
for the most metal-poor star known, HE0107-5240, and a comparison
star, CD -38 245, which is used as radial velocity standard. The aim
of the program is radial velocity monitoring of HE0107-5240. If the
star would be a binary, this would have important consequences for
the interpretation of its abundance pattern; in particular, models
predict that it would likely to be a Population III star in this case.
A 1 hour exposure of HE0107-5240 with the 390+564 setting and a 1''
slit in the blue and 0.6'' slit in the red arm shall be taken, and a
10 minute exposure of CD-38 245 with the same setting immediately
afterwards. We use a 1x1 pixel binning because we are not
readout-noise limited.
For avoiding slit losses due to atmospheric differential refraction,
the slit is put to the parallactic angle, and the derotator mode is
set to "ELEV" in the OBs.
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 ?
If you need secondary guiding, are there suitable objects within 30 arcsec
from your target ?
Last creation of page: Tue Oct 6 15:40:09 2009
If you have comments, please contact usd-help@eso.org