HEROS Devices
This repository contains python representations (think drivers) of frequently used lab equipment. While these drivers can be perfectly used also locally on the system attached to the lab equipment, the real advantage arises, when the created python object is made available in the network via HEROS.
The drivers in this repository sit in the hardware submodule and are arranged in submodules corresponding the vendor name of the device. The available devices are listed here
Howto Use
You can find more detailed information in the documentation
Using as a HERO with BOSS
Using the BOSS Object Starter Service (BOSS) it is easy to instantiate objects of the classes provided in this repository and make them a HERO that is available through the network. To this end you can either install BOSS in your system and follow it's instructions to create an object from the heros-devices module.
Standalone
The hardware control code in this repository is developed as stand-alone code. That means it also runs locally, without any HEROS magic. Thus, the classes in this module do not inherit from LocalHERO. It is up to the user to make it a HERO or to use BOSS as described in the following.
Interfaces
To signal that a HERO provides a certain interface, herosdevices provides the submodule interfaces. Inheriting
from the classes therein enforces that particular methods and attributes are implemented by the HERO (otherwise it
errors upon initialization of the HERO) and signals it's compatibility through the hero metadata. This allows the
remote site to safely assume that a certain interface is present with the HERO. This allows to, for example, to
transparently use HEROs in an atomiq script as RFSource, VoltageSource, CurrentSource, DACChannel, Switch, etc. This is
explicitly possible without herosdevices depending on atomiq itself. The mechanism can easily be extended to have interface
classes for other systems as well.
.. note:: The interfaces mechanism is completely optional. If a HERO does not inherit from an interface, nothing breaks but also none of the magic described above will happen on the remote side.
Metadata
Release files for herosdevices 2026.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| herosdevices-2026.6.0.tar.gz | 2.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| herosdevices-2026.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 MB
Release files / herosdevices-2026.6.0.tar.gz
| Download URL | herosdevices-2026.6.0.tar.gz |
|---|---|
| Size | 2.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a2740879c08f119aa16635a5268f6898308d071d53f0664bc63f8489d833e42
|
|
BLAKE2b-256 checksum How to use checksums |
0c404d12d4435972e5274eeeef50e8757a54097b13fa81ba019c089897125d8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / herosdevices-2026.6.0-py3-none-any.whl
| Download URL | herosdevices-2026.6.0-py3-none-any.whl |
|---|---|
| Size | 185.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7395921af8756205daf021e07d21262e96b7cfa1f853ccb933af6299c617dbb5
|
|
BLAKE2b-256 checksum How to use checksums |
bb285e16d832c8a5916a95c748cd141f183f5db0b03aa9248234f6b5379d1d73
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
