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

Principal Investigator Email Address

• prieto@mpia.de

Estimated Total Execution Time (hours, including overheads)

• 13

General Description

• Broad-band (JKLM) imaging program of bright AGN: JK imaging in one OB/target
   of ~1 hr duration, L imaging in a separate OB/target of 45min to 55 min, depending
   of target, and finally, M-band (via NB at 4.05um, see below)  in a separate OB/target
   of ~1 hr.
  Acquisition is to be done with move-to-pixel: this is to get the galaxy peak to
   the center of the array. A further movement is needed only in the  case of N7469:
   in this case, with move-to-pixel, get the galaxy peak to the center of the array,
   then move ~ -5"  RA and ~ +5" DEC aprox: this is to get the very faint star N-W
   of the galaxy peak in all science frames.
  The AGN nucleus is taken as the reference source in all cases. Generic-offset templates
   are used to get separate skies. The pattern in the generic offset is a square with
   9 positions and five sky offsets located in a pentagon shape.
  The optical wavefront sensor is used in all cases, except for NGC7582. This target
   has given problems with the optical wavefront sensor.
  DIT values in all cases are derived from NICMOS data. Please check for saturation
   in the acquisition and adjust DITxNDIT to get optimal values of counts per frame
   below the linearity limit. Also in cases where NDIT is small, please decrease DIT
   (e.g. by one half) and increase the number of exposures in order to avoid saturation.
   In none of the fields there are objects brigther than the allowed NACO limits. Due
   to the persistent problems with choping in M-band, we decided to use NB 4.05um and
   auto-jitter instead.

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• n/a

Time-Critical Aspects

• n/a

Special Execution Requirements

• Acquisition is done via move-to-pixel just to center the galaxy nucleus
   at about the center of the array. The chosen DIT value is a best estimate: Please
   check for saturation in the acquisition and adjust DITxNDIT to get optimal values
   of counts per frame below the linearity limit. Also in cases where NDIT is small,
   please decrease DIT (e.g. by one half) and increase the number of exposures in order
   to avoid saturation.
  N7469: With move-to-pixel, get the galaxy peak to the center of the array, then
   move ~ -5"  RA and ~ +5" DEC: this is to get the very faint star N-W of the nucleus
   in all science frames.

Special Calibration Information

• ZPs of the night are needed.

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 ?

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

• YES

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 ?

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

• 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