README web version of /home/usg/OPS/MTS/readme_xml/readme_81023500

Principal Investigator Email Address

• kuerster@mpia.de

Estimated Total Execution Time (hours, including overheads)

• 5:40:44.000

General Description

• This is the beginning of a 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-0...3, is also used as the wavefront-star,
   R1, and 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-0...3, 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 three waivers (381.C-0235A.01)  on 24.January, which were
   all approved on 25. January.
  The first request was concerning the distribution of OBs over P81 and 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 as well as the
   combined calibration/science OBs with a total of 1.4h was approved. 
  The third request regarded the total execution time. Calculating the observing time
   including overheads with P2PP led to a 10 min 44 sec longer total execution time
   as requested and allocated. The requested time was calculated with the formulas
   given in the NACO User Manual. We therefore asked for this extra execution time
   which was accepted.

Critical Observing Condition Constraints

• We hav no critical observing condition constraints.

Time-Critical Aspects

• Due to visibility of our target, the execution of the OBs is not possible
   before beginning of July.
  The calibration OBs, named CAL_47_Tuc-0...3, need to be executed right before the
   corresponding science OBs, named GJ1046-0...3.
  We aim to measure the astrometric motion of our target star due to its unseen companion.
   Therefore we need the four calibration/science OB pairs be executed in time intervalls
   of roughly three weeks.

Special Execution Requirements

• We kindly ask to get access to the data from our first OB pair (CAL_47_Tuc-0,
   GJ1046-0) as soon as possible after the data have been taken. This would allows
   us to check our strategy before the next 3 OB pairs are carried out and to verify
   our observing approach.
  In this way we can rule out the waste or wrong execution of the following OBs.

Special Calibration Information

• ---(Empty)---

ToO Information

• ---(Empty)---

ToO Activators List

• ---(Empty)---

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• ---(Empty)---

Source(s) of Pre-imaging

• ---(Empty)---

Pre-imaging sources not listed above

• ---(Empty)---

Do all your OBs comply with the instrument-specific requirements listed
 on the instrument-specific Phase 2 web page ?

• YES

If this is a pre-imaging run, did you select PRE-IMAGING for the Observing
 Category for each Observing Template ?

• N/A

Do all your finding charts comply with both the general and instrument-specific
 Phase 2 Web Pages ?

• YES

If you submitted OBs for standard stars, did you specify the magnitude
 and spectral type of all standard stars in the OBs ?

• N/A

Have you included OBs for any calibrations that you need but which are
 not part of the Calibration Plan ?

• N/A

If you are observing Moving Targets, have you attached suitable ephemeris
 files to your OBs?

• N/A

If you have preferences which OBs should be executed first, did you make
 use of the User Priority field in the OBs ?

• N/A

If this is a run that requires coordinated observations with other facilities,
 did you give proper instructions in the Time-Critical Aspects Section ?

• N/A

If you have PSF reference star OBs, do the names of those OBs begin with
 PSF_ ?

• N/A

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)
 ?

• YES

Have you clearly marked and labelled your wavefront reference objects
 R1, R2, R3, ... (as specified in the NAOS Preparation Software) on your Finding
 Charts ?

• YES

Have you specified the magnitude of the brightest object in the field-of-view
 for each OB ?

• YES

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
 ?

• NO

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 ?

• N/A