ESO Spanish Users : Observing Modes P89

Table of Contents Visitor mode Service mode Service mode policies In Period 89, most VLT and VLTI instruments will be offered in two modes: Visitor

Table of Contents Visitor mode Service mode Service mode policies In Period 89, most VLT and VLTI instruments will be offered in two modes: Visitor Mode (VM) and Service Mode (SM). These modes have been extensively described in the Data Flow Operations section of theDecember 1997andJune 1998issues of The ESO Messenger (see also an article on Service Mode scheduling in theSeptember 2001issue). As part of the Phase 1 proposal, investigators will have to specify which mode they desire and why they request that mode. While it will be attempted as much as possible to follow the desire of the proposers with respect to observing mode, ESO does reserve the right to allocate time in a mode different from the one requested. The telescope, as well as the instruments, will be operated by observatory staff only. The astronomer interfaces with the telescope/instruments via Observation Blocks (OBs), produced using the Phase 2 Proposal Preparation (P2PP) tool. Visitor Mode InVisitor Mode(VM) the astronomer is physically present at the observatory during the observations. Each approved VM run will be allocated specific calendar nights. One of the programme investigators will travel to the Observatory and execute the observations. Visitor Mode is not offered on VST, VISTA or APEX. For all ESO instruments data acquisition will be done by executing Observation Blocks (OBs), i.e. observing sequences specified by the astronomer which are based on templates provided by ESO. VM investigators will be encouraged to construct their OBs before arriving on the site. However, P2PP allows OBs to be constructed and/or modified in real-time at the telescope (with only the partial exception of VIMOS). VM investigators will be required to arrive on Paranal before the start of their observing run as follows: 24 hours for UVES, and 48 hours for all other instruments. On La Silla, Visiting Astronomers shall arrive 1 to 2 days before the start of the observations, and may leave the site up to 1 to 2 days after the end of their observing run according to the transportation schedule (seethe La Silla Science Operations page).Note that programmes must be executedas specified and approved at Phase 1. The proposer should prepare a backup/alternative programmeto be executed in place of the primary programme if the observing conditions are not ideal.The original science case and goals should be followed.Such backup programmes must be approved by ESO prior to the observing run. The corresponding requests must be submitted via the web-based form available at target change web page of ESO. If the conditions prevent the Visiting Astronomer's primary programme to be executed the telescope will be used for the execution of Service Mode observations; assuming no backup programme is in place and that Service Mode observations are allowed on that telescope. The QCDP group creates data packages for VM runs on Paranal and makes them available to the PI via the ESO User Portal. These packages contain all raw data (science and calibrations) and processed data unless no pipeline support is available. Raw data are available for download shortly after acquisition, product data typically within a few working days. Please note thatVM proposers must include overheadsfor all science exposures. ToO programme execution during VM observations VM observations may be interrupted by time-critical DDT or ToO programmes. As far as possible,the execution of observations for such programmes will be confined to scheduled Service Modeperiods. Under exception circumstances, the Director of the Observatory may decide to interruptVM runs to allow Service Mode observations. ToO runs in the Rapid Response Mode (RRM) mayalso interrupt VM observations. Service Mode Up to approximately 60% of the total time available for observations on Paranal will be carried out in Service Mode (SM). SM is also the only mode supported for APEX, VST and VISTA. It is not offered on any La Silla telescope. Investigators with runs allocated in SM time will be required to specify their programme by submitting to ESO a Phase 2 package in advance. This package consists of OBs, finding charts, and a Readme form. Observers intending to submit proposals to be executed in SM may find it useful to familiarize themselves with the Phase 2 Service Modeprocedures. Once the OBs are completed, they will be submitted to ESO for verification and acceptance. Accepted OBs will be executed by ESO staff based on their OPC recommended priority and a proper match between the requested and the actual observing conditions. An article about SM scheduling appeared inThe ESO Messenger (2001, v. 105, p. 18). The article helps proposers understand how they may optimize their use of this observing mode, and it should be considered compulsory reading for SM proposers.SM PIs and their delegates have direct access (via theirpersonal ESO User Portal account) to their own raw proprietary data as soon as the data is ingestedin the ESO Archive. Pipeline reduced data (except for modes without pipeline support) becomeavailable to PIs and/or their delegates shortly afterwards. Similar to VM runs, data packages arecreated by the QCDP group for all SM runs, and include the same types of data. SM data packagesare also sent out on media, after the termination of the whole run. Note that in Service Mode theproprietary period for a given science file starts as soon as the data are made electronically availableto PIs and their delegated observers. Please note thatSM proposers must include overheadsfor all science exposures. ESO will absorb all the time required to complete the calibration sequences to the level of accuracy foreseen in the calibration plan, as well as overheads associated with such calibrations. If those calibrations are not adequate, the SM proposer must include time for any additional calibrations including overheads. Proposers are especially encouraged to request Service Mode (on Paranal) if their programme involves Target of Opportunity events or synoptic observing, or if they require the best observing conditions (which occur at unpredictable intervals). Further information on SM observing may be found in theService Mode Guidelines. Service Mode policies To ensure the eficiency of SM observing, ESO has implemented a number of rules, procedures and limitations on Service Mode runs. They need to be carefully taken into account at the time of preparing an application for SM observations and are summarized here. Please note that most of these items have important consequences on the way that execution overheads must be taken into account. 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). Observation Blocks (OBs) are executed non-contiguously. Since efficient SM operations require continuous exibility to best match the OB constraints with actual observing conditions, OBs for a given run are normally scheduled non-contiguously. It is thus not possible to reduce acquisition overheads by requiring the sequential execution of OBs with the same target field. Multi-mode, multi-configuration OBs are normally not permitted in SM. Although multiple configurations within one OB may sometimes reduce overheads, scheduling and calibrating such OBs is extremely inefficient. Different configurations should thus be in different OBs. OB Total Execution Time. Proposers should make sure that all overheads, including telescope presetting and acquisition overheads have been properly included. OB execution times must be below 1 hour. Long OBs are more diffcult to schedule and execute within the specifed constraints because of the unpredictable evolution of the observing conditions. OBs taking more than one hour to execute are not normally accepted (with the exception of AMBER). Proposers are especially encouraged to plan for OBs substantially shorter than one hour if the execution conditions are particularly demanding, as the fulfilment of all the constraints during the entire execution time becomes more unlikely as the OB becomes longer. Phase 1 constraints arebinding. As constraints play an essential role in determining the long-term scheduling of SM time, a relaxation of observing constraints is permissible at Phase 2 but ESO will not allow any tightening of constraints. Changes with respect to the times on target specified at Phase 1 will not be allowed at Phase 2. Fulfilment of Phase 2 constraints:ESO will consider an OB as successfully executed if all the conditions in the constraint set are fulfilled. OBs executed under conditions marginally outside constraints by no more than 10% of the specified value will not be scheduled for re-execution. Adaptive Optics-assisted observations within 50% of the requested Strehl ratio will not be repeated (assuming that other constraints are suitably met). VLTI OBs executed marginally outside the specified LST intervals by no more than 30 min will not be scheduled for re-execution. Programmes with linked time requirements:SM is also intended to support programmes with special timing requirements. However, proposers planning such programmes should keep in mind that at most 60% of both bright and dark time is allocated to SM (on Paranal), and that observing conditions cannot be predicted when a time-series is started. This means that timing sequences that are extremely long and/or complex, timing links that are very restrictive, and time-series for observations requiring excellent observing conditions, are unlikely to be successfully completed. Therefore, all such proposals are reviewed for technical feasibility and may be rejected if judged to be too complex. Proposers for programmes requiring timing links are strongly encouraged to consider how they may simplify their timing sequences as much as possible, as this will minimize the risk that the observations are deemed unfeasible. If a given OB cannot be executed within its intended observability window, ESO will try to execute it as soon as possible thereafter on a best-effort basis, taking into account the user-specified constraints and the constraints imposed by other scheduled runs. ESO will not restart a sequence of linked observations if the pre-specified timing constraints cannot be fulfilled. VLTI:A separate run must be specified for each requested baseline configuration. ToO programme execution: Successful proposers of ToO runs will have to prepare OBs fortheir observations well ahead of the beginning of an observing period. MostlyToO OBs will have to be “dummy” OBs with default values for target coordinates, integrationtimes etc. At the time of occurrence of the predicted event, the PI of the programme mustactivate it and at the same time provide the missing information for completion of the OBs.The service observer will update and execute the specified OBs. Further details are availableon the Phase 2 ToO Procedures page. Information partially extracted from the pdf document:ESO Call for Proposals –P89

