Controls

The control plane the beamline runs on, and the seam CORA's edge conducts over. Control plane: BCS (LabVIEW).

8.3.2 runs on the ALS BCS (Beamline Control System), a LabVIEW control house-style, CORA's FIRST BCS plane (every prior Site is EPICS, Tango / Sardana, or BLISS). Device IO is BCS, surfaced as scan files (Time Scan, Single Motor Scan, Trajectory Scan) whose headers carry the device-state data record (als-computing/als.bcs). The emerging acquisition layer wraps BCS scans as bluesky ophyd fly devices through the LabVIEW BCS API (als-computing/bcs-api). No public per-beamline BCS channel manifest is published, so the live control handles are not bound here, carried pending staff verification (CTRL-1); when bound they would be modelled as opaque edge handles over the ControlPort, the way the MX3 and ID32 heterogeneous-control precedents do. The continuous-rotation tomography acquisition (the rotary trajectory, the camera triggering, the flat / dark sequencing) runs as a BCS Trajectory Scan; that orchestration is the seam CORA's edge replaces, conducting over BCS rather than replacing it. The downstream data movement and reconstruction (als-computing/splash_flows: Prefect + Globus to NERSC / ALCF, SciCat cataloguing, TomoPy / ASTRA / SVMBIR reconstruction in als-computing/microct) is plumbing CORA observes and subsumes at the debrief layer, not data it owns (see model.md).