Skip to main content

plesty-server · plesty-bench

The bench PC's own console for the PLESTY platform. It installs hub modules, starts and supervises device servers, runs field tests against the real instruments, and runs experiments across the lab's benches — keeping the logs, the runs and their reports — so a lab bench is set up and kept running from one place instead of one venv, one terminal and one hand-written uv pin per instrument.

This repository publishes two packages:

Install on Install with
plesty-server — the bench application: CLI, Qt console, agent the bench PC the installer from the releases
plesty-bench — the client that drives a bench from elsewhere your own machine uv tool install plesty-bench

Each release carries a Windows setup.exe (per-user, no admin) and an install.sh for macOS and Linux. Both install the whole application, console included, pinned to that release, and add a Start-menu or Launchpad entry. Without an installer, uv tool install "plesty-server[gui]" installs the same thing on macOS or Linux.

Bringing up a bench

plesty-server fleet init                      # a fleet.yaml to declare into
plesty-server declare pm100d plesty-pm100d --version 0.2.1 \
    --arg --address --arg "USB0::0x1313::…::INSTR"
plesty-server start pm100d                    # installs, launches, waits until it answers
plesty-server status

The instrument is now reachable from an experiment PC at this machine's address on the port status reports. plesty-server gui opens the same bench in a window; plesty-server fleet run keeps it up headless after a reboot.

Driving it from your own machine

The bench serves an agent; the client sends it plesty-server command lines and follows the output.

plesty-bench -b lab-bench-03 status
plesty-bench -b lab-bench-03 field-test pm100d --gates connect,drain
plesty-bench -b lab-bench-03 control pm100d          # a control panel per device

Documentation

Full documentation — start there if anything below is unfamiliar. It is in three parts:

Part Covers
GUI The window element by element: the Devices and Experiments tabs, every menu, every dialog, the Control window
CLI plesty-server, plesty-bench, and every file and setting
Usages Tasks start to finish: set up a bench, install modules, field-test, run an experiment, work remotely, run without a window, maintain

A new bench starts at Set up a bench.

Design and internals covers the architecture, the process model, the port rules, the installer, the agent protocol, experiment runs, the platform differences and the release machinery — for contributors, and for anyone debugging behaviour that only makes sense once the mechanism is visible.

New to the platform? The PLESTY quickstart runs a whole experiment against a bench and is the gentlest way in.

Metadata

Release files for plesty-server 0.5.0

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

Source distribution (sdist)

Source distribution for plesty-server 0.5.0
File Size Uploaded Provenance Actions
plesty_server-0.5.0.tar.gz 306.0 kB Without provenance Details for plesty_server-0.5.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for plesty-server 0.5.0
File Interpreter ABI Platform Actions
plesty_server-0.5.0-py3-none-any.whl Python 3 none any Details for plesty_server-0.5.0-py3-none-any.whl

Total release size: 663.0 kB

Release files / plesty_server-0.5.0.tar.gz

Download URL plesty_server-0.5.0.tar.gz
Size 306.0 kB
Tags Source
SHA-256 checksum
How to use checksums
0e7e85706c5a20d758c28a7a72f26e671f1c552c1447d71dd4e3062b2df7fd27
BLAKE2b-256 checksum
How to use checksums
e7ff506533f8164f7dd636a4cd1b57a6666c5a39a4935fa4d95695e31a86d0f7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.9.30 {"installer":{"name":"uv","version":"0.9.30","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"12","id":"bookworm","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / plesty_server-0.5.0-py3-none-any.whl

Download URL plesty_server-0.5.0-py3-none-any.whl
Size 357.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c93c3fdbd3290eec80780bf4a574a4c6a6ab8cfec1c05c0b246fc4b48c107e4d
BLAKE2b-256 checksum
How to use checksums
45dade7ddaccc6d8fb3e8add2c12420579d66f34725478bc7601c3a941355dad
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.9.30 {"installer":{"name":"uv","version":"0.9.30","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"12","id":"bookworm","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for plesty-server 0.5.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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