SKA control system in 2025

It is 2025 and the SKA Telescope Control System has come a long way since the start of construction. The outline of the software architecture and some key technology decisions (including the choice of Tango) were made early. To keep the geographically distributed teams engaged, and avoid creating silos and fragmentation, development of virtually all the software components started in parallel; often while the detailed designs for the custom hardware was still evolving and before the COTS equipment was selected. The deployment strategy was adjusted to align with the industry trends. From designing a software system for hardware that does not exist we arrived at the point where we can prove that the software can actually work with the hardware. However, the software design and implementation meeting reality uncovered some issues, forcing us to make changes (ska-tango-base) and learn hard lessons (naive implementation of event callbacks). Are we ready to deliver a large distributed control system? We realize that scalability will be a challenge. This paper provides an honest overview of what works and what did not work so well, and how we address issues.

Publication Details

Journal
JACOW
Published
2025-12-05
DOI
https://doi.org/10.18429/jacow-icalepcs2025-wemg002
Primary Topic
Radio Astronomy Observations and Technology
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

SKA control system in 2025

JACOW
Radio Astronomy Observations and Technology
article

SKA control system in 2025

article en

Abstract

It is 2025 and the SKA Telescope Control System has come a long way since the start of construction. The outline of the software architecture and some key technology decisions (including the choice of Tango) were made early. To keep the geographically distributed teams engaged, and avoid creating silos and fragmentation, development of virtually all the software components started in parallel; often while the detailed designs for the custom hardware was still evolving and before the COTS equipment was selected. The deployment strategy was adjusted to align with the industry trends. From designing a software system for hardware that does not exist we arrived at the point where we can prove that the software can actually work with the hardware. However, the software design and implementation meeting reality uncovered some issues, forcing us to make changes (ska-tango-base) and learn hard lessons (naive implementation of event callbacks). Are we ready to deliver a large distributed control system? We realize that scalability will be a challenge. This paper provides an honest overview of what works and what did not work so well, and how we address issues.

JACOW
Industry, innovation and infrastructure
Openalex Percentile: Top 38%
Radio Astronomy Observations and Technology
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

SKA control system in 2025 · JACOW (2025) | TGRS Research Map | TGRS