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

Principal Investigator Email Address

• cdumas@eso.org

Estimated Total Execution Time (hours, including overheads)

• 0.79

General Description

• This programs aims at imaging in H-band the MOVING TARGET asteroid Daphne
   (V~10) and its satellite (V~18, separation 0.3-0.5") at eight orbital positions
   of the satellite. The observations should be executed ASAP (preferably before June
   1, no later than June 17).
  
  Each Science Target OB is named "MOV_Daphne_xxx", where "xxx" corresponds to the
   approximate orbital longitude of the satellite for eight positions spaced by 45
   degrees (i.e. xxx=[0,45,90,135,180,225,270,315] deg).
  
  A single science OB "MOV_Daphne_xxx" and its corresponding PSF OB "PSF_Daphne_xxx"
   should be executed for each run. The PSF should be executed immediately after the
   science OB. 
  
  For each sciece OB, we obtain a series of *non-saturated* images of the asteroid
   (feel free to adjust the exposure time if needed to prevent saturation), then a
   series of deeper images for which the asteroid is *saturated* (to detect the satellite
   with a better SNR). 
  
  
  - No Finding Chart is provided for the asteroid because it's a moving target. If
   a star turns out to be present within a few arcsec of the asteroid, please do not
   continue and wait for the next available run, that the target has moved. 
  - Each pair of Science+PSF OBs can be executed independently. 
  - Several Science OBs (i.e. runs) can be executed in a single night.
  - Please refer to the ephemeris file in order to select the OB to execute for a
   specific date & time. The OB name corresponding to the satellite position is
   indicated for each date.
  
  Finally, *do not forget* to update the RA/DEC of the asteroid in the "aocfg" file
   and its PPM_RA and PPM_DE in Bob (acquisition template), which are listed in the
   ephemeris file for each date & time. 
  
  Thank you.

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• Good seeing (<0.8" or better), CLR conditions

Time-Critical Aspects

• This is a time criticial set of observations
  Observations should be executed ASAP, preferably before June 1, and no later than
   June 17 (then satellite's separation becomes too small).
  Please refer to the ephemeris file to know which Science OB should be executed at
   a given time

Special Execution Requirements

• Time critical

Special Calibration Information

• Each science OB should be immediately followed by its corresponding PSF
   OB

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 ?

• YES

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

• YES

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