Development Reports

plesty-bench From download to a first measurement, on one PC

plesty-bench A run is its own record, on the lab's shared disk

plesty-bench Fleets across benches, and a Hub that shows what a bench holds

plesty-lib A run's settings choose its devices

plesty-lib New instruments and the experiments built on them

plesty-bench Set up, run and watch an experiment from the bench console

plesty-lib Typed experiment data, with the spectrum first

plesty-lib The Analyzer contract — one shape for turning data into results, piloted by plesty-fss

plesty-bench The Bench Console — a new core project installs, launches and supervises a bench PC's device servers

plesty-lib The field test every device runs — one shared on-hardware gate sequence, generated per module

plesty-lib Watching a Run — the Monitor contract gives an experiment a live view from one function

plesty-lib The Experiment Framework — async Experiment ABC with plan, journal & resumable checkpoints

plesty-sdk Zero-effort device docs & gate d3 — reference pages from the live device model

plesty-sdk Schema-usage gates lock the device/experiment data layer

plesty-sdk Introduced 14+d1 automated HUB module validation gates (plesty check)

plesty-sdk Gate d1: Device API Pipeline — 8 mock-gate test suite for device modules

plesty-lib DevicePipeline reusable test harness & schema-driven SCPISolver.solve_func