Phase 2 Waiver Requests and Programme Change Requests
To ensure the observing efficiency and flexibility of Service Mode observing, ESO has implemented a number of rules, procedures and limitations on programmes scheduled for Service mode. Typically, these have to do with OB construction, observing strategy, or instrument modes available.
In some special cases it is possible to admit some justified exceptions to these rules with a reduced operational impact. However, it is necessary that the exceptions have been reviewed and authorized by ESO well in advance. The Phase 2 Waiver Request procedure is the channel to make this possible.
A waiver request, including a justification for the exception, is submitted by selecting the Waiver option in the Change Request tab in p2. Please note that justifications based on the reduction of execution overheads may not be accepted, as sequences of OBs or very long OBs decrease the flexibility of Service Mode observing and thus the operational efficiency. The request should be submitted at least 1 week before the Phase 2 deadline to allow for evaluation by the support astronomer including input from Paranal operations staff. In the following are listed general and instrument specific Phase 2 Waiver conditions.
Instrument independent conditions where a Phase 2 Waiver Request is needed
- OBs that will take longer than one hour to execute.
- Concatenated OBs that will take longer than one hour to execute.
- Concatenated OBs that have large angular separations between the OB targets (>75 deg) which would result in a very difficult scheduling.
- OBs that contain multiple instrument configurations. As an exception, multiple broad-band filters in a single OB can normally be allowed without a waiver, and for FORS2 up to two interference filters may be used in a single OB without a waiver.
- Delayed submission of Phase 2 material needed. This is admissible only under exceptional circumstances justified by scientific reasons, such as the need to wait for the outcome of another observing run before preparing the OBs. Users whose schedule prevents them from submitting their Phase 2 package by the due date are strongly encouraged to find a collaborator who can do it, rather than submitting a waiver request, as ESO cannot guarantee the prompt review and validation of Phase 2 packages submitted after the Phase 2 deadline.
- The time interval between succeeding time-linked OBs is < 1hr.
Additional conditions for Waiver Requests regarding VIRCAM
In addition to the general Phase 2 Waiver Request policies, waiver requests have to be submitted for the following conditions:
- OB requires an image quality better than 1.0" and AO PRIORITY is not set to "HIGH" in that OB, or in the first OB of the concatenation.
- the run is not a TOO run and the user wants to use the observing template VIRCAM_img_obs_paw
- OB submitted using VIRCAM_img_obs_tileX (where X=1, 3, or 6) template does not have AG stars defined using SADT for the first pawprint.
- ToO OB using VIRCAM_img_acq_quick template with values for the following parameters different than in the table:
Waiver Requests are petitions to override one or more operational rules or technical limitations. Programme Change Requests are petitions to deviate from observations as proposed at Phase 1 (e.g. new targets, new instrument, new/different observing modes, etc.). Formulation and submission of both types of petition is now fully supported in the p2 (Paranal) and p2ls (La Silla) user interfaces. Once logged in, the user should select the Run for which they intend to submit the Waiver Request or Change Request. By clicking on the Run, the user will be able to access the Change Request menu on the top right. Further information is provided here.
Note that all Phase 2 Waiver Requests and Programme Change Requests must be approved by ESO before Phase 2 package submission. Users should understand that such requests can take a number of days to process, especially when consultation with the Chilean Science Operations team is needed. Until they are processed no further progress can be made in processing of the run. Hence users are strongly encouraged to plan ahead and submit such requests in a timely fashion.
All approved requests (either waivers or programme change) should be summarized in your README file.