pyrolab 0.5.0

A framework for using remote lab instruments as local resources, built on Pyro5.

Developed by Sequoia Ploeg (for CamachoLab, Brigham Young University).

About

This project aims to allow all laboratory instruments to be accessed as local objects from a remote machine. Instruments that don't natively support such access, such as those required to be connected by a USB cable (or similar), are wrapped with a Pyro5 interface. However, this library may contain other instruments that are already internet-capable and don't rely on Pyro5. That's alright; we're just trying to create a minimal-dependency, one-stop-shop for laboratory instruments!

Note: while the software says "OS Independent", some of the servers are OS-specific. For example, ThorLabs DLL's only work on Windows. However, you could use PyroLab to connect to those devices from any operating system.

Installation

PyroLab is pip installable:

pip install pyrolab

PyroLab declares several "extras", depending on which instruments you need to support:

pip install "pyrolab[tsl550,rto]"

The full list of supported extras is:

• tsl550 (Santec lasers)
• ppcl55x (PurePhotonics lasers)
• rto (Rohde & Schwarz oscilloscopes)
• arduino (Arduino)
• cameras (ThorCam and AmScope cameras, via OpenCV)

You can also clone the repository, navigate to the toplevel, and install in editable mode:

pip install -e .

For development, use uv. From the toplevel, make install (equivalent to uv sync --all-extras followed by uv run pre-commit install) creates a .venv with PyroLab, every extra, and the development tools, and installs the pre-commit hooks. Run tests with make test (or uv run pytest).

Web Monitor

There's a web application that can monitor your PyroLab nameserver and provide an easy-to-access status board. It's a Flask app that can be served using a production grade server. Install it using pip:

pip install pyromonitor

To run:

pyromonitor up

Example

Local Instruments

Locally available instruments just import drivers without using any of the other features of PyroLab.

from pyrolab.drivers.lasers.tsl550 import TSL550

laser = TSL550("COM4")
laser.on()
laser.power_dBm(12)
laser.open_shutter()
laser.sweep_set_mode(continuous=True, twoway=True, trigger=False, const_freq_step=False)

Remote Instruments

First, make sure all configurations on the nameserver computer, instrument server computer, and client are correct (with the proper keys, if configured, etc.).

Run a nameserver:

from pyrolab.api import start_ns_loop

start_ns_loop()

Provide a service:

from pyrolab.api import Daemon, locate_ns
from pyrolab.drivers.sample import SampleService

daemon = Daemon()
ns = locate_ns(host="localhost")
uri = daemon.register(SampleService)
ns.register("test.SampleService", uri)

try:
    daemon.requestLoop()
finally:
    ns.remove("test.SampleService")

Connect using a remote client:

from pyrolab.api import locate_ns, Proxy

ns = locate_ns(host="localhost")
uri = ns.lookup("test.SampleService")

with Proxy(uri) as service:
    resp = service.echo("Hello, server!")
    print(type(resp), resp)

Instrument Server Configuration

PyroLab stores information about instruments and servers when it closes. This means that once PyroLab has been configured once, each time it is restarted, it will remember and reload the previous configuration. Hence, once a server is set up, unless the available instruments, nameserver, or other configurations change, PyroLab will automatically work when started, every time!

For an example of how a new PyroLab instrument server should be configured the first time it's run, see examples/library-catalog/config.yaml.

FAQ's

1. Another instrument library? What about all the others?
   In our experience, many of the other libraries are buggy or have difficulty with network connections. So, our approach was to rely on a well developed and time-tested framework (Pyro) instead of worrying about developing and supporting our own custom set of servers.

2. Is this a standalone software that automatically supports all the advertised instruments?
   No; many of these instruments depend on other software already being installed. In particular, ThorLabs equipment depends on ThorLabs software already being installed on the computer connected to the physical hardware (but not on the remote computer!). As much as possible, though, we try to make the drivers standalone capable.

For Developers

Since the passing of data is, by definition, between hosts and over IP, PyroLab avoids the use of complex Python objects for return values that will be transmitted to remote machines. Since serialization is complicated, and security is even harder, we resort to using only basic Python types when interfacing with hardware (i.e., Python lists, ints, tuples, and not NumPy arrays, matplotlib plot objects, custom objects, etc.).

Releasing

The version lives only in pyproject.toml; pyrolab.__version__ reads it from the installed package's metadata.

Every release starts as a release candidate on PyPI, so what gets tested is exactly what gets released. First commit a changelog file under docs/changelog titled <major>.<minor>.<patch>-changelog.md for the new version; it becomes the release notes for the candidates and the release. Then, with a clean working tree:

make minor      # start a candidate: 0.4.0 -> 0.5.0rc1 (or make patch, make major)
make rc         # if you need another: 0.5.0rc1 -> 0.5.0rc2
make release    # release the candidate: 0.5.0rc2 -> 0.5.0

Each one bumps the version with uv version, commits pyproject.toml and uv.lock, tags vX.Y.Z, and pushes the commit and tag. The tag triggers the release workflow, which runs the test suite, builds and checks the package, publishes it to PyPI, and creates the GitHub release with the changelog as its notes (marked as a pre-release for a candidate). pip installs a candidate only when asked, with pip install --pre pyrolab or pip install pyrolab==0.5.0rc1, so everyone else keeps getting the latest release.

make release only works on a candidate. While a candidate is out, make patch, make minor, or make major can only move it up a level (for example, if 0.5.1rc1 turns out to need a minor release, make minor gives 0.6.0rc1; rename the changelog to match). The rules are in scripts/release.sh.

Publishing uses PyPI's Trusted Publishing: PyPI accepts uploads only from this repository's release.yml workflow running in the pypi environment, so no PyPI token is stored in GitHub. Any PR that edits release.yml gets a dry run (checks and build, nothing published), and the workflow can also be dry-run by hand from the Actions tab.

Code Quality

Formatting and import sorting use ruff, run automatically by the pre-commit hooks that make install sets up. To run it by hand, use make format; make precommit runs every hook on every file, as CI does.

Building the Docs

Much of the API documentation is autogenerated from the source code. Gitignores are in place to prevent you from committing autogenerated pages.

To build the docs, run make doc (which installs the docs dependency group), then make serve to view them at http://localhost:8000. Read the Docs builds them the same way, from uv.lock.

Building the Package

You can test the build and view the bundled artifacts with make build (which runs uv build). It's recommended you build locally before pushing to PyPI. In particular, double check the included files and make sure only the required files are there by modifying MANIFEST.in as necessary.