The Discharge Scenario Library
A scenario library stores proven pulse schedules and their outcomes so operators build on validated starting points rather than from scratch.
Why keep a library
Developing a good discharge takes many shots of trial and refinement. Once a scenario works, it is worth saving so it can be reused and improved rather than rediscovered. A scenario library is the organized store of these proven pulse schedules together with the results they produced.
What each entry holds
- The full pulse schedule of references and feedforward waveforms
- The controllers and limits that were active
- The measured outcome and how well targets were met
- Any off-normal events and how they were handled
- Provenance: which shot validated it and under what machine conditions
Reuse and adaptation
A new discharge usually starts from the closest library scenario, adapted to the day's goal and machine state. This anchors development to something known to work, so operators spend their shots on the intended change rather than on re-establishing the basics. It also makes runs reproducible, since a scenario can be re-run and compared.
Versioning
As scenarios are refined, the library keeps versions, so a change that turned out worse can be rolled back. Linking each scenario to the machine conditions it was validated under prevents applying a scenario in conditions where it is no longer valid, for instance after a wall change alters recycling.
In the Kronos program
For the Hyperion breeder and the burner generators, the scenario library begins in simulation: schedules validated in the flight simulator against the digital twin form the initial entries. Because construction begins in the second quarter of 2027, the first hardware discharges draw on this pre-built library, and operating results then refine and version it.