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

Principal Investigator Email Address

• bcarry@eso.org

Estimated Total Execution Time (hours, including overheads)

• 0.7

General Description

• Orbital Characterization of the 2003 EL61 binary system
  
  It's a direct imaging program, to be performed with the high angular-resolution
   platescale (S13).
  During acquisition, only one body is expected to be seen (2003EL61 itself - K-mag
   ~ 16) )
  Both satellites will appear in the long exposure frames.
  
  Beware, the target is moving on sky. We provided ephemeris with a 1-hour step,
  corresponding to an apparent motion of no more than 3" on sky.
  It is more precise than required, but will hopefully helps the night astronomer
   to easily find the target.
  
  The targets is its own wavefront sensor TTS, we thus did not indicated any TTS on
   the finding charts.
  
  Although finding chart are not required for moving targets, we provided FCs along
   the path of our moving target to help discriminate with background stars. We provide
   4 FCs (maximum allowed) until June 19.
  In the case the run D is executed after June 19 (giving the C-run date), we can
   quickly provide finding charts covering the last days of June under request.

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• We need the observation to be performed with a maximum guide probe seeing
   of 0.8" in order to get the proper angular
  resolution for our study. The airmass is required to be better than 1.5 for the
   same reason.

Time-Critical Aspects

• The target visibility decreases rapidly until end of June.
  It is thus important for our program to perform the observations as soon as possible.
  
  In order to recover the target's satellite orbits, we need the 4 runs to be separated
   by at least 4 days.
  Because the target will be barely observable after June 30, we thus request this
   first run to be performed before June 10. Otherwise, it would be difficult to perform
   runs C, B and D. 
  But some data are better than no data at all, thus feel free to execute as many
   observations as possible, even if not all of them can be completed before the target
   becomes unvisible.

Special Execution Requirements

• ---(Empty)---

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?

• YES

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 ?

• N/A

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

• N/A

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