Observing Modes P89

Table of Contents

 

In Period 89, most VLT and VLTI instruments will be offered in two modes: Visitor Mode (VM) and Service Mode (SM). These modes have been extensively described in the Data Flow Operations section of the December 1997 and June 1998 issues of The ESO Messenger (see also an article on Service Mode scheduling in the September 2001 issue). As part of the Phase 1 proposal, investigators will have to specify which mode they desire and why they request that mode. While it will be attempted as much as possible to follow the desire of the proposers with respect to observing mode, ESO does reserve the right to allocate time in a mode different from the one requested.

The telescope, as well as the instruments, will be operated by observatory staff only. The astronomer interfaces with the telescope/instruments via Observation Blocks (OBs), produced using the Phase 2 Proposal Preparation (P2PP) tool.

Visitor Mode

In Visitor Mode (VM) the astronomer is physically present at the observatory during the observations. Each approved VM run will be allocated specific calendar nights. One of the programme investigators will travel to the Observatory and execute the observations. Visitor Mode is not offered on VST, VISTA or APEX.

For all ESO instruments data acquisition will be done by executing Observation Blocks (OBs), i.e. observing sequences specified by the astronomer which are based on templates provided by ESO. VM investigators will be encouraged to construct their OBs before arriving on the site. However, P2PP allows OBs to be constructed and/or modified in real-time at the telescope (with only the partial exception of VIMOS). VM investigators will be required to arrive on Paranal before the start of their observing run as follows: 24 hours for UVES, and 48 hours for all other instruments. On La Silla, Visiting Astronomers shall arrive 1 to 2 days before the start of the observations, and may leave the site up to 1 to 2 days after the end of their observing run according to the transportation schedule (see the La Silla Science Operations page).  Note that programmes must be executed as specified and approved at Phase 1. The proposer should prepare a backup/alternative programme to be executed in place of the primary programme if the observing conditions are not ideal. The original science case and goals should be followed.Such backup programmes must be approved by ESO prior to the observing run. The corresponding requests must be submitted via the web-based form available at target change web page of ESO. If the conditions prevent the Visiting Astronomer's primary programme to be executed the telescope will be used for the execution of Service Mode observations; assuming no backup programme is in place and that Service Mode observations are allowed on that telescope.

