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

Surrogate Models Inside the MPC Loop

MPC needs to roll the plant model forward many times per cycle, so Kronos uses fast differentiable surrogates as the prediction model.

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.

The rollout cost problem

Every MPC solve rolls the dynamics forward over the horizon, many times, as the optimizer searches. If each rollout required a mesh-based physics solve, MPC could not run in real time. Kronos uses the L3 surrogates, the equilibrium and stability PINNs for the breeder, the ambipolar-potential PINN for the burner, as the prediction model f_twin, so each rollout is a sequence of fast forward passes.

Differentiability buys gradients

Because the surrogates are neural networks, they are differentiable end to end. MPC gets gradients of the predicted trajectory with respect to the actuator sequence for free via automatic differentiation, turning the optimization into a smooth gradient-based problem rather than a derivative-free search. This is a major reason Kronos chose PINN surrogates over black-box lookup: the sensitivity information is intrinsic.

python
# gradient-based MPC step using a differentiable surrogate
x = rollout(f_surrogate, x0, u_seq)     # forward passes over horizon
J = cost(x, u_seq)
grad = autodiff(J, u_seq)                # d cost / d actuators
u_seq = project_to_constraints(u_seq - step * grad)   # one RTI step

The surrogate must be accurate over the horizon, not just at one point, so Kronos trains and validates the surrogates specifically on rollout accuracy, penalizing accumulated multi-step error, not only single-step error. A surrogate that is pointwise accurate but drifts over a rollout would give MPC a confidently wrong forecast.

Uncertainty into the loop

The surrogate reports predictive uncertainty, and MPC uses it: higher uncertainty tightens the effective constraints (via the envelope shrinking) so the controller is more cautious where the model is less trustworthy. This closes the loop between surrogate fidelity and control conservatism, ensuring MPC never bets more on the model than the model's validated accuracy justifies.

Content reviewed August 2026 · design-and-simulation stage