Search

The SKA Observatory, currently in the construction phase, will have two of the world's largest radio telescopes when completed in 2028. The scale of the project introduces unique challenges for the telescope software design and implementation at all levels, from user interfacing software down to the lower-level control of individual telescope elements. The Observation Execution Tool (OET) is part of the Observation Science Operations (OSO) suite of applications and is responsible for orchestrating the highest level of telescope control through the execution of telescope control scripts. One of the main challenges for the OET is creating a design that can robustly run concurrent observations on multiple subarrays while remaining responsive to the user. The Scaled Agile Framework (SAFe) development process followed by the SKA project also means the software should be allow to iterative implementation and easily accommodate new and changing requirements. This paper concentrates on the design decisions and challenges in the development of the OET, how we have solved some of the specific technical problems and details on how we remain flexible for future requirements., Comment: 6 pages, 2 figures, submitted to 2024 SPIE Astronomical Telescopes + Instrumentation, Software and Cyberinfrastructure for Astronomy VIII conference

The Observatory Science Operations (OSO) subsystem of the SKAO consists of a range of complex tools which will be used to propose, design, schedule and execute observations. Bridging the gap between the science and telescope domains is the key responsibility of OSO, requiring considerations of usability, performance, availability and accessibility, amongst others. This paper describes the state of the observatory software as we approach construction milestones, how the applications meet these requirements using a modern technology architecture, and challenges so far.

We describe the calibration and imaging heuristics developed and deployed in the ALMA interferometric data processing pipeline, as of ALMA Cycle 9. The pipeline software framework is written in Python, with each data reduction stage layered on top of tasks and toolkit functions provided by the Common Astronomy Software Applications package. This framework supports a variety of tasks for observatory operations, including science data quality assurance, observing mode commissioning, and user reprocessing. It supports ALMA and VLA interferometric data along with ALMA and NRO45m single dish data, via different stages and heuristics. In addition to producing calibration tables, calibrated measurement sets, and cleaned images, the pipeline creates a WebLog which serves as the primary interface for verifying the data quality assurance by the observatory and for examining the contents of the data by the user. Following the adoption of the pipeline by ALMA Operations in 2014, the heuristics have been refined through annual development cycles, culminating in a new pipeline release aligned with the start of each ALMA Cycle of observations. Initial development focused on basic calibration and flagging heuristics (Cycles 2-3), followed by imaging heuristics (Cycles 4-5), refinement of the flagging and imaging heuristics with parallel processing (Cycles 6-7), addition of the moment difference analysis to improve continuum channel identification (2020 release), addition of a spectral renormalization stage (Cycle 8), and improvement in low SNR calibration heuristics (Cycle 9). In the two most recent Cycles, 97% of ALMA datasets were calibrated and imaged with the pipeline, ensuring long-term automated reproducibility. We conclude with a brief description of plans for future additions, including self-calibration, multi-configuration imaging, and calibration and imaging of full polarization data., Comment: Accepted for publication by Publications of the Astronomical Society of the Pacific, 65 pages, 20 figures, 10 tables, 2 appendices. Small corrections and additions from the proof stage have been applied