Skip to content
Technology How it works Breeder — Hyperion Burner — Aegis Burner — MetroVolt AI-Native Architecture Magnets Fuel cycle Safety Roadmap
Solutions AI & Data Centers Defense & Government Grid & Baseload Neutron Detection Quantum
Learn Technical Library
Proof Publications Whitepapers Technical Library Open Science & Reproducibility The Honest Gates
Company About / Mission Leadership Environment Health & Safety Investors Careers Press Contact
3D Model
AI Architecture › L3 · Twin Modeling & AI
L3 · Twin Modeling & AI

Actuator Allocation Across Coupled Systems

Both machines have more actuators than control objectives; Kronos's MPC allocates effort across coils, heating, fueling and DEC to meet goals with margin.

THE STACK · click to jumpL7Ecosystem & StrategyL6Experience & VisualizationL5Applications & CopilotsL4OrchestrationL3Twin Modeling & AIL2Data FabricL1Control PlaneL0Foundation▲tlmctl▼L3 · TWIN MODELING & AIThe KRONOS-CTRL digital twin and its predictive shadow.1KRONOS-CTRL Twinlive plant state2GNNscoupled subsystems3PINNsphysics-constrained4Anomaly Ensemblesdrift & fault detection5MPCreceding-horizon control6Predictive Shadowruns seconds aheadMACHINE TIEState estimate descends to L1 control; alerts rise to L4 / L5.KRONOS FUSION ENERGYAI-NATIVE S.M.A.R.T. GENERATORTWIN MODELING & AISHEET 05REV. 2026-08L3 · AI-NATIVE STACK
L3 · Twin Modeling & AI — its place in the stack (left, click any layer) and its internal components (right). Telemetry rises; control descends.

Over-actuation as an asset

The breeder has many poloidal-field and solenoid coils plus heating and fueling; the burner has plug fueling, multiple heating sources and DEC potentials. There are more actuators than independent control objectives, which is an asset: the same shape or confinement target can be met by many actuator combinations, and MPC picks the combination that also respects secondary goals, staying off actuator limits, minimizing strain, keeping reserve for disturbance rejection.

Allocation inside the optimization

Kronos does not use a separate allocation stage; allocation falls out of the MPC objective. The actuator-effort term u^T R u with a per-actuator weight matrix R distributes effort, and constraints keep each actuator within limits with headroom. Weighting a nearly saturated coil more heavily pushes effort to coils with reserve, preserving the ability to respond to the next disturbance.

python
# per-actuator effort weighting drives allocation
R = diag(r_i)                      # larger r_i -> use actuator i less
r_i = base_i * (1 + saturation_penalty(u_i))   # back off near limits
# result: objectives met while keeping reserve on constrained actuators

Allocation is coupled across physics in the burner. The DEC collector potential serves double duty, energy extraction and ambipolar-boundary setting, so its use is allocated jointly by the plug-density MPC and the Power-Systems control. Kronos solves these with a shared state so the allocation is consistent rather than two controllers fighting over one actuator.

When an actuator degrades or is taken offline, the over-actuation provides graceful reconfiguration: MPC simply re-solves with that actuator constrained out, and the remaining actuators pick up the objective if the envelope still permits. If they cannot, the envelope shrinks and the controller moves to a safe reduced-performance operating point rather than pretending the objective is still reachable.

Content reviewed August 2026 · design-and-simulation stage