README web version of /home/usg/OPS/MTS/readme_xml/readme_82046801
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
We want to take images in J- and K-band of the nuclear star clusters in
the nearby galaxies NGC7793, NGC5206, and NGC300.
Judging from HST and 2MASS images, these clusters should be compact and bright enough
to directly use as a reference source for the adaptive optics correction (R1). In
case the AO-loop cannot be closed while guiding on the nuclear star cluster (R1)
itself, the choice would be to guide on a nearby star (R2). This can be done for
NGC5206 and NGC300 (the optional wavefront references (R2) are indicated in the
finding charts, and we give their coordinates and magnitudes below).
Unfortunately, no NGS is available within <55" for NGC7793. In case the AO-loop
fails to close on the nuclear cluster itself, this object cannot be observed in
AO mode.
The priority of the OBs is stated via the User Priority field in the OB.
In each case, the brightest object in the field-of-view is the nuclear star cluster.
We give the 2MASS magnitudes (which probably under-estimate the brightness):
NGC7793: Kmag~ 12.5 Jmag~ 13.4
NGC5206: Kmag~ 12.4 Jmag~ 13.3
NGC300 : Kmag~ 13.9 Jmag~ 14.6
In case the nuclear clusters are not compact or bright enough to serve as a wavefront
reference,
the alternative reference stars are:
For NGC 5206: 2MASS 13334169-4808551 at RA: 13:33:41.69 DEC:-48:08:55.2 with a
Kmag ~ 13.5
For NGC 300 : 2MASS J00545263-3741486 at RA: 00:54:52.9 DEC:-37:41:49.1 with a
Kmag ~ 13.8
The AO preparation software suggests to use the visible wavefront sensor, but we
are not sure whether this is the best choice, since we do not have reliable optical
magnitudes for the targets. Please use the wavefront sensor that provides the best
AO correction.
Waiver Requests
Critical Observing Condition Constraints
Time-Critical Aspects
Special Execution Requirements
Special Calibration Information
ToO Information
ToO Activators List
Is this a Pre-imaging run ?
Pre-imaging Requirements
Source(s) of Pre-imaging
Pre-imaging sources not listed above
Do all your OBs comply with the instrument-specific requirements listed
on the instrument-specific Phase 2 web page ?
If this is a pre-imaging run, did you select PRE-IMAGING for the Observing
Category for each Observing Template ?
Do all your finding charts comply with both the general and instrument-specific
Phase 2 Web Pages ?
If you submitted OBs for standard stars, did you specify the magnitude
and spectral type of all standard stars in the OBs ?
Have you included OBs for any calibrations that you need but which are
not part of the Calibration Plan ?
If you are observing Moving Targets, have you attached suitable ephemeris
files to your OBs?
If you have preferences which OBs should be executed first, did you make
use of the User Priority field in the OBs ?
If this is a run that requires coordinated observations with other facilities,
did you give proper instructions in the Time-Critical Aspects Section ?
If you have PSF reference star OBs, do the names of those OBs begin with
PSF_ ?
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)
?
Have you clearly marked and labelled your wavefront reference objects
R1, R2, R3, ... (as specified in the NAOS Preparation Software) on your Finding
Charts ?
Have you specified the magnitude of the brightest object in the field-of-view
for each OB ?
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
?
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 ?
Last creation of page: Tue Oct 6 15:40:27 2009
If you have comments, please contact usd-help@eso.org