Python Library for Experimental Science and Technology

From instrument to report, one shared platform.

Every instrument becomes a Python module that labs share through the hub. Experiments are built from those modules, run and watched from PLESTY Bench, and every run leaves a report of what it did. Try it on your laptop first: the demo replays a real photoluminescence measurement, with no hardware attached.

Try the demo → Download PLESTY Bench →

Shared instrument modules Runs without hardware A report for every run

1 / 6 From a folder of scripts to one measurement No more guessing which copy of the script ran, with which port and which settings. Instruments, measurement, analysis and report follow one path.

A terminal starts the two demo instruments and then the run, whose log records each step; the monitor then fills in the spectrum, the spectral map and each line's energy shift against wave-plate angle, step by step up to 92 of 92. — 2 / 6 **Two commands, and the data draws itself** The pol-pl demo measures polarization-dependent photoluminescence of a quantum dot. Start the instruments, start the run, and every step is recorded as it happens. No instrument is attached: the spectrometer replays spectra really measured on the sample.

Selecting the pm100d power meter in PLESTY Bench and pressing Control; its panel opens, Take control is ticked, the wavelength is set to 780 nm and Measure power returns a reading, then, held, keeps updating it once a second until it is held again. — 4 / 6 **Drive an instrument by hand** Select an instrument and press Control: its panel opens with every setting and operation the module declares. Take control, set a wavelength, measure, with no script. Hold a reading or a parameter and it streams, once a second, until you hold it again. Panels open read-only, so looking never disturbs a measurement.

Build your own experiment

Your instruments, your measurement.

Everything above is built from parts you can write yourself: a Python package per instrument, an experiment that combines them, and the tooling that tests and publishes both. Two guides take you from an empty folder to a device and a measurement running on a bench.

Build & run a device → Build & run an experiment →

A terminal: plesty init device creates plesty-powermeter, uv run pytest passes 9 tests, and plesty check passes every gate of the pixel standard. — 1 / 2 **A device module, scaffolded and checked** plesty init writes a device module from the template: the package, its tests, its docs and the pre-push hook. The tests pass from the start, and plesty check measures it against the Plesty standard, as the hook does again on every push.

One ecosystem

Standards, SDK, and shared lab modules in one loop.

Plesty combines reusable software components, documentation automation, and project checks into one CI/CD-friendly system for experimental science.

hub.plesty.net: searching for spectrometer, opening the LightField spectrometer's card and copying its install line, then filtering the list to experiments. — 1 / 3 **Find a module on the hub** hub.plesty.net lists every published instrument, analyzer and experiment, with its checks and field tests. Search it, open a module, and copy the line that installs it.

🧩

PlestyLib

Reusable Python components for devices, experiments, data, and automation patterns.

Standardized interfaces
Device-oriented modules
Experiment-ready abstractions

⚙️

PlestySDK

Project scaffolding, documentation generation, standard checks, and CI/CD integration.

Project scaffolding via templates
Sphinx docs from Python docstrings
Automated testing and deployment

🌐

PlestyHub

The catalog of published devices, analyzers, and experiments.

Reusable device catalog
Reproducible experiments
Community ecosystem

Join us

Build Plesty with us.

Ask questions, share the instrument you are wrapping, and meet the labs already measuring with Plesty. Researchers and developers alike are welcome.

Join the community →