README web version of /home/usg/OPS/MTS/readme_xml/readme_83024800
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
This is the continuation of our monitoring program to measure the astrometric
motion of our target due to its unseen companion with high astrometric precision.
We therefore need our OBs to be executed in pairs of calibration/science in time
intervalls of approximately three weeks.
To measure the astrometric motion we use a reference star in our FoV, 2MASSJ02190953-3646596.
The target GJ1046 in the science OBs, GJ1046-8...10, is also used as the wavefront-star,
R1, and is the brightest object in the FoV with V=11.61.
Due to the big separation between target and reference star we cannot center the
FoV onto the target. Instead we need another pointing, whose coordinates are clearly
marked in the finding charts. To ensure, that with our choosen jitter-pattern both
stars are always fully inside the FoV and to avoid crosstalk with appearing ghosts,
it is very important to then center the reference star, which is in the lower right
corner of the FoV, on the pixel (X=917, Y=65) of the S27 detector for all science
OBs!
For the same reasons we need the lower star, 2MASSJ0024303032-7204585, in the chart
for the calibration OBs, CAL_47_Tuc-8...10, the southernmost object, to be centered
on the pixel (X=917, Y=105) after the pointing. The pointing for the center of the
detector is given in the finding charts, too. The wavefront star in the calibration
field is the brightest, northernmost object in the FoV with V=11.82.
Waiver Requests
We requested two waivers (381.C-5057A.01) on 16. January, which were
both approved on 18. January.
The first request was concerning the distribution of OBs over P83 in calibration/science
pairs. We asked for the consecutive execution of our calibration and science OBs,
with the calibration OBs first.
The request for exceeding the 1h limit for the single science OBs was approved,
too.
Critical Observing Condition Constraints
Time-Critical Aspects
Due to visibility of our target, the execution of the OBs is not possible
befor end of July.
The calibration OBs, named CAL_47_Tuc-8..103, need to be executed right before the
corresponding science OBs, named GJ1046-8...10, due to visibility reasons.
We aim to measure the astrometric motion of our target star due to its unseen companion.
Therefore we need the three calibration/science OB pairs be executed in time intervalls
of roughly three weeks.
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:29 2009
If you have comments, please contact usd-help@eso.org