The Vera Rubin Observatory control system is a highly distributed system composed of a myriad of independent components that must act together to perform high-level operations. By high-level operations we mean actions such as commanding the telescope to slew to to a position in the sky, wait for the telescope, dome and all the other components to be ready and then perform observations.
Commanding and monitoring the state and other particular events from each individual component can be valuable when it comes to performing regular observations, commissioning and/or engineering activities but can be extremely taxing for users. This collection of high-level control software is designed to help mitigate the issue. The software is organized into a set of classes that bundle together functionality from a group of components, essentially grouping the coordinated action of many CSCs into single high-level operations. Users can utilize these classes separately to control a set of components or combine them to achieve even higher levels of operations.
User-level documentation, found at the link below, is aimed at observers and operators looking to perform interactive operations with any of the telescopes and/or their components. In most cases, users use the observatory control package from a Jupyter notebook to execute tasks in a controlled and highly interactive environment.
Information about how to connect to the Jupyter notebook server is available in the observatory control system nublado interface documentation.
Most of the tasks available in this package are encapsulated by a SAL Script that can be launched in the ScriptQueue, which provides a less-interactive and more user friendly interface. Information about operating the system using the ScriptQueue can be found in the observatory control system user interfaces documentation.
This area of documentation focuses on the classes used, API’s, and how to participate to the development of the [CSC] software packages.