Skip to main content

Karabo SCADA Framework - Karabo

Karabo Badge PyPI - Version PyPI - Python Version PyPI - License PyPI - Wheel GitHub language count GitHub top language GitHub contributors GitHub commit activity GitHub Repo stars

Karabo is the European XFEL's SCADA framework. It is a scientific control system that supports plugin (device) development in C++ and Python.

You can find an overview of Karabo on Wikipedia, and in this publication.

The Karabo source repository is on GitHub and also contains our Contributing Guidelines.

Additional documentation is available on ReadTheDocs

Installation

This package facilitates installation of the various Karabo subpackages.

Standalone and Full

For the installation of Karabo we recommend a fresh python environment. If you would like to try Karabo in a standalone fashion on a single machine it's easiest to just run:

pip install 'karabo[full]'

This will install a complete setup, including all essential service devices. Note that pre-compiled binaries will be installed for supported operating systems. Otherwise pip will attempt to compile the source, which might require additional dependencies to be installed first. If source compilation fails, we recommend you follow the instructions at https://github.com/European-XFEL/Karabo, which will result in a self-consistent environment, including a Python interpreter, with similar functionality to a karabo[full] installation.

After installation you should initialize the environment with either

karabo-activate --init-to PATH --standalone

for a standalone system, or

karabo-activate --init-to PATH [--backbone] --broker-host amqp://{broker:port} --broker-topic {TOPIC}

for headless full installations. The --backbone option sets the core services up, and the --broker-* parameters are used to configure the installation according to your AMQP broker setup.

Other options

Instead of a full installation, only individual core packages of Karabo can be installed:

  • karabo[karathon] will install the Karathon Python API
  • karabo[cpp] will install the Karabo C++ API
  • karabo[bound] will install the Karabo Python bindings to C++
  • karabo[services] will install service tools, allowing to manage installations with karabo.daemontools

Options can be combined, such as karabo[karathon,services], which will result in a Karathon installation with service tools installed.

Karabo GUI

If you require the GUI, please install it into a separate Python environment:

pip install karabo.gui

Starting a Karabo standalone system

If you wish to run Karabo standalone you can do this if you have podman or docker installed on the system.

First, run

karabo-activate --init-to $PATH --standalone

Then run

podman-compose -f $PATH/var/containers/compose.yaml up

or (docker-compose ...). This will start containerized version of the services a full Karabo installation requires:

  • A RabbitMQ broker (user: xfel, pw: karabo)
  • An Influx database instance for logging (user: infadm, pw: admpwd)
  • A Grafana installation with the Influx database as a pre-provisioned source (user: admin, pw: admin)

Note that the Grafana provisioning assumes karabo as the broker topic in use. If you've used karabo-activate --broker-topic TOPIC you'll need to edit the data source to refer to a database of TOPIC from inside Grafana.

Additionally, the above setup will use a local sqlite database for projects. You can switch this to MySQL database by providing the following arguments to karabo-activate:

  • --project-db HOST:PORT
  • --project-db-user USER
  • --project-db-pw PASSWORD
  • --project-db-name DATABASE_NAME

Finally, run

$PATH/activate

followed by

karabo-start

Device Development

These packages are not intended to facilitate development of devices for Karabo's C++ API. Please create a self-consistent development environment using the instructions at https://github.com/European-XFEL/Karabo.

Development of devices against these packages using the Bound and Karathon Python APIs should be trivially possibly, as long as the device packages define the correct entrypoints.

For the Karathon API, a line similar to this one should exist in your pyproject.toml:

[project.entry-points."karabo.middlelayer_device"]
PropertyTestMDL = "karabo.middlelayer_devices.property_test:PropertyTestMDL"

For the Bound API, a line similar to this one should exist in your pyproject.toml.

[project.entry-points."karabo.bound_device"]
PropertyTest = "karabo.bound_devices.property_test:PropertyTest"

Metadata

Release files for karabo 3.0.16

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for karabo 3.0.16
File Size Uploaded
karabo-3.0.16.tar.gz 12.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for karabo 3.0.16
File Interpreter ABI Platform
karabo-3.0.16-py3-none-any.whl Python 3 none any Details

Total release size: 24.7 kB

Release files / karabo-3.0.16.tar.gz

Download URL karabo-3.0.16.tar.gz
Size 12.6 kB
Tags Source
SHA-256 checksum
How to use checksums
4b54cbbbd3c6fe7ecbaf073ebf8d4f937bc107e5fc0987134356e20db3db2f27
BLAKE2b-256 checksum
How to use checksums
9c9c00b85f08e54fa6cd62059b211774d1be41452f59a2c983fdb1c2602965cf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.14

Release files / karabo-3.0.16-py3-none-any.whl

Download URL karabo-3.0.16-py3-none-any.whl
Size 12.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3fa09e182858f68145d1487727c55ef37cd15937e58b895fa934725f4069c78f
BLAKE2b-256 checksum
How to use checksums
a161a63384c156267710c829d8c7cfab17466eec5d6a1dee985f33fe7dc1162c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.14

Release history Release notifications | RSS feed

3.1.2

2 release files

3.1.1

2 release files

3.1.0

2 release files

This release

3.0.16 This release

2 release files

3.0.9

2 release files

3.0.8

2 release files

3.0.7

2 release files

3.0.5

2 release files

3.0.3

2 release files

3.0.2

2 release files

3.0.1

2 release files

3.0.0

2 release files

2.21.5

2 release files

2.21.4

2 release files

2.21.3

2 release files

2.21.1

2 release files

2.21.0

2 release files

2.20.8

2 release files

2.20.7

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page