Henrik Lemke 44d4400d61 Property grids: setpoint next to the readback, "⋯" item menu per row
Both grids (Qt display_qt, ipywidgets display_widget) now show the
absolute-value entry right after the readback, with step and up/down
tweak buttons after it.

Every row - Adjustable, Detector or sub-assembly - ends in a "⋯" menu
(also on right-click of the name in Qt) offering what the item supports:
its _widget_* views, a live strip chart in the same window/page, the
archiver strip plot window, archiver history (10 min .. 7 days), the
indicator gadgets, its memories, details (channels, unit, limits, doc),
and in Qt copy name / PV names and Find IOC. In eco desktop new views dock
next to the grid; in a notebook they open as closable panels below the
row. All GUI code lives in eco/widgets (item_menu, item_menu_qt,
item_menu_ipy); archiver's plotting is split into _plot_dataframe_on so
the panels can draw into their own figures.

Hardware and archiver access stays off the GUI/kernel thread; matplotlib
renders from threads are serialized; the rows' menus hold the grid only
weakly.
2026-10-30 18:12:05 +01:00
2026-10-04 10:08:08 +02:00
2026-08-18 21:56:17 +02:00
2026-10-30 12:16:03 +01:00
2026-08-18 21:56:17 +02:00
2018-07-06 12:38:44 +02:00
2026-08-18 21:56:17 +02:00
2026-08-18 21:56:17 +02:00
2026-08-18 21:56:17 +02:00
2026-09-20 07:44:29 +02:00
2021-01-13 13:11:22 +01:00
2026-08-18 21:56:17 +02:00
2026-08-21 15:10:25 +02:00
2025-06-24 15:33:02 +02:00

eco — Experiment Control

                       ___ _______
                      / -_) __/ _ \
 Experiment Control   \__/\__/\___/

eco is a Python-based control environment for experiments, developed and used at SwissFEL, PSI. It is used both as:

  • a library of experimental devices for higher-level Python applications or GUIs, and
  • an interactive command-line interface, e.g. from an IPython/Jupyter shell or notebook.

eco follows an object-oriented approach: every device is represented as a Python object with a small, predictable interface, so devices can be freely combined in generic control/acquisition routines and analysed with the scientific Python ecosystem. For a general introduction to object-oriented Python, see e.g. this short introduction.

Documentation

The full documentation — installation, core concepts, and worked examples (listening monitors, archiver data and strip charts, pipeline offload, motor configuration) — lives in docs/ and is built with Sphinx, configured to build on Read the Docs via .readthedocs.yaml.

Build it locally:

pip install -r docs/requirements.txt
sphinx-build -b html docs docs/_build/html

Installation

conda install -c paulscherrerinstitute eco

or, for development, in editable mode from a checkout:

git clone https://github.com/paulscherrerinstitute/eco.git
cd eco
pip install -e .

See Installation for beamline-specific setup (the eco launcher, .ecorc defaults) and the full dependency picture.

Creating a new device

New devices are implemented as a subclass of Assembly, which provides naming, aliasing, and shell representation:

from eco.elements.assembly import Assembly

class MyDevice(Assembly):
    def __init__(self, name=None):
        super().__init__(name=name)
        self._append(MySubObject, name="my_sub_object", is_setting=True, is_status=True)

is_setting=True marks the child as a setting of the assembly (shown by .settings() and captured when settings are saved); is_status=True marks it as contributing to the assembly's .status(). See Representing real devices — the Assembly in the full docs for the rest of the model (Adjustable, Detector, Namespace) and a from-scratch, runnable example of each.

S
Description
Experimental control package
Readme GPL-3.0
7.1 MiB
0 Stars 0 Watchers 0 Forks
Languages
Python 87%
HTML 9.7%
Jupyter Notebook 1.9%
Shell 0.9%
JavaScript 0.3%