#
Asynchronous Bluesky hardware abstraction code, compatible with control systems like EPICS and Tango.
Source |
|
|---|---|
PyPI |
|
Documentation |
|
Releases |
Ophyd-async is a Python library for asynchronously interfacing with hardware, intended to be used as an abstraction layer that enables experiment orchestration and data acquisition code to operate above the specifics of particular devices and control systems.
Both ophyd sync and ophyd-async are typically used with the Bluesky Run Engine for experiment orchestration and data acquisition.
The main differences from ophyd sync are:
Asynchronous Signal access, simplifying the parallel control of multiple Signals
Support for EPICS PVA and Tango as well as the traditional EPICS CA
Better library support for splitting the logic from the hardware interface to avoid complex class heirarchies
It was written with the aim of implementing flyscanning in a generic and extensible way with highly customizable devices like PandABox and the Delta Tau PMAC products. Using async code makes it possible to do the “put 3 PVs in parallel, then get from another PV” logic that is common in flyscanning without the performance and complexity overhead of multiple threads.
Devices from both ophyd sync and ophyd-async can be used in the same RunEngine and even in the same scan. This allows a per-device migration where devices are reimplemented in ophyd-async one by one.
How the documentation is structured#
Documentation is split into four categories, also accessible from links in the top bar.
- How-to Guides
- How to choose the right base class when implementing a new Device
- How to contribute to the project
- How to implement a Device for an EPICS areaDetector
- How to interact with signals while implementing bluesky verbs
- How to use settings to put devices back in their original state
- How to store and retrieve device settings