A planned IT Maintenance and Release Window is scheduled between
Saturday, 15 February 2025 at 08:00 CET/04:00 CLST and Sunday, 16 February 2025 at 24:00 CET/20:00 CLST.
From 08:00 CET/04:00 CLST on Saturday, all ESO IT services including ERP, Email, Database Management Systems,
the Scientific Archive, the User Portal, and internet connectivity on all ESO sites, may experience intermittent outages
due to configuration changes in the computer rooms.
Full services cannot be guaranteed before Monday, 17 February 2025. We apologize for any inconvenience this may cause.
OB Execution Overheads
The time allocated to your program is total execution time, i.e., integration time + overheads. Therefore, the total execution time of the Observation Blocks (OBs) you submit should be less than or equal to the total time allocated, with the only possible exception of Target of Opportunity runs. The option of submitting OBs for an execution time exceeding the allocation and terminating the programme when the allocation time is exceeded is not currently supported in Service Mode.
To determine total execution time, please use the the Execution Time report function in the web-based p2.
To enable flexible scheduling in Service Mode the 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.