README web version of /home/usg/OPS/MTS/readme_xml/readme_78035700
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
The purpose of this program is to resolve the three components of the
triple system LHS 102ABC with NAOS/CONICA and map the orbit of the close-binary
L dwarfs. The M3.5V primary star (V = 12.84, K = 7.73) lies 18.2 arcsec from the
binary L dwarfs (K = 11.36), which themselves are separated by 0.086 arcsec. To
measure the L dwarfs' positions with NACO, we need the best possible seeing conditions
and pixel resolution. The primary star LHS 102A also serves as the NAOS reference
star for all CONICA exposures. LHS 102A is the brightest object in the CONICA field,
and it satisfies all CONICA brightness restrictions.
This programme contains two OBs. One OB employs the S13 objective (for highest
resolution imaging of LHS 102BC); the other OB employs the S27 objective (for simultaneous
imaging of LHS 102A, B, and C). It is imperative that the OBs within each sequence
are executed consecutively and contiguously.
Waiver Requests
Critical Observing Condition Constraints
Seeing equal to or better than 0.8" at airmass 1.2.
The locations of LHS 102A and LHS 102BC on the detector array are important:
The OB labeled LHS102A-Epoch-8 uses the S27 objective. The target is
the primary star LHS 102A, which is also the NAOS reference star. CONICA must
first be rotated 33.8 degrees so that LHS 102A and BC are aligned along the
upper-left-to-lower-right diagonal of the array. Then, the target star LHS 102A
must be offset (approximately) to pixel (225,775). This offset will place the
faint L dwarf binary at (approximately) pixel (700,300).
The OB labeled LHS102BC-Epoch-8 uses the S13 objective. The target is
the binary L dwarf LHS 102BC. The target should be acquired near the center of
the array; no other offsets are needed. The primary star LHS 102A (the NAOS
reference star) will fall outside the S13 FOV, beyond the upper left corner of
the array.
Finding charts that show the targets' positions within the rotated S13 and S27
FOVs are provided for each OB. The FOV of these finding charts is 2x2 arcmin.
Note that the epoch of the finders is 1994.652. The targets have relatively
large proper motion (1.618 arcsec/yr at PA = 154.5), so their positions with
respect to the few background stars in the FOV have changed perceptibly since
mid-1994.
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:15 2009
If you have comments, please contact usd-help@eso.org