The QCDP group creates data packages for VM runs on Paranal and makes them available to the PI via the ESO User Portal. These packages contain all raw data (science and calibrations) and processed data unless no pipeline support is available. Raw data are available for download shortly after acquisition, product data typically within a few working days.

Please note that VM proposers must include overheads for all science exposures.

ToO programme execution during VM observations

VM observations may be interrupted by time-critical DDT or ToO programmes. As far as possible, the execution of observations for such programmes will be confined to scheduled Service Mode periods. Under exception circumstances, the Director of the Observatory may decide to interrupt VM runs to allow Service Mode observations. ToO runs in the Rapid Response Mode (RRM) may also interrupt VM observations.
 

Service Mode

Up to approximately 60% of the total time available for observations on Paranal will be carried out in Service Mode (SM). SM is also the only mode supported for APEX, VST and VISTA. It is not offered on any La Silla telescope.

Investigators with runs allocated in SM time will be required to specify their programme by submitting to ESO a Phase 2 package in advance. This package consists of OBs, finding charts, and a Readme form. Observers intending to submit proposals to be executed in SM may find it useful to familiarize themselves with the Phase 2 Service Mode procedures. Once the OBs are completed, they will be submitted to ESO for verification and acceptance.

Accepted OBs will be executed by ESO staff based on their OPC recommended priority and a proper match between the requested and the actual observing conditions. An article about SM scheduling appeared in The ESO Messenger (2001, v. 105, p. 18). The article helps proposers understand how they may optimize their use of this observing mode, and it should be considered compulsory reading for SM proposers. SM PIs and their delegates have direct access (via their personal ESO User Portal account) to their own raw proprietary data as soon as the data is ingested in the ESO Archive. Pipeline reduced data (except for modes without pipeline support) become available to PIs and/or their delegates shortly afterwards. Similar to VM runs, data packages are created by the QCDP group for all SM runs, and include the same types of data. SM data packages are also sent out on media, after the termination of the whole run. Note that in Service Mode the proprietary period for a given science file starts as soon as the data are made electronically available to PIs and their delegated observers.

