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

Principal Investigator Email Address

• alain.doressoundiram@obspm.fr

Estimated Total Execution Time (hours, including overheads)

• 06:58:35

General Description

• Astrometry, photometry and spectroccopy of the TNO 1999TC36 which is actually
   double.
  The aim is the obtain of sciences data of both.
  The pre-imaging run A must be scheduled before these OBs.
  Those pre-images will serve to safely identify the moving target during the conjunction
   night.
  The order of each OB is mandatory (see time intervals in each OB) to get both our
   science and 
  calibration targets at the right airmass and also in order to monitor the right
   portion of the 
  surface of the TNO.

Waiver Requests

• 076.C-0801B & C.01.WAV APPROVEDS 
  
  "Finally I received the approval for your waiver request.
  
  What will happen is the following:
  
  Unless there is an A-ranked program which cannot otherwise be completed,
  your programs will be executed on the required dates, if observing
  conditions are within your constraints."

Critical Observing Condition Constraints

• We need at least clear conditions for photometry and spectroscopy.
  However, spectroscopy can be performed with thin cirrus.
  
  Tracking table was made with offsets differences equal to coordinates of: (reference
   star) - (moving target)
  
  Pre-images don't show any star in the FOV

Time-Critical Aspects

• Our OBs must be executed at indicated date during the stellar conjunction
   night.
  Our OBs must also be executed within specific time interval and specific sequence.
  
  The schedule of the sequence is (night of  13 oct 2005 to 14 oct 2005 in UT TIME):
  Flexibility of the schedule is about 10-15 min per each OB.
  If these 10-15 minutes are run out, stop the OB and start the next.
  14 oct 2005 at 00h30 UT: CAL_S754C (mJ:11)
  00h50: CAL_spec_HD195458 (mV:9.98)
  01h10: MOV_1999tc36JHKs
  02h00: MOV_1999tc36Jspec
  02h40: MOV_1999tc36HKspec
  03h35: MOV_1999tc36JHKss
  04h30: CAL_spec_Land93101 (mV:10)
  04h50: MOV_1999tc36Jspecs
  05h30: MOV_1999tc36HKspecs
  06h25: CAL_FS03 (mJ:12.6)
  06h45: CAL_FS06 (mJ:13.2)
  07h05: CAL_spec_Land93101s (mV:10)

Special Execution Requirements

• In case of problem in the completion of this run, preference should be
   given to the spectrocopic OBS 
  (both science and calibration).
  
  1999TC36 is a Kuiper Belt Object that has a companion.
  Modify the rotation angle, and put the slit in the aim to have the spectra of the
   two bodies (1999TC36 1 and 2) 
  Note: Estimated magnitude of 1999TC36-1 and 2: mJ1=17.5, mH1=17.1, mK1=17.1 and
   mJ2=19.7, mH2=19.3, mK2=19.3
  and maximum elongation is about 0.29"
  
  All the spectroscopic calibrator were checked (no binaries)

Special Calibration Information

• We have submitted OBs for photometric calibration and spectrocopic analogs.
  Photometric calibration permit us to perform best photometric measurements in the
   case where the night is not 
  photometric (e.g: clear sky condition).
  The order and timing of each calibration OB is mandatory to monitor the science
   target in the same weather 
  conditions.

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 ?

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

• 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