README web version of /home/usg/OPS/MTS/readme_xml/readme_81067201
Principal Investigator Email Address
Estimated Total Execution Time (hours, including overheads)
General Description
Information on targets and AO Reference Stars:
OB names R(AOstar) target separation comments
--------------------------------------------------------------------
COSMOS-ZC410123_LGSAO_P81-# 17.1 K=21.0 26 arcsec H_alpha: line at
2.100um
COSMOS-ZC409985_NGSAO_P81-# 13.4 K=20.6 17 arcsec H_alpha: line at
2.269um
COSMOS-ZC405226_NGSAO_P81-# 16.7 K=20.5 6 arcsec H_alpha: line at
2.158um
COSMOS-ZC407376_LGSAOSky_P81-# 16.6 K=19.8 22 arcsec H_alpha: line at
2.083um
N.B. The source ZC407376 is the exact same target as ZC772759 which appears in the
proposal. The new ID number comes from the most recent version of the zCOSMOS
source catalogue.
The main characteristics of the observations are as follows.
- The targets have the following priority:
1) COSMOS-ZC410123 : 4 OBs (LGS)
2) COSMOS-ZC409985 : 4 OBs (NGS)
3) COSMOS-ZC405226 : 4 OBs (NGS)
4) COSMOS-ZC407376 : 7 OBs (LGS)
These priorities are scientifically-driven.
However, if the LGSF is not available (due to intervention or other technical
reasons
preventing LGSF operations on a short term), and because the COSMOS field is visible
until mid-May only, the targets for NGS-AO mode should then be observed, and in
turn
(priority 2, then 3).
- It is more important for the science goals to carry out ALL OBs of a given source
before observing the next one.
The exception would be if LGS observations of the 1st priority target have been
started but the LGSF becomes unavailable (cf. previous point).
- OBs are named after the targets, with "-0", "-1", "-2", etc. appended for different
OBs.
- There is no priority among the OBs for a given source; therefore, the priority
is set to
the same value in the OBs of a given source.
If possible, we would prefer the OBs of each source to be carried out in the order
corresponding to the number "-0", "-1", "-2", etc. in the OB names.
- The DITs for our exposures of our faint targets are 600s.
OBs have between 6 and 8 science exposures each.
- The brightest spectral feature of the targets is H_alpha in emission;
the observed wavelength (confirmed through pre-imaging in no-AO mode) is given
in the
table above.
- We are using the 100mas scale, with FOV of 3.2"x3.2".
Two different strategies are followed, depending on the target.
(1) Three of the targets (ZC410123, ZC409985, ZC405226) are sufficiently compact
(sizes <~ 1.5" based on no-AO pre-imaging) to enable "on-source" dithering,
where
two successive exposures are offset mostly along E-W by about 1/2 the 3.2"x3.2"
FOV
(i.e., about 1.5") for pairwise sky subtraction. Small jitters about the two
main
dithering positions are used to minimize the number of redundant positions.
(2) The other target (ZC407376) is more extended in all directions. For proper
coverage
of the entire source and proper background subtraction, "sky" exposures away
from the
source are needed. The sequence is "O S O O S O" where each "O" on-source pointing
is offset by about 0.2" along RA and DEC in four positions around the target
(giving a "jitter box width" of about 0.4").
Remarks on the finding charts:
- Two finding charts are provided for each target and OB, following the instructions
for SINFONI.
(1) The first one (SINFONI_{configuration}_{source}_fchart1.jpg) has wider FOV;
the
large and small solid-line black squares show regions 1'x1' and 8"x8" centered
on the target; the AO reference star is labeled "R1". The larger dashed rectangle
shows the Strap Field Selector FOV of the AO system.
(2) The second one (SINFONI_{configuration}_{source}_fchart2.jpg) is zoomed in
on the
target, with the large and small solid-line squares showing regions of 8"x8"
and
3.2"x3.2" centered on the target. In addition, two dashed-line squares show
the
outline of the two main dithering positions (for the 3 targets with on-source
dithering) or of the jitter box (for the 4th target for which sky exposures
are
taken away from the source).
Waiver Requests
One Waiver Request was submitted:
081.A-0672B.01.WAV: for an increase of the OB execution time limit to 1h45.
(submitted on April 11, 2008; Approved on April 15, 2008)
In addition, one Instrument Setup Change Request was also submitted.
The request was to change from LGS-AO to NGS-AO for two of the targets:
COSMOS-409985 (09:59:14.18 +02:15:47.0)
COSMOS-405226 (10:02:19.52 +02:00:18.1)
(submitted on April 16, 2008; Approved on April 17, 2008)
Critical Observing Condition Constraints
Transparency constraints:
- For all OBs, CLEAR sky transparency conditions is acceptable, as specified
in the proposal.
Moon constraints:
- For all targets, conforming to our proposal, there is no constraint on lunar phase
and so the illumination is set to 1.0.
- For three targets, the AO star is rather faint (R > 16), however, so we have
set
the constraint for moon distance to 50 degrees
(following recommendations from the ESO SINFONI P2PP Web pages
(http://www.eso.org/observing/p2pp/SINFONI/SINFONI-P2PP.html#Requirements)
Seeing constraints:
- Seeing < 0.6", as specified in the proposal.
Time-Critical Aspects
Special Execution Requirements
As we explain in the General Description, the priority flag set in the
OBs
reflects the scientific priority of the targets.
OBs for a given source all have the same priority value, but we would prefer
if the OBs are carried out in the order indicated by the "-0", "-1", "-2", etc.
appended to the names of the OBs.
It is more important to complete all OBs of a given source before starting the
observations of the next one by priority.
The only exception to this is the following, as we emphasize in the General Description.
If the LGSF becomes unavailable for technical or other reasons, even if the LGS
observations
of the highest priority target have been started, then the two sources with NGS-AO
should be
observed (priority 2, then 3).
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 ?
Did you indicate the magnitude of the brightest object in the field in
each SINFONI OB?
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)?
If you submitted OBs for standard stars, did you use the provided StandardStar
templates?
If you are using a specific offset pattern or position angle: did you
check carefully the definition in the manual?
Did you make really sure that none of your OBs ever saturates the detector?
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?
Last creation of page: Tue Oct 6 15:40:25 2009
If you have comments, please contact usd-help@eso.org