README web version of /home/usg/OPS/MTS/readme_xml/readme_75502500
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
We want to observe pluto+charon, to prepare the occultation of next July,
11th, where Charon will occult a K=12.2 star.
GOAL : observe the relative position of CHARON wrt PLUTO, with 0.001 arcsec accuracy
(~ 1/15th pixel in S13).
WHEN : on June 9th 5:00 UT (when Charon is at the **SAME** orbital phase than for
the occultn of July 11th, 3:37 UT).
SPECIAL NEEDS : C A L I B R A T I O N !!!.. we need to have a very good accuracy
on the detector pixscale (<0.1%) and orientation (better 0.1 deg). To do this,
we will observe a calibration double-star, where components are separated by 14.33
arcsec. As the field of S13 is only 13.56 arcsec, it will be rotated so that both
component fit in the diagonal.
Waiver Requests
Critical Observing Condition Constraints
Time-Critical Aspects
TIME CRITICAL: to be observed in the night from 8 to 9 June 2005 (= 2005-06-09
UT:05:00)
The Pluto/Charon observation (OB called "pluton") will start on 2005-06-09 UT:04:30
and stop on 2005-06-09 UT:05:30.
OBSERVATION :
3:45 = observation of calibration star (OB called "calibstar")
4:30 = observation of Pluto (OB called "pluton")
5:30 = end
Observation of calib star must be done BEFORE, otherwise the airmass is too high
(airmass > 2.00)
Special Execution Requirements
Pluto/Charon will be observed, closing the loop on (Pluto/Charon), mV=14.0
The calib star will be observed, closing the loop on the brightest star (mV=14.8).
This calib star is a DOUBLE STAR, 14.33 arcsec apart.
A POSITION ANGLE of -17.2 deg has been defined in the OB, so that both component
fit in the DIAGONAL of the field.
I hope I didn't make any mistake in the choice of "-17.2 deg".
If you think there's a mistake, feel free to modify the position angle : what is
important is just that BOTH COMPONENTS OF THE STAR FIT IN THE FIELD (have a look
at the finding chart).
Special Calibration Information
ToO Information
ToO Activators List
Is this a Pre-imaging run ?
Pre-imaging Requirements
Source(s) of Pre-imaging
Pre-imaging sources not listed above
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 ?
Do all your finding charts comply with both the general and instrument-specific
Phase 2 Web Pages ?
If you submitted OBs for standard stars, did you specify the magnitude
and spectral type of all standard stars in the OBs ?
Have you included OBs for any calibrations that you need but which are
not part of the Calibration Plan ?
If you are observing Moving Targets, have you attached suitable ephemeris
files to your OBs?
If you have preferences which OBs should be executed first, did you make
use of the User Priority field in the OBs ?
If this is a run that requires coordinated observations with other facilities,
did you give proper instructions in the Time-Critical Aspects Section ?
If you have PSF reference star OBs, do the names of those OBs begin with
PSF_ ?
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)
?
Have you clearly marked and labelled your wavefront reference objects
R1, R2, R3, ... (as specified in the NAOS Preparation Software) on your Finding
Charts ?
Have you specified the magnitude of the brightest object in the field-of-view
for each OB ?
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 ?
Last creation of page: Tue Oct 6 15:40:09 2009
If you have comments, please contact usd-help@eso.org