Enabling co-simulation of tokamak plant models and plasma control systems

A system for connecting the Plasma Control System and a model of the tokamak Plant in closed loop co-simulation for plasma control development has been in routine use at DIII-D for more than 20 years and at other fusion labs that use variants of the DIII-D PCS for approximately the last decade. Here, co-simulation refers to simultaneous execution of two independent codes with the exchange of data between them during execution. Interest in this type of PCS-Plant simulation technology has also been growing recently at other fusion facilities. In fact, use of such closed loop control simulations is assumed to play an even larger role in the development of both the ITER Plasma Control System (PCS) and the experimental operation of the ITER device, where they will be used to support verification/validation of the PCS and also for ITER pulse schedule development and validation. We describe the key use cases that motivate the co-simulation capability and the features that must be provided by the Plasma Control System to support it. These features could be provided by the PCS itself or by a model of the PCS. If the PCS itself is chosen to provide them, there are requirements imposed on its architecture. If a PCS model is chosen, there are requirements imposed on the initial implementation of this simulation as well as long-term consequences for its continued development and maintenance. We describe these issues for each use case and discuss the relative merits of the two choices. Examples are given illustrating uses of co-simulation to address plasma control problems during operation of DIII-D and other devices that use the DIII-D PCS.