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

Principal Investigator Email Address

• benoit.neichel@obspm.fr

Estimated Total Execution Time (hours, including overheads)

• 08:57:09.0 hours

General Description

• The forseen objective of these observations is to obtain high resolution
   images of 3 galaxies.
  We dispose of 9hours in total, 3hours per galaxy = 3 OBs per galaxy = 9 OBs in total...
  For each galaxy, the 3 corresponding OBs are identical. They have the same name
   following by -1; -2; -3. 
  For instance, in the case of the object CDFS32925, the OBs are respectivly named
   CDFS32925-1, CDFS32925-2, CDFS32925-3.
  
  The three galaxy are very faint object (mk>20), so the completion of the 3 OBs
   is necessary to reach a reasonable S/N. In that way we have given one user priority
   per object, hopping that each serie could be complete.
  
  FOR THE ACQUISITION TEMPLATE :
  PLEASE SEE THE "SPECIAL EXECUTION REQUIREMENTS" SECTION.
  
  FOR SCIENCE TEMPLATE :
  The objects we want to observe are located near their reference star (few tenth
   of arcsec). In order to avoid the Reference Star in the CONICA field, we have adjusted
   a generic offset composed of at least two positions.
  But, we also want to take images of the reference star (with adapted DIT) to obtain
   information about the PSF structure. 
  In that way our science template is divided in three "generic_offset" templates.
  First template (#1) aims of taking images of the target with apropriate offsets.
  Second template (#2) permits to shift the field on the Reference star and takes
   few images of it.
  Finally, third template (#3) is identical to the first.
  
  Following this strategy we will be able to have both sky and PSF structure information.

Waiver Requests

• No Waiver Request was submitted

Critical Observing Condition Constraints

• No special critical observing constraints.

Time-Critical Aspects

• No time critical aspect.

Special Execution Requirements

• FOR ACQUISITION TEMPLATE :
  
  The scientific target (galaxy) is too faint (integrated mK>>20) to be detected
   during acquisition.
  
  In order to center the scientific target in the field, we have defined our OBs so
   that 
  - you center the guide star (mK=12) right in the wavefront sensor field stop ,
  - .. then NAOS will offset the conica fov towards the galaxy according to the coordinates
   taken from the .aocfg : DON'T TRY to do offsets nor search for the object or center
   whatever : you can't see it anyway. TRUST the coordinates, and JUST ANSWER "OK".
   Otherwise you may miss the galaxy.
  
  Notice that the coordinates of the "scientific target" defined in the .aocfg define
   the center of the S27 field : they're not the exact coordinates of the galaxy. We
   do this because we don't want the galaxy to be in the center of the field, in order
   to avoid the (bright) guide star in our field.
  We have verify that this strategy do not change the AO configuration of NAOS.
  
  The DIT and NDIT of the acquisition template are set to be able to properly see
   the reference guide star ; not the galaxy (hopeless anyway)

Special Calibration Information

• ---(Empty)---

ToO Information

• ---(Empty)---

ToO Activators List

• ---(Empty)---

Is this a Pre-imaging run ?

• false

Pre-imaging Requirements

• ---(Empty)---

Source(s) of Pre-imaging

• NACO

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 ?

• 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