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

Principal Investigator Email Address

• pschuller@cfa.harvard.edu

Estimated Total Execution Time (hours, including overheads)

• 2h

General Description

• General remarks
  ---------------
  For this DDT run a very non-standard setup is used, and most of the setups
  need to be done manually.  From 15-25 July 2006 Chris Lidman (shift leader)
  and Oliver Marco (UT4 night astronomer) will be on Paranal and it is agreed
  that they will take care of these observations.  Note that the target is
  setting, take advantage of twilight. Allocated time 2h. Good and stable AO
  correction is critical - the dectection of a putative companion will be at
  the limit.
  
  Do not hesitat to call:
  +56-2-4633071 (office)
  +56-2-2161742 (home)
  +56-91359374  (mobile)

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• Very special setup. Observations need to be done mostely manually. See
   Special Execution Requirements.

Time-Critical Aspects

• Time-critical programme, setting target.

Special Execution Requirements

• Summary of OBs
  -------------
  arcturus_3rot_HK_A
  arcturus_3rot_HK_B
  
  arcturus_3rot_HK_A 
  ---- 
  The OBs can only be used for the acquisition, then ALL SETUPS NEED TO BE DONE
  MANUALLY, since 128x128 HW windowing and readout mode Uncorr & HighBackground
  cannot be set in the OBs! Furthermore, HW windowing is switched back to SW
  windowing at the beginning of each template if the windowing option in BOB as
  hidden parameter is used! (This behaviour is due to current SW architecture).
  Note that the setting for the readout mode, DIT and NDIT need to be modified
  manually as described further below.)
  
  Nevertheless, the OB reflects the observing strategy, i.e, acquisition, and
  then 3 rotator angles with exposures for the 2 NB filters NB_1.64 and
  NB_2.17. At the end of the sequence skyframes taken for both filters. For a
  detailed description read below (Strategy).
  
  arcturus_3rot_HK_B
  ----
  This OB is a clone of A, since the complete observing sequence should be
  repeated.
  
  
  Strategy
  ========
  Only the acquisition part of the OBs can be used, everything else needs to be
  set manually. The config file is prepared to use N90C10 and Dens-100, take
  care that these setting are used, do not optimize.
  
  No offsets, object should be always roughly centered in the FOV. Sky field at
  the end of the OB.
  
  After acquisition:
  ------------------
  - switch to 128x128 HW (Attention for skipped line: 128x130!)
  - set DIT 20msec
  - select readout mode Uncorr, HighBackground
  - verify settings (particularly readout mode in the FITS header of data, since
    the readout mode might not be displayed properly)
  - remove ND
  
  - recenter object if necessary after rotation
  
  rot 00, NB_1.64:  take 5 obj cubes (2000x20msec, each cube) 
  rot 00, NB_2.17:  take 5 obj cubes (4000x10msec) 
  
  rot 33, NB_2.17:  take 5 obj cubes (4000x10msec) 
  rot 33, NB_1.64:  take 5 obj cubes (2000x20msec) 
  
  rot 66, NB_1.64:  take 5 obj cubes (2000x20msec) 
  rot 66, NB_2.17:  take 5 obj cubes (1000x10msec) 
  
  - move object out FOV for the sky exposures
  
  rot 66, NB_2.17:  take 5 sky  cubes (1000x10msec) 
  rot 66, NB_1.64:  take 5 sky  cubes (2000x20msec) 
  
  
  This is the end of the first sequence (arcturus_3rot_HK_A), now go back to
  object and back to rot angle 00 deg and repeat the sequence
  (arcturus_3rot_HK_B) in the same order (no acquisition). At the end of the
  second sequence (arcturus_3rot_HK_B) the sky frames may be skipped, if no
  time.
  
  PSF star
  --------
  PSF_A (interferometric calibrator from Borde et al. 2002. V=4.1, K=0.4,
  Spectral type: K5.5III)
  PSF_B (backup)
  PSF_C (backup)
  
  Two OBs are prepared for a PSF. Please use PSF_A only! PSF_B and C are backup
  in case there is a problem with PSF_A. Note that the first impression might be
  that you caught a binary, but normally it is just an aberration (trifoil or
  coma).
  
  Again, the OBs can only be used for the acquisition and then everything needs
  to be done manually. The strategy/setup is IDENTICAL as for the target, but
  only one sequence of rotator angles (00, 33, 66 deg) is needed, and the DIT
  will be around 0.05 sec (pls adjust to be in the linear domain), hence for
  each rotator and filter setting 1 datacube (600x0.05sec; in total 30sec
  exposure, adjust for the different filters) should be taken. Same for the
  skyframes at the end of the rotator sequence.
  
  
  Exposure time estimate
  ----------------------
  15 min acquisition
  
  (time including overheads estimated from aborted run in Aug 2006)
  
  time to register 1 cube 
  ----
  2000x20msec cube (for NB_1.64): 60sec
  4000x10msec cube (for NB_2.17): 90sec
  
  
  time for 1 rot pos, 2 filters: 5x(60+90) + 30sec [overhead filterchange] =
  780sec
  time for 3 rot pos, 2 filters: 3x780sec + 200sec [overhead rotator +
  re-centering] = 2540
  
  for second sequence no acquisition (15min) => 2540sec-15*60sec=1640sec
  
  total:
  sequence 01: 2540sec
  sequence 02: 1640sec
               -------
               4180sec (70min)
  
  In the remaining time the PSF star will be taken.
  
  
  Further notes:
  ==========================
  - It was checked that 2000x20msec and 4000x10msec cubes can be registered
    (there will be just some missing frames, but this is ok).
  
  - Always check setting HW128x128, Uncorr, HighBackground. Remember, that HW
    windowing is set back to SW at the beginning of each template!

Special Calibration Information

• Dark cubes with the same setting. Flat cubes. They need to be taken manually.
   Details can be coordinated with Markus Hartung (mhartung@eso.org) once the DDT was
   succesfully executed.

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 ?

• N/A

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
 ?

• N/A

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