Documentation

The full manual ships inside the package; this page is the quick path.

Quick start

Launch

Copy the package anywhere and double-click Demulate.bat. The window opens in 1–2 seconds; the launcher finds a usable Python on its own (or uses the bundled one).

Open a template

The start screen is a grid of template cards. Click one to enter the workbench; the parameter panel, viewport, analysis and AI panels follow the same case.

Run and read results

Press Run. When the job finishes, the results workspace opens with analysis cards computing the numbers. Save the tuned case as .demcase to keep it alive across restarts.

solver untouched — stock YADE physics spawn subprocess stdin / stdout protocol writes loads Qt desktop UI UI shell JobRunner isolated process YADE solver WSL2 .dres result file Viewer & analysis cards
One run, end to end. The UI is only a shell: the job runs in an isolated process, and the physics comes from stock YADE, untouched.

What ships with the app

DocumentCovers
User manual (HTML)Every template, every parameter with its unit and range, all analysis cards and presets, the capability ledger, troubleshooting — generated from the same source of truth as the UI
Capability mapPer-capability verification status with evidence: verified (with proof), planned (with unlock conditions), excluded (with reasons)
START-HERE.md (in the package)Launcher internals: which Python it picks and why, where files live, what to do when something crashes

The manual and the field tables are generated from the code base with byte-exact sync guards in the regression suite: a change to the code without regenerating the docs, or to the docs without regenerating them, turns the tests red. "What the docs say" and "what the software does" cannot quietly drift apart.