You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/explanation/architecture.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ pyAML is not a single package but a small ecosystem. You only install what your
12
12
|`tango-pyaml`| Control-system bindings for TANGO. |
13
13
|`pyaml-cs-oa`| Control-system bindings based on [ophyd-async](https://blueskyproject.io/ophyd-async/), supporting EPICS (Channel Access and PV Access) and TANGO. |
14
14
| Facility packages | Optional packages containing classes specific to one facility (special magnet models, devices, applications, ...). |
15
-
|`pyaml-test-lattice`| A test lattice with ready-made configurations, used in the tutorials. |
15
+
|`pyaml-test-lattice`| A test lattice with ready-made configurations, used in the tutorials and for integration tests. |
16
16
17
17
The core never imports a control system library directly. A control system is selected in the configuration by naming the class of its bindings, which implement the abstract interface of the core. Only the bindings you use have to be installed. See [User Installation](../how-to/installation/user-installation.md) and the [API Reference](../reference/index.md).
0 commit comments