Outline

1. Development of a flight simulator for the control of plasma dischargesN. Ravenel, JF Artaud, S. Brémond, B. Guillerminet, P. Huynh, P. Moreau, Ja. Signoret

2. Outline • Motivations • Functional needs • Modes of operation for the flight simulator • Tools for the flight simulator • Outcome and future work

3. Motivations  Real time control of plasma discharge: an old problematic new challenges are coming Today's tokamaks Plasma control issues Support in scientific program Intrinsic instabilities Complex non linear behavior ITER  new challenges Safety of machine operation Machine protection Narrow path to burning plasma experiments Build a plasma discharge flight simulator for the development, the tests and the validation of scenarios or advanced controls.

4. Functional needs User needs • For the physicists, the development of sophisticated controllers using a friendly environment (a control toolbox). • To browse and tune the variables of the controller during the simulation • To build the scenarios using a graphical interface. • Between two pulses, to validate the parameters using the simulator(predictive mode). • To test the controller using the ITM framework. • To configure and run the simulation. • To exchange data/parameters between the tokamak database and the simulator. • To easily generate the controller developed (stand-alone C function). Simulation needs Implementation needs

5. Tokamak Present stage Configuration tool - CONTROLLERS + RT Diagnostics

6. Discharge Simulator Control toolbox KEPLER (Codes, METIS CRONOS, etc.) Tokamak ITM Local configuration Flight simulator Synthetic diagnostics Tokamak Configuration + Raw data (ie field B, etc.) CONTROLLERS - RT DIAGNOSTICS Data (ie Ip, Rp, Zp, etc.)

7. + - Simulation mode Needs : development, tests Discharge Simulator Control toolbox KEPLER (Codes, METIS CRONOS, etc.) ITM Local configuration Data (ie Ip, Rp, Zp, etc.) To use a friendly environment to develop controller (control toolbox). The controller code must be integrated in Kepler.

8. CONTROLLERS New controller Connected mode Needs : test in the final target before the plasma Plasma simulator KEPLER (Codes, METIS CRONOS, etc.) Synthetic diagnostics Tokamak Configuration - ITM Raw data (ie field B, etc.) + Local configuration RT Diagnostics Data (ie Ip, Rp, Zp, etc.)

9. Tokamak Configuration Tokamak + CONTROLLERS - RT DIAGNOSTICS Flight simulator : three modes Plasma Simulator Control toolbox KEPLER (Codes, METIS CRONOS, etc.) Synthetic diagnostics ITM Raw data (ie field B, etc.) Local configuration Data (ie Ip, Rp, Zp, etc.)

10. Exchange dataITM framework  tokamak database  ITM data structure = Consistent Physical Object CPOs. Data access through UAL Universal access layer (access/retrieve/store). Machine Dependant • Some CPOs are ‘in progress ‘ (ex: controllers) . Add «private» CPO a private UAL will be used. • Exchange data between the ITM data structure and the tokamak database • -> Exp2itm (designed for JET and Tore Supra, MDSplus) : import data and parameters to the ITM environment. Tore Supra have provided its machine description and the mapping file. Poster J. Signoret • -> The export tool have to be developed. Use a XML mapping file. Tokamak Configuration ITM Local configuration

11. ITM framework : Kepler and the associated tools Needs : to build and run the simulation A tool to design and run workflows with wrapped physics modules as elementary “acting units” called actors. • Actors : UALinit, UALcollector, plasma code, controllers, … • FC2K (Fortran/C/C++ to Kepler) tool

12. ISEEuropean Simulator Interface Needs : to configure and run the simulation • ISE: editor • Parameters setting • Waveform/arrays • ISE: simulation control interface • Check • Run • Monitor • Overview Development of specific functionalities (the internal variables of the controller, building of the scenarios).

13. The control toolbox Needs : a control toolbox to design the controller. A code generator. • Freeware. Scicos. Developed by the INRIA (French national institute for research in computer science and control). • Collaboration for the integration of Scicos block in Kepler. • After development, the code generator will produce a stand alone “C callable function”for the integration in Kepler and in the target unit. Scicos blocks C code

14. Applying on Tore Supra To develop a new monitoring mode to achieve the “Connected mode”. To improve modularity of the existing code to facilitate the integration. Under progress. Simulator Local (TS) configuration Controllers TS ITM configuration RT Diagnostics Make available necessary real time data(Equinox : RT plasma equilibrium reconstruction).

15. Outcome and future work The technical and functional specifications of the project are ended. An generic framework A collaboration with the INRIA has been initiated for the integration of Scicos in Kepler. Milestone 2009 (Q4) first iteration of the project (the K test).

16. Thank you for you attention

17. Diagnostics Diagnostics APLASMA Controllers APOLO AGAZ AHYB AFCI AFCE Poloidal Gaz injection LHCD ICRH ECRH Actuators APLASMA : supervisor of the controllers

18. Scénario#1 (ex. Plasma breakdown) Scénario#2 (Plasma limiter) Scénario#3 (X-point formation) Scénario#4 (Burning phase) Transition #1#2 Transition #2#3 Transition #3#4 Transition #4#5 • Ip • Vloop • qpsi • ECRF • Prefill • I poloidal • … • Ip • Vloop • qpsi • Rp, Zp, e, t • heating syst. • … • Ip • X-point pos • Strike points • Rp, Zp, e, t • heating syst. • … • Ip • fusion power • heating syst. • Rp, Zp, e, t • b, li • … Recovery Strategies #1 Recovery Strategies #2 Recovery Strategies #3 Recovery Strategies #4