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

Principal Investigator Email Address

• a.cimatti@unibo.it

Estimated Total Execution Time (hours, including overheads)

• 24

General Description

• K-band AO observations of two z=2.5 galaxies (detected already in non-AO
   mode).
  
  There are 8 equal OBs for GK2562 in LGS mode. There are 9 equal OBs for GK2363 in
   NGS mode. A tenth OB is cut short to 4 exposures (instead of 6) to keep within the
   time constraints (a DIT of a little less than 600s would have been preferred but
   is not allowed). This tenth OB should preferrably be carried out directly after
   another OB of the series in order to be able to do sky subtraction on the combined
   observations from these (two or more) OBs.
  
  No priorities have been set but the OBs should preferrably be carried out in order
   of numbering. LGS OBs should be carried with higher priority than NGS OBs as the
   time available for LGS observations is less, but we guess that ESO's internal priority
   for LGS observations is higher than for NGS observations and will automatically
   take care of this.
  
  OB names       R (NGS)    target       separation     comments
  --------------------------------------------------------------------
  CDFS-GK2363*   13.5       K=20.9       16.35"         spatial extent < 1.3",
   NGS mode
  CDFS-GK2562*   17.1       K=20.5       19.55"         spatial extent < 1.3",
   LGS mode
  None of the NGSs and targets is brighter than 6th magnitude in the NIR.
  Magnitudes are in the Vega system. R magnitudes are from the USNO catalog. 
  K magnitudes are from our own measurements on the ISAAC Ks band images of CDFS.
  
  The TGS is specified in all OBs, but should this TGS be unsuitable, it is fine for
   the TO to pick another one but all subsequent OBs for this target *need* to use
   this exact same TGS.
  During phase2 preparation a problem turned up with P2PP saying that the only two
   possible TGSs were unacceptable due to vignetting even though they were more than
   4' away. This problem has been solved after communication with the USD.
  
  Finally, we would like to note that for GK2562, the only suitable star for AO is
   rather faint for NGS/LGS.  However, we succesfully carried out preliminary SINFONI
   NGS-AO observations during our previous P78 run of this source using this NGS in
   particular.  Some members of our
  team also have further experience with SINFONI AO observations with NGS and TTS
   of comparable magnitudes and at similar distances. We are aware that the star's
   faintness may affect the AO performance but based on our previous experience we
   expect an effective angular resolution of 0.1"-0.2", which still meets our scientific
   requirements. We trust the observers carrying out our service mode program will
   do their best for these observations of GK2562.

Waiver Requests

• 080.A-0635B.01.WAV
  
  OBs longer than 1h allowed
  Use of LGS mode allowed

Critical Observing Condition Constraints

• The constraint for the Strehl has been set to the ETC-predicted value
   for the seeing and R-mag of the NGS that are specified, but at least equally important
   is the coherence timescale which should be long to ensure good AO performance.

Time-Critical Aspects

• None

Special Execution Requirements

• As GK2363_K-NGS-100mas-10 contains only 4 exposures (instead of 6), it
   would be best if this OB is carried out directly after another OB if the GK2363
   series is carried out to be able to do sky subtraction on the combined exposures
   of both OBs.

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

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

Did you indicate the magnitude of the brightest object in the field in
 each SINFONI OB?

• YES

If you are using the AO: Did you indicate for every OB the magnitude
 of the guide star, and its distance to the target (if any)?

• YES

If you submitted OBs for standard stars, did you use the provided StandardStar
 templates?

• N/A

If you are using a specific offset pattern or position angle: did you
 check carefully the definition in the manual?

• YES

Did you make really sure that none of your OBs ever saturates the detector?

• YES

If you are using the AO: did you enter the correct Strehl Ratio (on-axis,
 K-band) AND the seeing value in the constraint set?

• YES