IMPORTANT NOTICE (11 July 2025 11:00CEST): we are currently experiencing a major issue with our p2 software that prevents the creation of new Observation Blocks, so that Phase 2 submissions cannot be made at this stage. We are actively investigating this issue and hope to restore p2 to its normal state as soon as possible. We sincerely apologize for the inconvenience.
UPDATE (11 July 2025 13:00CEST): the bug has been corrected. Please refresh the p2 page in your browser and make sure that you are using version 2.22.6 (or above) of the interface as indicated in the top-left corner of the page.
OB run-time failure policy
Although ESO carefully reviews Service Mode Observation Blocks (OBs) before they are scheduled at the telescope, it is impossible to detect every OB problem until it is actually executed.
If an OB fails to execute due to an error introduced by the user (as for example if the user entered wrong target coordinates), ESO reserves the right to charge the respective observing programme for the time lost during night operations. Time charged will include any telescope time used to investigate why OB execution failed.
For Service Mode observations time lost due to failures caused by ESO (e.g. instrument malfunction) will not be charged to the user. Whenever possible, these OBs will be re-executed as time, conditions, and overall priority permit.