Same-machine workflow

Use SyntheticBio with PolarH10

SyntheticBio starts the named-pipe synthetic server and helps launch or reuse the PolarH10 app on the matching pipe. The default pipe is polarh10-synth.

Typical flow

Start SyntheticBio first

Open the operator app, keep the default pipe unless you have a reason to change it, and press Establish connection or start the server manually.

Launch PolarH10 on synthetic transport

Let SyntheticBio reuse an existing synthetic session or launch the sibling PolarH10 app with the synthetic transport enabled.

Scan the virtual devices

Use the demo profiles in PolarH10 just like live straps. The scenarios loop, which makes longer capture and validation sessions easier.

Export if you need artifacts

Use SyntheticBio to write fixture folders, benchmark reports, and showcase data without needing to re-run a live session.

CLI launch example

dotnet run --project src\SyntheticBio.Cli -- serve --pipe polarh10-synth --duration 360

dotnet run --project C:\Users\tillh\source\repos\PolarH10\src\PolarH10.Cli -- scan --transport synthetic --synthetic-pipe polarh10-synth

Operator-side notes

Five-minute HRV window

The default 360 s scenario length is long enough to fill PolarH10’s default five-minute rolling HRV window without a loop boundary.

Transport is fixed at startup

If PolarH10 is already running with the Windows BLE transport, close it before trying to reuse the synthetic path.

Cross-site split

PolarH10 Pages gives a short companion-app pointer. SyntheticBio Pages hosts the download flow and the deeper SyntheticBio-specific guidance.