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

Principal Investigator Email Address

• pierre.kervella@obspm.fr

Estimated Total Execution Time (hours, including overheads)

• 5.0

General Description

• With these NACO observations, we aim at obtaining ultra-precise differential
   astrometry of the two main components of Delta Vel (the eclipsing pair Aab on one
   hand and B on the other hand). For this purpose, we want to record a series of short
   exposures over 10 epochs of the orbital period of the eclipsing binary Aab (P=45
   days). One epoch is specifically constrained in time to be executed during the primary
   eclipse of 18 May 2008. The other OBs can be executed randomly over the period,
   with an interval of at least one day between two consecutive observations (two OBs
   should not be executed the same night).
  
  The OBs are prepared to match the procedure for NACO astrometry described by Seifahrt
   et al. (2007, http://fr.arxiv.org/abs/0706.2613). The sky background is not a problem
   for us, and for this reason, the OBs are "staring" at the binary without any jittering
   offset.
  
  ACQUISITION: The main component A (the eclipsing system) should be selected during
   the acquisition to fall on a fixed target pixel of CONICA. The A component is the
   brightest star in the field. Please always precisely center this component A (which
   is also the AO reference R1) on the detector pixel 660/460. This pixel should be
   a "good" pixel. If it turns out that pixel 660/460 is "bad" or that the region where
   component B falls onto is "bad", then move to a "good" spot, note the pixel coordinates
   and notify USD (so that the README file can be updated accordingly). THANKS! :-)
  
  The magnitude of the brightest object in the CONICA field of view is Delta Vel Aab,
   with K ~ 2.0 (V ~ 2.1).

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• There are no critical observing condition contraints.

Time-Critical Aspects

• One OB is intended to be executed during the eclipse of the Aab star occurring
   on 18 May 2008: the corresponding time constraints are specified in the OB. We know
   that according to the current schedule
  there is VLTI SM on May 18, but in case of short-term changes in the schedule, please
   try to 
  execute the OB Delta_Vel-PrimEclipse - it is very important for our programme, thanks!

Special Execution Requirements

• ACQUISITION: The main component A (the eclipsing system) should be selected
   during the acquisition to fall on a fixed target pixel of CONICA. The A component
   is the brightest star in the field. Please always precisely center this component
   A (which is also the AO reference R1) on the detector pixel 660/460. This pixel
   should be a "good" pixel. If it turns out that pixel 660/460 is "bad" or that the
   region where component B falls onto is "bad", then move to a "good" spot, note the
   pixel coordinates and notify USD (so that the README file can be updated accordingly).
   THANKS! :-)

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 ?

• YES

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