Controls

The control plane the beamline runs on, and the seam CORA's edge conducts over. Control plane: Tango + DonkiOrchestra.

SYRMEP runs on the Elettra Tango control stack (the device floor, shared with ID32) with the in-house, trigger-driven DonkiOrchestra framework as the scan / acquisition engine (DonkiDirector schedules DonkiPlayers over a ZeroMQ trigger train, collecting into HDF5). The Elettra 2.0 successor names this orchestration an abstract "Executer" Tango device server feeding the STP3 / MAPI reconstruction and the Elettra Scientific Data Lake. That orchestration is the seam CORA's edge replaces, conducting over Tango rather than over BLISS or EPICS. UNLIKE the public ID32 BLISS config, SYRMEP's device handles are NOT in public source (the DonkiOrchestra source location is unconfirmed and the acquisition code lives in the private gitlab.elettra.eu syrmep_acquisition group), so the handles above are carried confirm-pending placeholders, not invented Tango device URLs (CTRL-1). The reconstruction pipeline (the SYRMEP Tomo Project: phase retrieval, ring removal, FBP / iterative on ASTRA + TomoPy) is post-acquisition compute CORA records as Method / Compute provenance, not data it owns (see model.md).