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

Principal Investigator Email Address

• rne@astro.uni-jena.de

Estimated Total Execution Time (hours, including overheads)

• 14.0

General Description

• Simple Imaging Observations.
  
  Very bright targets are observed with the NB_2.17 Filter to not saturate the detector.
  
  HD 203030 is observed using the S27 camera, as the sub-stellar companion is 11.9
   arcsec to the east,
  all others with S13.
  
  There are always two objects to be observed, pls make sure that both are in the
   FoV in all images.
  
  Very red faint targets are observed with the IR WFS to get a better S/N, others
   with optical WFS.
  
  All our targets need an astrometric calibration to be observed in the same night.
   
                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  We suggest an approriate astrometric calibrator OB in the table below.
  
  But if that star is not visible well, then pls observe any other astrometric calib
   OB:
  HIP 73357 or HIP 6445 or HIP 51416.
  HD203030 as only S27 target has its own astrometric calibrator HIP 118018.
  
  OB      OBJECT      CALIBRATOR OB     CENTERING COMMENTS
  ------  ----------  ----------------  -------------------------------------
  360200   1RXSJ1609   CAL_HIP73357-*    
  
  360203   2M1207      CAL_HIP73357-*    
  
  360206   ABPic       CAL_HIP51416   Companion 5.5" S of star A. Put primary (target)
   in the upper half of FoV
  
  360228   CHXR 73   CAL_HIP73357-*       
  
  360231   CTCha     CAL_HIP73357-*
  
  360234   DHTau     CAL_HIP6445-*
  
  360237   GQLup     CAL_HIP73357-*
  
  360240   GSC08047  CAL_HIP6445-*
  
  360243   HD130948  CAL_HIP73357-*
  
  360246   HD203030_S27 CAL_S27_HIP118018 Companion 12" E of star A. Put Primary (target)
   in right half of FoV
  
  360249   HR7329    CAL_HIP6445
  
  360252   UScoCTI0108   CAL_HIP73357-*   Companion 4.6" S of star A. Put Primary
   (target) in upper half of FoV
  
  360209   HIP51416   -               astro cal double star target, NE star is AO
   reference, both stars in FoV !
  
  360211   HIP6445    -               astro cal double star target, NE star is AO
   reference, both stars in FoV !
  
  360214   HIP6445    -               astro cal double star target, NE star is AO
   reference, both stars in FoV !
  
  360215   HIP6445    -               astro cal double star target, NE star is AO
   reference, both stars in FoV !
  
  360216   HIP73357   -               astro cal double star target, NE star is AO
   reference, both stars in FoV !
  
  
  360219   HIP73357   -               astro cal double star target, NE star is AO
   reference, both stars in FoV !
  
  
  360220   HIP73357   -               astro cal double star target, NE star is AO
   reference, both stars in FoV !
  
  360221   HIP73357   -               astro cal double star target, NE star is AO
   reference, both stars in FoV !
  
  360222   HIP73357   -               astro cal double star target, NE star is AO
   reference, both stars in FoV !
  
  360223   HIP73357   -               astro cal double star target, NE star is AO
   reference, both stars in FoV !
  
  360224   HIP73357   -               astro cal double star target, NE star is AO
   reference, both stars in FoV !
  
  360225   HIP118018  -               astro cal double star target, NE star is AO
   reference, both stars in FoV !

Waiver Requests

• Setup Change request was approved
  to observe brightest targets in NB_2.17
  to observe faintest targets with IR WFS N90C10 or N20C80
  and to use S27 for the target HD 203030 with a companion 12 arc sec east

Critical Observing Condition Constraints

• No Critical Observing Condition Constraints

Time-Critical Aspects

• No Time-Critical Aspects

Special Execution Requirements

• ---(Empty)---

Special Calibration Information

• We always suggest one astrometric calibrator OB to be obsered in same
   night.
  
  But if that star is not visible well, then pls observe any other astrometric calib
   OB.
  HIP 73357
  HIP 6445
  HIP 51416
  HD203030, our only S27 target has its own astrometric calibrator HIP 118018.
  
  Thank you.

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 ?

• N/A

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?

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

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

• N/A

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