CCAT: Prime-Cam Control System and Related Software
Listen
Radio episode about this paper
Transcript
Introduction to the show: ident: Astrophysics. The day in astrophysics: observations, models and what the data forces.
Vera: We're looking at the paper: "CCAT: Prime-Cam Control System and Related Software".
Jocelyn: Here's the gist of the paper. Prime-Cam is one of the primary instruments being developed for use by the CCAT collaboration with the Fred Young Submillimeter Telescope (FYST), which is undergoing construction at a height of 5600 m in Cerro Chajnantor.
Vera: This paper presents an overview of the Prime-Cam Control System (PCS), developed using the Observatory Control System (OCS) framework, designed to manage hardware and software for remote operations during observations.
Jocelyn: System Architecture The Prime-Cam Control System (PCS) is built upon the Observatory Control System (OCS) framework originally developed for the Simons Observatory (SO).
Vera: Within OCS/PCS, hardware devices are controlled individually by long-running software processes known as “agents,” which are typically deployed in Docker containers running in the background of one of the Prime-Cam network computers.
Title and authors: Vera: We’ve seen how they’ve set up the control infrastructure for this project using the CCAT: Prime-Cam Control System and Related Software paper. Now let's talk about what the authors actually wrote in that introduction and summary section to see their main message.
Jocelyn: I think the core message is that they needed a distributed control system because Prime-Cam has so much hardware, requiring independent management of those components.
Vera: That’s right, it’s about managing all those individual devices through software agents deployed in Docker containers running on network computers rather than relying on a single monolithic system.
Subrahmanyan: From a theoretical side, that distribution is important because it implies modularity in the instrument design itself, allowing different parts to be updated or controlled separately without bringing down the entire observation setup.
Jocelyn: And they clearly show how this system connects everything: from hardware agents on computers to client scripts and the web interface for remote users.
Vera: They emphasize that this whole structure is built upon the OCS framework, which they adapted from their work on the Simons Observatory, showing a scalable approach.
Subrahmanyan: So it’s not just a custom solution; it’s leveraging proven control logic from other major astronomical collaborations to handle the complexity of this new instrument.
Jocelyn: And then they move into the practical details of how these agents communicate and perform their tasks, which is where the engineering gets really interesting for us.
Vera: They give a concrete example with the LakeShore two hundred forty agent controlling those specific USB-connected detectors to show exactly what one of these agents does on day-to-day operations <ref:2611.05253#pg3>.
Subrahmanyan: That detail grounds it, showing how a specific piece of hardware is abstracted into a manageable software process that can be called by client scripts.
Jocelyn: It clarifies the relationship between the physical detector and the network control layer, which is crucial when you’re trying to debug issues remotely.
The paper's summary: Vera: So, summarizing what we've covered so far, this paper describes how they engineered a software backbone for Prime-Cam using agents and Docker containers to manage its hardware. They also detail the client tools like Nextline for script generation and PCS-web for remote control.
Jocelyn: It really paints a picture of an end-to-end system where the goal is to ensure data isn't lost and that operations can be managed reliably from a distance.
Subrahmanyan: The summary highlights that this system directly addresses the need for independent management of hardware modules, which is fundamental when dealing with instruments that have multiple distinct operating frequencies.
Vera: Yes, because those different frequency bands require different control protocols and specific settings to operate correctly, and this system isolates them.
Jocelyn: And they also clearly outline the data flow pipeline, showing how raw HK data gets from the main computer through various agents to final processing at an off-site cluster.
Subrahmanyan: It's telling us that the control system isn't just about running things; it’s fundamentally about establishing a reliable path for high-volume astronomical data to move from collection to analysis.
Vera: And they make it clear that this entire architecture is designed to be flexible, allowing for more complex tasks by chaining different agents together.
Jocelyn: It gives us confidence that the system isn't just a brittle setup; it’s built with sequential tasks and processes in mind, ready for sophisticated observation scheduling.
The paper's improvements: Vera: Moving into the improvements section, they detail several key enhancements over previous versions or approaches to make this system more robust and usable.
Jocelyn: One improvement is definitely that distributed control system for hardware management we talked about earlier, specifically how the LakeShore two hundred forty agent is now running on a dedicated nuc-daq computer <ref:2611.05253#pg3>.
Subrahmanyan: By isolating that specific agent onto its own node, they’re enhancing fault tolerance; if one node fails, it shouldn't necessarily crash the control over all other instrument modules.
Vera: They also improved the remote operation interface by making PCS-web much more intuitive and user-friendly than before.
Jocelyn: Instead of users having to deal with complex PCS scripts or Docker commands, they can now interact with agents directly through buttons and text inputs on that web interface.
Subrahmanyan: That abstraction is significant because it lowers the barrier to entry for running complex sequences, allowing astronomers who aren't systems experts to operate the instrument effectively.
Vera: Then there’s the automated monitoring system, which uses Grafana data feeds to trigger notifications via Slack or Campana if things like cryostat pressure or temperature get out of bounds.
Jocelyn: So it’s not just manual checking; it’s proactive alerting that lets personnel know instantly if data acquisition stops because something critical happened.
Subrahmanyan: That immediate feedback loop is essential for maintaining the integrity of sensitive instruments operating in extreme environments like a high-altitude telescope site.
Conclusion: Vera: So wrapping up this paper on the CCAT: Prime-Cam Control System and Related Software, it seems the authors are showing how to take a complex, multi-faceted instrument and put it under a highly manageable, distributed control umbrella.
Jocelyn: The main implication is that they’ve created a flexible framework where hardware control is decoupled from the user interface, making remote operations much smoother.
Subrahmanyan: For cosmology, this means we can expect more reliable data streams because the system manages the data flow pipeline very tightly from acquisition through to off-site processing.
Vera: It’s about providing a solid foundation for running those long, complex observation scripts that they need for deep sky surveys and detailed mapping.
Jocelyn: And they’ve really made sure that as the instrument grows, this control system is scalable enough to handle more modules without needing a complete overhaul.
Subrahmanyan: The paper establishes a blueprint for how future large-scale instruments can adopt this modular agent-based architecture for reliable control and data handling.
Vera: So in short, it’s about reliability, remote usability, and scalability in managing the software side of big astronomy projects like the CCAT.
Jocelyn: It’s a really solid piece of work that shows how to manage complexity through smart software architecture for these kinds of massive astronomical facilities.
Alicia Middletona, James Burgoyneb, Victoria Butlera, Scott Chapmanb,c, Cody J. Duella, Min Gaoa, Graham Gibsond, Ben Kellera, Lawrence T. Lina, Michael D. Niemacka, Darshan A. Patela, Samantha Walkera, Yuhan Wanga, Ruixuan (Matt) Xieb
Department of Physics at Cornell University · Department of Physics and Astronomy at University of British Columbia · Department of Physics and Atmospheric Science at Dalhousie University · Department of Physics at University of Alberta
astro-ph.IM
Submitted: 2026-11-03
Updated: 2026-11-03
Comments: 11 pages, 8 figures, as submitted to SPIE Astronomical Telescopes + Instrumentation
Journal ref: Proc. SPIE 14155, Software and Cyberinfrastructure for Astronomy IX, 1415508 (19 Aug 2026)
DOI: 10.1117/12.3105331
Code: https://github.com/simonsobs/ocs
License: http://creativecommons.org/licenses/by-nc-sa/4.0/
Importance score: 83/100
The gist: Prime-Cam is one of the primary instruments being developed for use by the CCAT collaboration with the Fred Young Submillimeter Telescope (FYST)…
Key concepts
- Agents
- These are long-running software processes deployed in Docker containers on network computers. They are responsible for controlling individual hardware devices, such as the LakeShore 240s, allowing for independent management of specific components during observation.
- PCS-web
- This is a web interface designed to provide a user-friendly remote operation tool. It allows personnel to control PCS agents using simple buttons and text inputs instead of requiring users to be familiar with complex PCS scripts or Docker commands.
- Nextline
- This tool generates complex observing scripts. It pulls information from the CCAT Operations Database and the observatory scheduler to create line-by-line scripts that interface with multiple PCS agents for sequential tasks during observations.
- Integrated Data Flow Pipeline
- This is a system combining various data streams: HK data files, telescope pointing data from an ACU agent, and detector data from RFSoC controllers. These are combined for quality checks before the final dataset is transferred to an off-site RAMSES cluster.
Terminology
Summary
Prime-Cam is one of the primary instruments being developed for use by the CCAT collaboration with the Fred Young Submillimeter Telescope (FYST), which is undergoing construction at a height of 5600 m in Cerro Chajnantor. p. 0 Niemacka
, Darshan A. Patela
, Samantha Walkera
, Yuhan Wanga
, and Ruixuan (Matt) Xieb
aDepartment of Physics, Cornell University, Ithaca, NY 14853, USA
bDepartment of Physics and Astronomy, University of British Columbia, Vancouver, BC,
Canada
cDepartment of Physics and Atmospheric Science, Dalhousie University, Halifax, NS, Canada
dDepartment of Physics, University of Alberta, Edmonton, AB, Canada
ABSTRACT
Prime-Cam is one of the primary instruments being developed for use by the CCAT collaboration with the Fred
Young Submillimeter Telescope (FYST), which is undergoing construction at a height of 5600 m in Cerro Chajnantor. Prime-Cam requires a number of hardware devices for standard operation and data collection, and so a distributed control
system must be developed for software integration of these devices and user-friendliness when controlling PrimeCam in the field, especially during remote operation that will be typical during observations. The Prime-Cam
Control System (PCS) is being developed using the Observatory Control System (OCS) framework originally
developed for Simons Observatory (SO) and is adapted for Prime-Cam and CCAT-specific requirements.Where the paper says it
Where the paper says it
System Architecture
The Prime-Cam Control System (PCS) is built upon the Observatory Control System (OCS) framework originally developed for the Simons Observatory (SO). Within OCS/PCS, hardware devices are controlled individually by long-running software processes known as “agents,” which are typically deployed in Docker containers running in the background of one of the Prime-Cam network computers. p. 0 The Prime-Cam
Control System (PCS) is being developed using the Observatory Control System (OCS) framework originally
developed for Simons Observatory (SO) and is adapted for Prime-Cam and CCAT-specific requirements. Within
OCS/PCS, hardware devices are controlled individually by long-running software processes known as “agents,”
which are typically deployed in Docker containers running in the background of one of the Prime-Cam network
computers. Within
OCS/PCS, hardware devices are controlled individually by long-running software processes known as “agents,”
which are typically deployed in Docker containers running in the background of one of the Prime-Cam network
computers. These agents are controlled by “client” scripts through the command line or frontend tools like
Nextline and PCS-web.Where the paper says it
Where the paper says it
Green — the paper says it, and the page is printed. Red — no passage carries it, so treat that sentence as unverified. The same check runs on your own text: check a summary against its source, $5.
Improvements for AI systems
-
Distributed Control System for Hardware Management: The Prime-Cam Control System (PCS) uses
agents
deployed in Docker containers running on network computers to control individual hardware devices, allowing for independent management of components like theLakeShore 240 agent, which controls the USB-connected LakeShore 240s.
-
Remote Operation Interface: The PCS provides user-friendly remote access through
PCS-web,
a web interface that allows remote control of PCS agents through buttons and text inputs, eliminating the need for users to be familiar withPCS scripts and Docker commands.
-
Automated Monitoring and Alerting: An alerting system monitors conditions from data feeds in Grafana to trigger notifications via Slack or Campana, allowing personnel to be
notified
if issues likepressure or temperature is very high in some part of the cryostat, or if data acquisition and logging is interrupted.
-
Complex Observation Script Generation: The Nextline tool generates observing scripts from the CCAT Operations Database (OpsDB) and observatory scheduler to run them line-by-line by interfacing with PCS agents, enabling
more complex client scripts involving multiple agents and several sequential tasks and processes.
-
Integrated Data Flow Pipeline: A robust data management plan combines HK data stored in timestamped .g3 files on the main PCS computer with telescope pointing data from the ACU interface agent and detector data streamed by RFSoC controller agents, which are then combined for quality checks before being transferred to an off-site RAMSES cluster.
Abstract
Prime-Cam is one of the primary instruments being developed for use by the CCAT collaboration with the Fred Young Submillimeter Telescope (FYST), which is undergoing construction at a height of 5600 m in Cerro Chajnantor. Prime-Cam can host up to seven instrument modules with kinetic inductance detectors (KIDs), including broadband modules ranging 280-850 GHz and imaging spectrometers for line-intensity mapping. Prime-Cam requires a number of hardware devices for standard operation and data collection, and so a distributed control system must be developed for software integration of these devices and user-friendliness when controlling Prime-Cam in the field, especially during remote operation that will be typical during observations. The Prime-Cam Control System (PCS) is being developed using the Observatory Control System (OCS) framework originally developed for Simons Observatory (SO) and is adapted for Prime-Cam and CCAT-specific requirements. Within OCS/PCS, hardware devices are controlled individually by long-running software processes known as agents, which are typically deployed in Docker containers running in the background of one of the Prime-Cam network computers. These agents are controlled by client scripts through the command line or frontend tools like Nextline and PCS-web. PCS also makes use of several external open source software tools for remote operations, data management, and logging. This system is being tested in the lab in preparation for deployment in 2026 for use with Prime-Cam on FYST.
Related papers
- On-sky demonstration of a vector Zernike wavefront sensor in a cascaded adaptive optics system
- Euclid Data Release 1 (DR1): Calibration strategy and observations
- The General Antiparticle Spectrometer (GAPS) Antarctic Balloon Payload
- Detection and excision of radio-frequency interference in radio arrays
- Unified matched-filter and excess-power pipeline for gravitational-wave detector characterization
- Ushering in sub-arcsecond angular resolution observatories in the far-infrared: The case for a double-Fourier interferometer