Skip to main content

Module controller

Module controller 

Expand description

The demo’s run controller: one seeded study, advanced one trial at a time.

The controller owns all mutable optimizer state. A frame calls Controller::tick, which runs at most one ask/evaluate/tell transaction and returns; the page then refreshes its read-only views from the controller’s accessors and latest StudySnapshot. Pausing therefore always lands between transactions, and nothing here needs a window, a clock, or a browser, so host tests drive the exact sequence the browser build replays.

Structs§

Controller
Drives one seeded study a transaction at a time.
RunConfig
What a run is configured with.
TrialRecord
One completed trial as the demo shows it.

Enums§

PauseReason
Why a run is paused.
SamplerChoice
A sampler the demo can run. Each choice is a separate, separately seeded run; the demo never ranks them.
Status
Where a run is in its lifecycle.

Constants§

DEFAULT_BUDGET
The browser demo’s trial budget.
DEFAULT_SEED
The public seed every demo run starts from.