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

Principal Investigator Email Address

• stumpf@mpia-hd.mpg.de

Estimated Total Execution Time (hours, including overheads)

• 3:13h

General Description

• This run observes 4 different binary brown dwarfs in 4 different spectroscopical
   Obs. 
  For all cases we provide the position angle of the binary to the sky. If you can
   orient the binary components along the finer sampled X-axis without losing the TTS
   due to the limited range of the field selector, please try to do so. We also attached
   (at least for Kelu1 and 2MASSJ0310+1648) valuable magnified Finding Chart with the
   visible resolved binary.
  In all OBs the science object should be clearly visible during acquisition and should
   be centered in the array. Since we chose the 25mas resolution scale our target (and
   therefore = the brightest target) will be visisble in the FoV of 0.8" x 0.8"
  
    OB names		R (TTS)		target				separation	comments
    -----------------------------------------------------------------------------------------------------
    Kelu1			14.42		K~ 11.5				27.66 arcsec	
    2MASSJ0310+1648	16.91		K~ 14.2				47.16 arcsec
    DENIS 1859-3706	16.02		I~ 17.1 (potentially K~ 14.1) 	27.00 arcsec	TTS is galaxy
    SDSS 0423-0414	17.95		K~ 13.2				44.72 arcsec 	TTS is galaxy
  
  we know, that the TTS for OB SDSS0423-0414 might be a little bit faint, but its
   the only guide star in the permitted radius for a TTS. Since the science target
   is very interesting its still worth trying.
  
  The OBs: Kelu1, DENIS1859-2706 and SDSS0423-0414 contain 10 dither points in total
   (for each OB). 8 science dither points and 2 sky-dither points (one in the middle,
   one in the end). Only OB 2MASS0310+1648 has a 9 ditherpoint pattern (only 1 sky)
   due to time constraints.
  The goal is to stack together all the science output of one OB to achieve the necessary
   S/N ratio for data reduction.

Waiver Requests

• waiver request with WaiverID 078.C-0123A.01
  for OB 250579 with total execution time of 1:05:25 
  was submitted on August 3rd 2006  at 09:36am
  and approved on August 3rd 2006  at05:05pm
  
  waiver request with WaiverID 078.C-0123A.02
  for the whole run with total execution time of 1:12:52
  was submitted on August 19th 2007 at 07:37pm
  and approved on August 22nd 2007 at 09:35am

Critical Observing Condition Constraints

• Since the contrast and resolution are very dependent on the ambient conditions,
   we
  ask the night astronomer to feel free to adapt the observational strategy
  (DIT/NDIT) to optimize the observations.
  
  Thank you for your cooperation!

Time-Critical Aspects

• N/A

Special Execution Requirements

• N/A

Special Calibration Information

• N/A

ToO Information

• N/A

ToO Activators List

• N/A

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• N/A

Source(s) of Pre-imaging

• ---(Empty)---

Pre-imaging sources not listed above

• N/A

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?

• 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

Did you indicate the magnitude of the brightest object in the field in
 each SINFONI OB?

• YES

If you are using the AO: Did you indicate for every OB the magnitude
 of the guide star, and its distance to the target (if any)?

• YES

If you submitted OBs for standard stars, did you use the provided StandardStar
 templates?

• N/A

If you are using a specific offset pattern or position angle: did you
 check carefully the definition in the manual?

• YES

Did you make really sure that none of your OBs ever saturates the detector?

• YES

If you are using the AO: did you enter the correct Strehl Ratio (on-axis,
 K-band) AND the seeing value in the constraint set?

• YES