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

Principal Investigator Email Address

```
bruno.sicardy@obspm.fr
```

Estimated Total Execution Time (hours, including overheads)

```
2 hours
```

General Description

Observe the approach of system Pluto-Charon (0.56'' sep, mV=14.1, SP=G5)
 to star TYC5671-929-1 (mK=8.67, SP=M0). GOAL : improve pluto's ephemeris, and  Charon/Pluto's
 ephemeris. This is done in view of the STELLAR OCCULTATION BY CHARON OF JULY, 11th
 2005.
The observation is time-constrained. Should start on may 22th 2005, at UT=7h30 (pluto
 at approx 25 arcsec from star), should stop at UT=9h30 UT because of high airmass
 constraints (pluto at approx. 18 arcsec from star).
Speed of Pluto =-3.53 arcsec/hour in alpha.
We begin the observation by closing the loop on (Pluto+Charon), and we do autojitter
 on it during 1 hour. We observe SIMULTANEOUSLY the couple (Pluto+Charon) and the
 star, as we want to observe their relative movement. An accurate measurement of
 the pixel scale and frame orientation will be given by Pluto ephemeris (so that
 we don't need to calibrate on an astrometric field). We use a rotator angle of 45
 degrees on the sky in order that Pluto, Charon and the star can fit together in
 the field of the S27.
2nd part of the observation : same as 1st one, but now closing the loop on the star,
 when pluto is closer to the star.

Waiver Requests

```
No Waiver Request was submitted
```

Critical Observing Condition Constraints

no particular constraints, besides time (see Time Critical Constraints)

Time-Critical Aspects

Observation is time-constrained.
Should start at 7:30 UT, on MAY 22.
It stops at 9:30 UT.

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 ?

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 ?

```
N/A
```

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

```
N/A
```

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 ?

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
```

Last creation of page: Tue Oct 6 15:40:06 2009
If you have comments, please contact usd-help@eso.org