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 VISIR
In service-mode, VISIR is offered in the following two basic instrument modes:
|SPEC||long-slit and cross-dispersed spectroscopy|
Imaging is available with a 36" x 36" field of view for various broad and narrow band filters in the N- and Q-band. Coronagraphic imaging observations are only offered in visitor-mode. Long-slit spectroscopy is offered in low- and high-resolution for specific central wavelength settings in the N- and Q- bands. Cross-dispersed high-resolution spectroscopy is offered for specific central wavelength settings in the N- and Q-band.
Please refer to the VISIR instrument page which configurations, filters, scales, slits and central wavelengths are offered in detail.
Target Brightness in Servide-Mode OBs
To aid in the acquisition of targets, each service-mode OB should contain the expected target brightness in Jy or mJy in the User Comment field of the OB.
Allowed Filter Combinations in Service-Mode
For VISIR, imaging OBs executed in service-mode may have a maximum of five filters in a single OB without the need to submit a waiver request. However, it is not permitted to mix N- and Q-band filters within one OB. OBs that deviate from these general rules are accepted only if duly justified and authorized by means of a Phase 2 Waiver Request.
Concatenation Scheduling Container Execution Times
For VISIR, concatenations of science and user-provided calibration OBs may be up to 90 minutes in duration. However, both the science and calibrator OB must still have individual execution times of one hour or less. 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.
High-Resolution Spectroscopy OBs
The operating range in ADUs of the new Aquarius detectors is relatively small. Therefore, for high-resolution spectroscopy, the Detector Integration Time (DIT) needs to be optimized by the night-time astronomer for a given wavelength. It is therefore important that he wavelength(s) of scientific interest need to be clearly indicated in the README information, and by means of a plot of the Exposure Time Calculator (ETC) transmission spectrum, attached as an additional Finding Chart to the OB. If the wavelength(s) of interest are different from the central wavelength, this should be clearly indicated in this plot.