Pith. sign in

REVIEW

SKAO Observation Execution Tool: Designing for concurrent, responsive observations

Not yet reviewed by Pith; the record is open.

This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.

SPECIMEN: schema-true, not a live event

T0 review · schema-true

One-sentence machine reading of the paper's core claim.

pith:XXXXXXXX · record.json · timestamp

arxiv 2407.17149 v1 pith:I4FBZIT3 submitted 2024-07-24 astro-ph.IM

classification astro-ph.IM
keywords telescopechallengescontroldesignexecutionobservationsoftwareconcurrent
verification ladder T0 review T1 audit T2 compute T3 formal
0 comments
read the original abstract

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.

Discussion (0). Sign in to comment.

Pith tools