Service Mode Rules and Recommendations for Observation Blocks
Preparing Observation Blocks
Observations at all ESO telescopes are carried out by executing Observation Blocks (OBs) provided by the users. OBs for Service Mode runs at UT2 (i.e. using FLAMES, UVES and/or XSHOOTER), VISTA (i.e. VIRCAM) and VST (i.e. OMEGACAM) must be made with p2. OBs for all other Service Mode runs with Paranal Instruments must use P2PP version 3 (P2PP3). For (designated) Visitor Mode observation preparation, please follow dedicated Visitor Mode Guidelines.
Please refer to the P2PP3 User Manual and to the User Manuals of the different instruments for more specific information on the structure and content of OBs, and how to build OBs for different instruments. A number of tutorials describing step-by-step the construction of OBs for different instruments is available.
Service Mode OBs: rules and advices
It is important to keep in mind the Service Mode policies and the following rules and guidelines when designing a Service Mode programme or when preparing a Phase 2 package:
- Some observing strategies cannot be supported in Service Mode; in particular, real-time decisions about the sequencing of OBs, complex OB sequencing, or decisions based on the outcome of previously executed OBs (like adjustment of integration times or execution of some OBs instead of others).
- OBs are only executed once. If you want to repeat an identical observation multiple times, you must submit multiple OBs. This requirement applies to standard stars as well.
- OBs are normally executed non-contiguously. Since efficient Service Mode operations require continuous flexibility to best match the OB constraints with actual observing conditions, OBs for a given programme may be scheduled non-contiguously. Therefore, users should not expect their OBs to be executed in a specific sequence or in a linked way, unless a sound scientific justification (indicated in the README file and approved with a Phase 2 Waiver in case of a contiguous execution lasting longer than 1 hr) exists. Approved OB sequences should then be prepared as concatenations. Exceptions to this rule are cases in which one OB observing a calibration source needs to be executed contiguously to a science OB. In such a case place both OBs into a concatenation scheduling container to enforce their contiguous execution.
- Multi-mode, multi-configuration OBs are normally not permitted in Service Mode. Although multiple configurations within one OB may sometimes reduce overheads, scheduling and calibrating such OBs is extremely inefficient and can increase the calibration load to an unsustainable level. Examples of such multi-configuration OBs are those combining imaging and spectroscopy in a single OB, spectroscopy with multiple grisms or multiple central wavelength settings, or imaging with a large number of filters (although most imagers allow multiple broadband filters in one OB). Multi-configuration OBs are accepted only if duly justified and authorized by means of a Phase 2 Waiver Request.
- OB execution times must be below 1 hour. Long OBs are more difficult to schedule and execute within the specified constraints because of the unpredictable evolution of the observing conditions. For this reason, OBs taking more than one hour to execute are accepted by ESO only in exceptional cases and provided that a Phase 2 Waiver Request is submitted and approved. In such cases, ESO will consider the OB successfully executed if the constraints were fulfilled during the first hour of execution, even if conditions degrade after that time.
- Concatenation scheduling container execution time must be below 1 hour and exceptionally for CRIRES instrument science+telluric standard concatenation must be below 1.5h. Only in exceptional cases, and provided that a Phase 2 Waiver Request is submitted and approved, longer concatenations may be submitted. In such cases, ESO will consider the concatenated OBs successfully executed if the constraints were fulfilled during the first hour of execution, even if conditions degrade after that time.
- User-provided calibration OBs that need to be executed contiguously with science OBs need to be specified via concatenation scheduling containers.
- Time constraints must be indicated in the OBs. If you intend to observe time-critical events or monitor a target at specific time windows, you need to indicate this under the Time Intervals tab of the OBs. Please note that absolute (UT) time constraints refer to the interval in which the OB can be started, whereas for Local Sidereal Time (LST) time intervals, the time interval refers to the entire duration of the OB. For monitoring observations it is often more appropriate to put OBs in a time-link container. Specifying time windows as broad as possible will reduce the possibilities that your OBs are not executed because of higher priority programmes or because the observing conditions did not allow the observations during the interval that you specified. Usage of absolute time intervals must be scientifically justified in the README file. Please read carefully the time-critial OB execution policy.
- Specify the weakest possible Constraint Set values. OBs that can be executed under a broad range of conditions are easier to schedule. In particular, if photometry is needed of a field, it is normally sufficient to obtain a short integration under photometric conditions (transparency = PHO) and carry out the rest of the integration with OBs having a transparency = CLR constraint.
Additional Service Mode Requirements for NACO
The window size is now selectable with the following choices: 1024 (full frame), 768, 512, 384, 256, 128, and 64. The window will be square, and centered on pixel (512,512). Choosing small windows allows shorter DITs but increases the noise. For small windows some 8-pixel noise pattern appears in the frames.
The maximum file size for a cube is 512 MB. This, in turn, constrains the maximum value for NDIT according to the following Table (but consult the User Manual for important notes!):
|Detector Setup||Window size||Min DIT||Max NDIT||Frame Loss||Time Loss|
The minimum time between exposures should be 20 seconds. Depending on which template is used, the integration time parameters (DIT, NDIT) should be defined so as to ensure that this rule is strictly followed. The reason for this limitation is to allow the Active Optics to settle and correct the M1 at least once. In the course of a template, if Active Optics corrections are not sent to the mirror, aberrations will start piling up, significantly affecting the achievable image quality.
Direct imaging of very bright objects results in residual images lasting for several minutes. In Service Mode, this problem can affect subsequent observations of other programs.
Observations involving fields with objects brighter than those specifed in the table below cannot be guaranteed.
Requests for observations not compliant with these limits must be submitted as a Phase 2 Waiver Request.
|SW broad band imaging||6|
|SW narrow band imaging||4|
|LW broad band imaging||5|
|LW narrow band imaging||3|
Brightness limits: Acquisition
For acquisition of bright targets, the following filter settings must be used. Note that this applies not only to standard stars, but also to other bright objects in the field of view.
|IR Magnitude||Filters to use|
|>4 and <6||Any Narrow Band filter|
|>2 and <4||Any filter together with a neutral density filter (ND_short for SW filters and ND_Long for LW filters)|
|0 - 2||Any Narrow Band filter together with a neutral density filter (ND_short for SW filters and ND_Long for LW filters)|
Important note: in case of spectroscopic observation when the bright object in the field of view is not the science target, the target may become too faint to centre on slit due to the use of the Narrow Band filter(s). In this case offsets from a reference star should be used.
There are a three basic rules that must be abided by for such cases:
- For targets that are to be tracked through the meridian the name of the OB must be suffixed with "_meridian".
- For targets that are to be tracked through the meridian the OB must contain an LST time interval. This makes it straightforward to schedule at the telescope.
- For any OB that has an LST time interval specified the length of that interval must exceed the total execution time for the OB itself, but by no more than 10 minutes.
There are two basic rules that must be followed for the case where you are using PSF calibration OBs, to facilitate their correct scheduling at the telescope:
- The science OB and its corresponding PSF OB must be placed together into a concatenation.
- The PSF OB must be listed second in the concatenation (that is, it must appear below the science OB).
The "Atmospheric Turbulence Model." Constraint Set parameter is used at the telescope to assist in the scheduling of OBs. The default value for this parameter is "no constraint," which implies that no consideration for the atmospheric turbulence is to be considered when scheduling such an OB. The other value for this parameter, "default Paranal atmosphere model," implies that the atmospheric turbulence is to be considered in the scheduling of the associated OB. Hence, users who are preparing OBs for "No AO" mode must use "no constraint" while users preparing OBs that make use of adaptive optics must select "default Paranal atmosphere model."
The PS produces an ASCII file with the extension aofcg which is required by P2PP and is used to set up NAOS. This file should never be manually edited. If you do, the execution of your OB will be severely compromised and your name will go on a yellow piece of paper on a big white board.