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 with Paranal Instruments must be made with p2. For (designated) Visitor Mode observation preparation, please follow dedicated Visitor Mode Guidelines.
Please refer to the Phase 2 step-by-step preparation with p2 page 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 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. 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 (most relaxed) possible Constraint Set values. OBs that can be executed under a broad range of conditions are easier to schedule. In particular, for photometric calibration 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.
Some OBs must be executed within precise time windows for scientific reasons, rather than any time when the external conditions (moon, seeing, transparency...) would allow the execution. The following types of time-dependencies can be recognized:
- Absolute time constraints, meaning that an OB must be executed at specific dates that can be predetermined. An example is the observation of a binary star at a precise phase of its period or a planetary transit observation.
- Relative time links, implying that an OB must be executed within a time interval after the execution of a previous OB, but not necessarily at a fixed date. Examples of this are monitoring observations of a variable source at some pre-defined intervals.
Both types of time-dependency are implemented within p2. Whereas absolute time constraints are available at the level of single OBs, the relative time links are implemented within the new "Time Link" container.
Within a Time Link container, the user can define a series of OBs, having the earliest and latest time when a given OB in the series must be executed with respect to the preceding OB. The time-related information is stored in a database, from where it is retrieved by scheduling tools available to the operator on the mountain in order to build up a short-term schedule that properly takes these constraints into account.
If an OB with absolute time constraint or time-linked OB that acquired an absolute time constraint following execution of a previous OB in sequence (i.e. OB to be observed after earliest from and before latest from time of the previous OB in the sequence) is not successfully completed within the specified time interval, it will expire and get status F(ailed). Such an OB is not observable any more and policy for time-critical OB execution applies.
If the time-linked OB expired in the middle of a time-link sequence, the sequence execution continues as follows:
- If the failed OB is not the very first OB of the time link, it had the absolute time window corresponding to delay from the previously executed OB. After it expired the next OB acquires an absolute time window by adding the relative minimum and maximum time delays to an assumed hypothetical execution for the failed OB in the middle of its constraint window.
- If the failed OB is the very first OB of the time link, the failure can only occur if this OB has one or more absolute time constraints defined and all of them have expired. In this case the next OB acquires an absolute time window by adding its relative minimum and maximum time delays to an assumed hypothetical execution of the failed OB at the end of its last absolute time interval.
It should be noticed that, depending on the length of the relative time intervals, and the delays between them, a failure of an OB in a sequence may result in a cascade of failing OBs.
In some cases it may be desired to execute the OBs consecutively, with no other observations in between. This has been implemented in p2 within the "Concatenation" container. The Concatenation container consists of two or more OBs that must be executed "back-to-back" without breaks. The sequence of the execution of OBs in a Concatenation typically follows the sequence as they are listed in the p2 window.
Groups of OBs are used to express the preference to complete observations of a given group of OBs before continuing with other OBs (or groups of OBs) within the same observing run. This is the most loose scheduling container concept, and the priority for execution of the group with respect to other groups within the same run is defined though group priority that has values 1-10 (1 top, 10 lowest priority) as for the user priority for loose OBs. The priority for execution of OBs within the given group is regulated through the OB group contribution.
If OBs within the group, whose observation started, are not observable (constraints are not fulfilled), it is possible to start observations of another group. After that group score defines which groupo will be given priority in case both groups of OBs are observable again.
Additional Service Mode Requirements for MUSE P109
Note: For seeing ~1", the SGS works with stars as faint as R~21.5
General: recommended position angles and offsets
To improve the flat-fielding of the slicer and channel patterns during the data reduction we strongly advise the observer to split the on-target observation in multiple exposures taken at least at two different position angles (separated by 90 degrees) and with a small offsets pattern. The size of each offset should at least be larger than a spaxel (i.e. >0.2" for the WFM, and >25mas for the NFM).
Offsets and position angles are always cumulative.
For accurate target centring users should use the MoveToPixel acquisition template, which allows to select a reference bright source from which a blind-offset is then applied. However, should the user decide to not select the reference star (i.e. no blind-offset is used) with the MoveToPixel acquisition template, then point-like sources within the FoV should be clearly marked in the attached finding chart such as to be used for accurate target centring at the telescope.
WFM-AO observations can be performed with or without the use of a visible natural Tip-Tilt Star (TTS) to correct for the atmospheric tip-tilt. The TTS-free mode uses only the 4LGS, which by design always follow the target, therefore this mode provides 100% sky coverage.
The TTS has to be located between 52" and 107" off axis and must be brighter than R=17.5 mag. However, for OBs requesting IQ<0.6" the TTS can be as faint as R=18.5 mag.
For a given OB, the user can provide up to two TTS such as, should the first TTS not be suitable, the second TTS can be used. When providing two TTS, users should remember to select as TTS1 the brightest among the two.
WFM-AO observations of moving targets or high proper motion target sare offered only if no TTS is selected (i.e. only in TTS-free mode). In this case, the Slow Guiding System must be switched off.
NFM observations can be only performed if a point-like Natural Guide Stars (NGS) is available within a radius of 5.0" from the center of the MUSE FoV (NFM FoV=7.5"x7.5"). The suitable magnitude ranges for a point-like, non-extended NGS depend on the on the distance of the NGS to the target, the required airmass (AM) and turbulence category (TC) constraints. The following rules apply:
- The bright NGS magnitude limit is J>5.5 (Vega)
- For a target-NGS separation <3":
- The NGS faint limit is J<19 if TC=10% and AM<=1.2
- The NGS faint limit is J<18.5 if TC>10% or AM>1.2.
- For a target-NGS separation is >=3":
- The NGS faint limit is J<18 if TC=10% and AM<=1.2
- The NGS faint limit is J<17.5 if TC>10% or AM>1.2.
Extended objects can be also used as NGS providing their magnitude within an aperture radius of 1.5" is in the range 5.5<J<17. Moreover, their distance from the field center should not be larger than 3.35".
Observations of moving targets are possible only with on-axis NGS (i.e. the target is used as NGS).
As for the case of the WFM (AO and NOAO), we suggest to break the total exposure time on source in sub-exposures, and applying a small dithering pattern and 90 degrees rotation between on-object exposures. Indeed, the combination of small dithering pattern and 90 degrees rotations is currently the best strategy to reject comics, and obtain a more uniform combined dataset in terms of noise properties. However, the following should be taken into account:
- The maximum size of the offset between two consecutive on-object exposures should not be larger than 1” (i.e., 40 pixels).
- When the observation sequence of an NFM template starts with the NGS on-axis (i.e., target is the NGS), then rotations to different position angles can be done only when the offset sequence brings the NGS (and Field Selector) to within 0.2" (8 pixel) from the starting position before the rotation is applied. Note, however, that rotations are expensive in overheads as they are done slowly and with the loop closed in steps of 10 degrees. Two possible use cases are those:
- If all offsets keep the pointing within 0.2” from the original (on-axis) pointing, then arbitrary combinations of offsets and rotations can be applied.
- If offsets bring the pointing beyond 0.2” from the initial (on-axis) centered position, rotations cannot be done at those positions. Rotations can only be applied if the sequence brings the pointing back to within 0.2” from the initial centered (on-axis) position.
- In case the NGS is located at an off-axis position, no rotation can be applied during the observing sequence of such an OB. If rotated cubes are needed, it is recommended to split the observations into different OBs, with each one starting at a different position angle.