README web version of /home/usg/OPS/MTS/readme_xml/readme_76002700
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
Deep NACO-SDI imaging of Eps Eridani with the aim to identify planetary
mass companions within 1 arcsec
of Eps Eri. The observations require high contrast as the companions are at least
11 mag fainter than
Eps Eri.
Eps Eri, the brightest object in the field, has V=3.73mag.
Note that all six OBs (EpsEriOB1 to EpsEriOB6) are identical.
Note on DIT: for our visitor mode observing run in Sept. 2004, we used a DIT = 4s
for Eps Eri.
For the service mode, a DIT = 1s has been selected, which should assure that no
too strong
saturation of the detector occurs. A slight over-saturation, i.e., saturating the
inner 4 to 5
pixel (diameter) of the PSF is what we aim for, as this should yield the best signal-to-noise
ratio for the detection of planetary mass companions further out in the PSF wings.
Eps Eri has a proper motion of ~ 1 arcsec per year. Similar to our observing run
from Sept. 2004,
we corrected the 2000 equinox coordinates to the expected coordinates for observations
in P76. No
precession correction was applied (i.e., Epoch 2000). We proceeded this way as it
was not clear
to us if the proper motion values entered in the *.aocfg file are forwarded to the
TCS (Jason
wanted to have this disabled at some point).
Note on checksum: the phase 2 proposal was prepared under MacOSX 10.4.2.
Version 1.77 of jnps does not compute the checksum correctly in this case (see email
exchange
with ESO User Support Department, Entry-Id: USD-13807).
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 have PSF reference star OBs, do the names of those OBs begin with
PSF_ ?
If there are Finding Charts attached to your OBs, is the field-of-view
of at least one of these charts 2' x 2' (with clearly labelled field orientation)
?
Have you clearly marked and labelled your wavefront reference objects
R1, R2, R3, ... (as specified in the NAOS Preparation Software) on your Finding
Charts ?
Have you specified the magnitude of the brightest object in the field-of-view
for each OB ?
Are there objects in any of your fields (including standard stars) which
are brighter than the limits specified in the User Manual and on NACO web Pages
?
If the previous answer is yes, have you given a list of OBs and a justification
for the brightness limit violation in the general description field ?
Last creation of page: Tue Oct 6 15:40:09 2009
If you have comments, please contact usd-help@eso.org