Control Systems#
A connector is OSPREY’s single interface to a control system. The agent, the plans and the safety layers are all written against that one interface, so the machine underneath it is interchangeable. Use the simulator in process for development, the simulator served from its container for rehearsal, and the real hardware for production.
The two-layer connector abstraction, the connectors that ship in-tree,
and where to register your own. Moving from simulator to production
changes control_system.type, not code.
Read a control system and its archiver from a script of your own with
pip install osprey-connectors alone – no agent, no built deployment.
Run against a containerized simulator serving real EPICS Channel Access, with PyAT physics behind the storage-ring lattice channels, so correctors move and BPMs respond.
Rehearse a piece of work on the simulator, then run the same work on the live machine without rebuilding the project or restarting anything.
Let the agent open, read and drive live Phoebus displays through the agent bridge.
Have a model read the Python the agent writes for what it would do to the machine, under rules you write, before it runs.