Please note that SM proposers must include overheads for all science exposures.

ESO will absorb all the time required to complete the calibration sequences to the level of accuracy foreseen in the calibration plan, as well as overheads associated with such calibrations. If those calibrations are not adequate, the SM proposer must include time for any additional calibrations including overheads.

Proposers are especially encouraged to request Service Mode (on Paranal) if their programme involves Target of Opportunity events or synoptic observing, or if they require the best observing conditions (which occur at unpredictable intervals). Further information on SM observing may be found in the Service Mode Guidelines.

Service Mode policies

To ensure the eficiency of SM observing, ESO has implemented a number of rules, procedures and limitations on Service Mode runs. They need to be carefully taken into account at the time of preparing an application for SM observations and are summarized here. Please note that most of these items have important consequences on the way that execution overheads must be taken into account.

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).

Observation Blocks (OBs) are executed non-contiguously. Since efficient SM operations require continuous exibility to best match the OB constraints with actual observing conditions, OBs for a given run are normally scheduled non-contiguously. It is thus not possible to reduce acquisition overheads by requiring the sequential execution of OBs with the same target field.

Multi-mode, multi-configuration OBs are normally not permitted in SM. Although multiple configurations within one OB may sometimes reduce overheads, scheduling and calibrating such OBs is extremely inefficient. Different configurations should thus be in different OBs.

OB Total Execution Time. Proposers should make sure that all overheads, including telescope presetting and acquisition overheads have been properly included.

OB execution times must be below 1 hour. Long OBs are more diffcult to schedule and execute within the specifed constraints because of the unpredictable evolution of the observing conditions. OBs taking more than one hour to execute are not normally accepted (with the exception of AMBER). Proposers are especially encouraged to plan for OBs substantially shorter than one hour if the execution conditions are particularly demanding, as the fulfilment of all the constraints during the entire execution time becomes more unlikely as the OB becomes longer.

Phase 1 constraints are binding. As constraints play an essential role in determining the long-term scheduling of SM time, a relaxation of observing constraints is permissible at Phase 2 but ESO will not allow any tightening of constraints. Changes with respect to the times on target specified at Phase 1 will not be allowed at Phase 2.

Fulfilment of Phase 2 constraints: ESO will consider an OB as successfully executed if all the conditions in the constraint set are fulfilled. OBs executed under conditions marginally outside constraints by no more than 10% of the specified value will not be scheduled for re-execution. Adaptive Optics-assisted observations within 50% of the requested Strehl ratio will not be repeated (assuming that other constraints are suitably met). VLTI OBs executed marginally outside the specified LST intervals by no more than 30 min will not be scheduled for re-execution.

Programmes with linked time requirements: SM is also intended to support programmes with special timing requirements. However, proposers planning such programmes should keep in mind that at most 60% of both bright and dark time is allocated to SM (on Paranal), and that observing conditions cannot be predicted when a time-series is started. This means that timing sequences that are extremely long and/or complex, timing links that are very restrictive, and time-series for observations requiring excellent observing conditions, are unlikely to be successfully completed. Therefore, all such proposals are reviewed for technical feasibility and may be rejected if judged to be too complex. Proposers for programmes requiring timing links are strongly encouraged to consider how they may simplify their timing sequences as much as possible, as this will minimize the risk that the observations are deemed unfeasible. If a given OB cannot be executed within its intended observability window, ESO will try to execute it as soon as possible thereafter on a best-effort basis, taking into account the user-specified constraints and the constraints imposed by other scheduled runs. ESO will not restart a sequence of linked observations if the pre-specified timing constraints cannot be fulfilled.

VLTI: A separate run must be specified for each requested baseline configuration.

ToO programme execution: Successful proposers of ToO runs will have to prepare OBs for their observations well ahead of the beginning of an observing period. Mostly ToO OBs will have to be “dummy” OBs with default values for target coordinates, integration times etc. At the time of occurrence of the predicted event, the PI of the programme must activate it and at the same time provide the missing information for completion of the OBs. The service observer will update and execute the specified OBs. Further details are available on the Phase 2 ToO Procedures page.

Information partially extracted from the pdf document:  ESO Call  for Proposals – P89