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

Principal Investigator Email Address

• ohainaut@eso.org

Estimated Total Execution Time (hours, including overheads)

• 0.92h

General Description

• This DDT program aims at measuring directly the diameter of the largest
   TNO known to date (2004 UB313) and detect its satellite. This is a time critical
   program which must be executed on the night of Sunday November 13, when the separation
   between the TNO and the appulse star is minimum (16"). 
  
  - OB 2003UB313-NACO uses a nearby star (G0 H=10.6) to lock the AO system. Acquisition
   is done on the star, then we offset to the field of the TNO. The last template goes
   back to the AO star in order to calibrate the AO performances. 
  - OB CAL_NGC288_68 (star:G6 H=11): This OB is used to calibrate the performance
   of the AO system at various distances from the AO guide star. We use a star (#68)
   from the globular cluster NGC288 to lock the AO system. Then we offset to nearby
   fainter stars to calibrate the aberrations. Note that the magnitude for these fainter
   stars is not know, therefore, please decrease the DIT in case we are close to saturation
   (which is not really likely though). 
  
  Important note: In case the observations cannot be done on the night of Sunday November
   13 (bad meteo conditions), then should be attempted the night after.

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• Good seeing conditions (0.8" or better) are required. 
  
  If the seeing is fast (about 2ms or less), please switch to K band filter instead
   of H band for the science and calibration OBs.

Time-Critical Aspects

• This DDT program must be executed on the night of Sunday Nov. 13, 2005,
   when the distance between the AO guide star and the TNO is minimum (16"). If, for
   some reasons, the execution must be postponed, then a last attempt should be made
   the night after (Monday Nov. 14) while the separation is 40". After these two dates,
   the program will not be feasible anymore (distance too large between the AO star
   and the TNO). A Finding Chart has been provided for the science OB, that shows the
   path of the target wrt the AO guide star. 
  
  Note that the ephemeris file contains the coordinates for the moving target for
   the dates of Nov. 14-15 (UT), as well as separation and RA/DEC offsets from the
   AO guide star. 
  
  An additional science OB (2003UB313-NACO-Nov15) has been provided in case the observations
   happen on Nov. 14 (local) instead of Nov. 13 (local). The aocfg file for each science
   OB contains the target coordinates for the corresponding date and does not need
   to be edited. The offset values in the last template of the science OB (to record
   the PSF quality) also correspond to the offsets for the dates and do not need to
   be edited. The tracking tables in the aocfg file also contain the offsets values
   corresponding for the dates.

Special Execution Requirements

• We provide a tracking table in the aocfg file of the science OB to take
   into account the relative motion of the TNO wrt the AO guide star.

Special Calibration Information

• A calibrator OB has been provided and aims at measuring the changes in
   the PSF aberrations in function of the distance from the AO guide star.

ToO Information

• N/A

ToO Activators List

• N/A

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• N/A

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 ?

• YES

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

• YES

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