gac berninaandClaude Sonnet 5 4116d4afb6 Make eco desktop's scope default follow .ecorc like every other subcommand
Real bug: p_desktop hardcoded scope_default=None regardless of .ecorc, so
`.ecorc`'s scope= was silently ignored for `eco desktop` specifically --
even when .ecorc's own command= is something else (e.g. console), running
`eco desktop` on its own should still pick up .ecorc's scope, same as
`eco console`/`eco webapp`/`eco jupyterlab` already do. Now
scope_default=defaults["scope"], matching every other subcommand; the
"plain console, no Namespace panel" case (see eco.widgets.desktop_app) is
still reachable, just needs an explicit `-s ""` or a blank `scope =` in
.ecorc instead of being the unconditional default.

Verified via eco-dev desktop --help with an ECORC pointed at a scope=alvra
file (and command=console, to confirm it isn't gated on command matching)
-- correctly showed "(default: alvra)".

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-21 23:06:07 +02:00
2026-08-18 21:56:17 +02:00
2026-08-18 21:56:17 +02:00
2026-08-21 15:10:25 +02:00
2026-08-18 21:56:17 +02: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
2021-01-13 13:11:22 +01:00
2026-08-18 21:56:17 +02:00
2026-08-21 15:10:25 +02:00
2026-08-21 15:10:25 +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
8.8 MiB
0 Stars 0 Watchers 0 Forks
Languages
Python 86.7%
HTML 10.4%
Jupyter Notebook 2%
Shell 0.8%