- Email: [email protected]
The design of remote discharge scenario management system on EAST
G Model
ARTICLE IN PRESS
FUSION-8713; No. of Pages 6
Fusion Engineering and Design xxx (2016) xxx–xxx
Contents lists available at ScienceDirect
Fusion Engineering and Design journal homepage: www.elsevier.com/locate/fusengdes
The design of remote discharge scenario management system on EAST W.T Chai a,b,∗ , B.J Xiao a,b , Q.P Yuan a , R.R. Zhang a a b
Institute of Plasma Physics, Chinese Academy of Sciences, Hefei, Anhui, PR China University of Science and Technology of China, Hefei, Anhui, PR China
h i g h l i g h t s • The remote discharge scenario management system is established on EAST, it provides some useful function for operators to manage discharge scenarios and formulate discharge schedule.
• Operators can use this system to formulate discharge schedule on account of it can electing optimal scenarios automatically. • The system is not only for local user but also for remote user. • In the future, we can combine with actual discharge data and data mining technology to acquire optimal configuration, which to generate expert database and guiding experiment.
a r t i c l e
i n f o
Article history: Received 19 June 2015 Received in revised form 26 February 2016 Accepted 8 April 2016 Available online xxx Keywords: PCS EAST Web Discharge scenario
a b s t r a c t The discharge scenarios on EAST plasma control system (PCS), characterized by different waveform parameters and different hardware requirements, will need a systematic discharge scenario management system for remote and local operators, in order to optimize storage structure and rationally manage discharge time. The remote management of discharge scenarios will require extending the functionalities of the present PCS “future shot” and “next shot” modules. Taking advantage of database technique, the operators can acquire detail information of all discharge scenarios directly without PCS user interface and search the specified scenarios by key words. In addition, the system can elect optimal scenarios automatically based on discharge schedule and plasma pulse setting for later artificial selection. To this purpose, a new remote discharge scenario management system (RDSMS) basis for Web is being conceived on EAST. The system contains a database with functions of “user management”, “scenario verification”, “prepared scenario management”, “actual discharge scenario management” and “discharge schedule management”. This paper will present the relevant conceptual design and give an account of the test results for implementation on EAST discharges. © 2016 Elsevier B.V. All rights reserved.
1. Introduction Coping with multiple discharge scenarios in an efficient way is an important issue in plasma operation, some previous design or application has being conceived on some tokmaks such as Tore Supra [1], ITER [2], ASDEX [3], JT-60 [4] for improved device operation. This paper reports conceptual design of EAST RDSMS. After several years of development, EAST has become very complex device, containing a number of sophisticated sub-systems that demand complex operator programming for control during a discharge. Improper programming can lead to unwanted abnor-
∗ Corresponding author at: Institute of Plasma Physics, Chinese Academy of Sciences, Hefei, Anhui, PR China E-mail address: [email protected] (W.T Chai).
malities or shot abort during a discharge. At present, EAST operators manage discharge scenarios using the plasma control system, which was adapted from DIII-D [5]. EAST PCS saves future shot parameters setting information in form of PCS setup files (which are named in suffix by .wa10) for use in discharge execution and archives the actual discharge shot parameters setting information in PCSSETUP nodes of MDSplus tree named pcs east during the discharge [6], However, although EAST operators can call and retrieve these parameters through filename, user name or shot number (Fig. 1), there is no way to obtain more detail information on these parameters. An improvement in the retrieval functions is the object of this paper. In order to manage discharge scenarios efficiently and conveniently, a remote discharge scenarios management system based on Web input is presented in this paper. The system takes advantage of database technology to implement the functions of scenario
http://dx.doi.org/10.1016/j.fusengdes.2016.04.015 0920-3796/© 2016 Elsevier B.V. All rights reserved.
Please cite this article in press as: W.T Chai, et al., The design of remote discharge scenario management system on EAST, Fusion Eng. Des. (2016), http://dx.doi.org/10.1016/j.fusengdes.2016.04.015
G Model FUSION-8713; No. of Pages 6 2
ARTICLE IN PRESS W.T Chai et al. / Fusion Engineering and Design xxx (2016) xxx–xxx
Fig. 1. Discharge scenario calling and retrieval in EAST PCS.
Fig. 2. The existing scenario management on EAST.
Fig. 3. System architecture of RDSMS.
verification, scenario classification, scenario query, scenario calling and actual discharge scenario. Furthermore, the operator can use
this system to formulate a discharge schedule based on an automatically generated optimal scenario.
Please cite this article in press as: W.T Chai, et al., The design of remote discharge scenario management system on EAST, Fusion Eng. Des. (2016), http://dx.doi.org/10.1016/j.fusengdes.2016.04.015
G Model FUSION-8713; No. of Pages 6
ARTICLE IN PRESS W.T Chai et al. / Fusion Engineering and Design xxx (2016) xxx–xxx
3
Fig. 4. The workflow of RDSMS.
Fig. 5. Interface design of discharge schedule management.
2. Existing scenario management on EAST EAST PCS is a PC cluster with four nodes (one host node and three real-time nodes) [5]. An IDL user interface is provided for
users to input discharge parameters [7] and contains three control modules respectively called “future shot”, “next shot” and “shared shot” [8], among these, “future shot” and “next shot” related to scenario management. The “future shot” module allows individ-
Please cite this article in press as: W.T Chai, et al., The design of remote discharge scenario management system on EAST, Fusion Eng. Des. (2016), http://dx.doi.org/10.1016/j.fusengdes.2016.04.015
G Model FUSION-8713; No. of Pages 6 4
ARTICLE IN PRESS W.T Chai et al. / Fusion Engineering and Design xxx (2016) xxx–xxx
Fig. 6. Initial implementation of the system (a)Home page (b)Unfold of advanced search.
ual users to set up parameters for a “future” shot and store the parameters setting information in form of PCS setup files in a PCS public directory area with a file name associated with the user and identifier (e.g.user vde 37992.wa10) [6]. This module is for preset scenarios only and is not used for discharging and testing, so the scenarios in this module only contain parameters setting information. The “next shot” module not only edit the next shot parameters directly (will stored as file called “Nextshot.wa10”), but also call PCS setup files that archived by “future shot” module or pcs east for
actual discharge or simulation test, after actual discharge or simulation test, the scenarios contain parameters setting information and experimental data and simulation data would store in pcs east. As shown in Fig. 2, the IDL user interface connects the PCS server thorough socket communication. After parameters are set up through the IDL user interface, the PCS will archive actual discharge parameters, experimental data and simulation data after discharge. Operators have access to these previous discharge and simulation parameters through the PCS public directories or pcs east. How-
Please cite this article in press as: W.T Chai, et al., The design of remote discharge scenario management system on EAST, Fusion Eng. Des. (2016), http://dx.doi.org/10.1016/j.fusengdes.2016.04.015
G Model FUSION-8713; No. of Pages 6
ARTICLE IN PRESS W.T Chai et al. / Fusion Engineering and Design xxx (2016) xxx–xxx
ever, as shown in Fig. 1, it is hard to obtain detail parameters setting information (e.g. IP, density, pulse length, discharge type, etc.) in PCS interface to optimize the next shot parameters based on the experimental data and simulation data. 3. System overview The architecture of proposed remote discharge scenarios management system is shown in Fig. 3, which is the extension function module of WebPCS [9]. The WebPCS is a web-based user interface for EAST PCS, which can acquire waveform information of specified scenario from RDSMS and make it display on its user interface through socket communication to EAST PCS. Instead of IDL user interface of previous PCS, the RDSMS is based on a web interface like WebPCS and it allows remote and local operators access to the system by a secure web browser interface. It connects the users using a Graphical User Interface (GUI) using standard HTTP protocol and shares the EAST PCS and MDSplus scenario files by means of Network File System (NFS). It contains five parts as shown in Fig. 3. The “prepared scenarios management” and “actual discharge scenarios management” is the extension of “future shot” and “next shot” concept; the “discharge schedule management”, “scenarios verification” and “user management” are new parts for selecting an optimal discharge schedule. The next chapter will introduce the detail design of these five parts. The GUI is implemented in languages HTML and CSS [7] and Javascript, jQuery and Ajax are used to optimize the interaction, operation and display on the web. Server side development is accomplished with PHP, which implements client-server communications. MySQL and Apache HTTP server provide database storage and web service, respectively. 4. The detailed design of remote discharge scenarios management system The workflow of RDSMS is shown in Fig. 4, in which the green boxes represent different modules of RDSMS. The following sections will describe these modules in detail. 4.1. User management Four levels of user privileges are available for system security: (1) Common user: this level is for basic PCS users who can set scenarios on “prepared scenario management” module and call scenarios from scenario database for simulation test. However, they cannot put information into system for actual discharge. (2) Scenario verification operator: the users in this level mainly verify discharge scenarios submitted by common users, so they should be experienced operators. Moreover, they can put in actual shot data for PCS operation. (3) Discharge schedule operator: the users in this level have right to formulate discharge schedule and submit the pending shot data for active operation of the PCS.
5
Table 1 Design of prepared scenario table. Field Name
Field Description
Comment
ID Title User IP Shape Density Pulse Heating Discharge type Description Adddate
Scenario ID Scenario Name UserName IP Value(KA) Plasma Shape Density Value(e19 /m3 ) Pulse length(s) Heating or not Discharge Type Scenario description Scenario Creation time
Primary Key Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null Allow Null Not Null
(4) Administrator: user administrators manage all other users and participate in development of the system. They manage all aspects of the PCS implementation at the local site including the permissions for each particular user. 4.2. Scenario verification In order to reject unexpected scenarios, the scenarios submitted by the common user must pass through both verification tests before being archived in the database. There are two types of verification, namely system verification and scenario verification. First, the system examines the legitimacy and rationality of all parameters automatically to eliminate abnormal parameters. Active page feedback is given to the user if parameters do not pass this verification test. Scenarios that pass the system verification test will enter approval status, and the scenario verification operator will verify the scenarios validity. 4.3. Prepared scenario management The prepared scenario management is an extension of “future shot” and manages the “future shot” scenario by database technology. The data flow of this module is shown in Fig. 4. After verification a common user submits the scenario through WebPCS and it is stored in the database according to specific categories. The database technology provides basic database manipulation such as scenario query and scenario deletion. In particular, the operator can query a scenario using some key words or plasma parameters and obtain more detail information. The design of a prepared scenario table is shown in Table 1. The table contains 12 fields with the primary key “ID” identifying a particular scenario. The “Title” is a scenario name created by the “User”. The “IP”, “Shape”, “Density”, “Pulse”, “Heating”, “Discharge type” are scenario parametric description. The “Description” field provides additional scenario information. The “Adddate” field is used to identify the scenario creation date. 4.4. Actual discharge scenario management The actual discharge scenario management is an extension of “next shot”. In the current EAST system, convenient data analysis
Table 2 Design of actual discharge scenario table. Field Name
Field Description
Comment
Shot num Scenario ID IP experiment Density experiment Pulse experiment Status Discharge time
Shot number Scenario ID Experimental data of IP(KA) Experimental data of Density (e19 /m3 ) Experimental data of Pulse length(s) Discharge status Discharge date
Primary Key Foreign Key of ID in prepared scenario table Not Null Not Null Not Null Not Null Not Null
Please cite this article in press as: W.T Chai, et al., The design of remote discharge scenario management system on EAST, Fusion Eng. Des. (2016), http://dx.doi.org/10.1016/j.fusengdes.2016.04.015
G Model FUSION-8713; No. of Pages 6
ARTICLE IN PRESS W.T Chai et al. / Fusion Engineering and Design xxx (2016) xxx–xxx
6
and visualization tools such as ReviewPlus, Logbook, jScope, WebScope [10–13] are available for physicists and engineering experts to view operational status and data from the device. In the same way, as show in Fig. 4, the setup parameters and experimental data are also extracted from MDSplus and archive in a scenario database for optimal scenario selection and for the purpose of scenario optimization and data query. The system compares these two parts and then decides the merits of scenario. Table 2 reports the actual discharge scenario table which contains experimental data, the “Scenario ID” will as foreign key of “ID” in prepared scenario table for setup parameters. The meaning of other field is the same with Table 1. 4.5. Discharge schedule management During EAST experimental discharge period, there are different discharge requirements, which demand discharge schedule management conveniently and a discharge schedule module is being developed to meet these requirements. Fig. 5 shows the interface design of this module, which formulates a discharge schedule according to the date. The “RESTORE” button will select scenarios from prepared scenarios or actual discharge scenarios to set up a discharge schedule directly. In addition, operators can set discharge parameters according to their requirements, the “optimize search” button will jump to scenario selection page and the system will provide several optimal scenarios from which the operator can choose. The interface provides a list of date based scenarios and basic database functions such as add, delete, update and query are available to the operator. 5. The preliminary constructing of website The present system is building on for use on the EAST website and the initial implementations shown in Fig. 6 [10]. The five parts of this system are distributed on the home page (Fig. 6(a)). The prepared scenario management, provides a common search function for quick search and also a means for advance search function (Fig. 6(b)) in which operator can search scenario for a range of parameters or for a combination of some conditions for a more complex search. In addition, the scenario list and basic database functions are provided for users to query, add, delete and update the scenario. Furthermore, detail information is available based on selection within certain scenario parameters. 6. Conclusion The RDSMS is being implemented for operation on EAST. The system provides PCS and data access for both local and remote users. It provides many useful functions for managing discharge scenarios and formulating the discharge schedule. Operators can use this system to formulate discharge schedule based on automatic generation of optimal scenarios.
In the future, we will combine with actual discharge data using data mining technology to acquire optimal configurations, and to generate an expert database for the guiding experiment. Acknowledgments This work is supported by the National Magnetic Confinement Fusion Research Program of China under Grant No. 2014GB103000, the National Nature Science Foundation of China with contract number 11205200, the External Cooperation Program of BIC, Chinese Academy of Sciences, Grant No. GJHZ201303. The authors would like to thank all of the colleagues of the Computer Application Division at the Institute of Plasma Physics, Chinese Academy of Sciences, for their contributions. References [1] O. Barana, R. Nouailletas, S. Brémond, P. Moreau, L. Allegretti, S. Balme, N. Ravenel, S. Mannori, B. Guillerminet, F. Leroux, D. Douai, E. Nardon, P. Hertout, F. Saint-Laurent, Conceptual design of a generic pulse schedule and event handling editor for improved fusion device operation, Fusion Eng. Des. 88 (2013) 1078–1081. [2] T. Yamamoto, I. Yonekawa, K. Ohta, H. Hosoyama, Y. Hashimoto, A. Wallander, A. Winter, T. Sugie, Y. Kusama, Y. Kawano, R. Yoshino, Designing a prototype of the ITER pulse scheduling system, Fusion Eng. Des. 87 (2012) 2016–2019. [3] G. Neu, A. Buhler, K. Engelhardt, J.C. Fuchs, O. Gruber, V. Mertens, G. Raupp, J. Schweinzer, W. Treutterer, D. Zasche, T. Zehetbauer, A.U. Team, Experiment planning and execution workflow at ASDEX Upgrade, Fusion Eng. Des. 86 (2011) 1072–1075. [4] T. Totsuka, Y. Suzuki, S. Sakata, T. Oshima, K. Iba, Web-based java application to advanced JT-60 man-machine interfacing system for remote experiments, Fusion Eng. Des. 83 (2008) 287–290. [5] B.J. Xiao, D.A. Humphreys, M.L. Walker, A. Hyatt, J.A. Leuer, D. Mueller, B.G. Penaflor, D.A. Pigrowski, R.D. Johnson, A. Welander, Q.P. Yuan, H.Z. Wang, J.R. Luo, Z.P. Luo, C.Y. Liu, L.Z. Liu, K. Zhang, EAST plasma control system, Fusion Eng. Des. 83 (2008) 181–187. [6] R.R. Zhang, The remote participation and data visualization of EAST plasma control system, in: PhD Dissertation of Institute of Plasma Physics, Chinese Academy of Sciences, 2013. [7] B.G. Penaflor, J.R. Ferron, M.L. Walker, D.A. Humphreys, J.A. Leuer, D.A. Piglowski, R.D. Johnson, B.J. Xiao, S.H. Hahn, D.A. Gates, Worldwide collaborative efforts in plasma control software development, Fusion Eng. Des. 83 (2008) 176–180. [8] M.W. John Ferron, Ben Penaflor, Bob Johnson, Application Programmer’s Guide to the Plasma Control System (preliminary draft), DIII-D documents, 2011. [9] R.R. Zhang, B.J. Xiao, Q.P. Yuan, F. Yang, Y. Zhang, R.D. Johnson, B.G. Penaflor, The web-based user interface for EAST plasma control system, Fusion Eng. Des. 89 (2014) 558–562. [10] J. Schachter, Q. Peng, D.P. Schissel, Data analysis software tools for enhanced collaboration at the DIII-D National Fusion Facility, Fusion Eng. Des. 48 (2000) 91–98. [11] F. Yang, B.J. Xiao, Web-based logbook system for EAST experiments, Plasma Sci. Technol. 12 (2010) 632–635. [12] G. Manduchi, C. Taliercio, A. Luchetta, The java interface of MDSplus: towards a unified approach for local and remote data access, Fusion Eng. Des. 48 (2000) 163–170. [13] F. Yang, N.N. Dang, B.J. Xiao, WebScope: a new tool for fusion data analysis and visualization, Plasma Sci. Technol. 12 (2010) 253–256.
Please cite this article in press as: W.T Chai, et al., The design of remote discharge scenario management system on EAST, Fusion Eng. Des. (2016), http://dx.doi.org/10.1016/j.fusengdes.2016.04.015
ARTICLE IN PRESS
FUSION-8713; No. of Pages 6
Fusion Engineering and Design xxx (2016) xxx–xxx
Contents lists available at ScienceDirect
Fusion Engineering and Design journal homepage: www.elsevier.com/locate/fusengdes
The design of remote discharge scenario management system on EAST W.T Chai a,b,∗ , B.J Xiao a,b , Q.P Yuan a , R.R. Zhang a a b
Institute of Plasma Physics, Chinese Academy of Sciences, Hefei, Anhui, PR China University of Science and Technology of China, Hefei, Anhui, PR China
h i g h l i g h t s • The remote discharge scenario management system is established on EAST, it provides some useful function for operators to manage discharge scenarios and formulate discharge schedule.
• Operators can use this system to formulate discharge schedule on account of it can electing optimal scenarios automatically. • The system is not only for local user but also for remote user. • In the future, we can combine with actual discharge data and data mining technology to acquire optimal configuration, which to generate expert database and guiding experiment.
a r t i c l e
i n f o
Article history: Received 19 June 2015 Received in revised form 26 February 2016 Accepted 8 April 2016 Available online xxx Keywords: PCS EAST Web Discharge scenario
a b s t r a c t The discharge scenarios on EAST plasma control system (PCS), characterized by different waveform parameters and different hardware requirements, will need a systematic discharge scenario management system for remote and local operators, in order to optimize storage structure and rationally manage discharge time. The remote management of discharge scenarios will require extending the functionalities of the present PCS “future shot” and “next shot” modules. Taking advantage of database technique, the operators can acquire detail information of all discharge scenarios directly without PCS user interface and search the specified scenarios by key words. In addition, the system can elect optimal scenarios automatically based on discharge schedule and plasma pulse setting for later artificial selection. To this purpose, a new remote discharge scenario management system (RDSMS) basis for Web is being conceived on EAST. The system contains a database with functions of “user management”, “scenario verification”, “prepared scenario management”, “actual discharge scenario management” and “discharge schedule management”. This paper will present the relevant conceptual design and give an account of the test results for implementation on EAST discharges. © 2016 Elsevier B.V. All rights reserved.
1. Introduction Coping with multiple discharge scenarios in an efficient way is an important issue in plasma operation, some previous design or application has being conceived on some tokmaks such as Tore Supra [1], ITER [2], ASDEX [3], JT-60 [4] for improved device operation. This paper reports conceptual design of EAST RDSMS. After several years of development, EAST has become very complex device, containing a number of sophisticated sub-systems that demand complex operator programming for control during a discharge. Improper programming can lead to unwanted abnor-
∗ Corresponding author at: Institute of Plasma Physics, Chinese Academy of Sciences, Hefei, Anhui, PR China E-mail address: [email protected] (W.T Chai).
malities or shot abort during a discharge. At present, EAST operators manage discharge scenarios using the plasma control system, which was adapted from DIII-D [5]. EAST PCS saves future shot parameters setting information in form of PCS setup files (which are named in suffix by .wa10) for use in discharge execution and archives the actual discharge shot parameters setting information in PCSSETUP nodes of MDSplus tree named pcs east during the discharge [6], However, although EAST operators can call and retrieve these parameters through filename, user name or shot number (Fig. 1), there is no way to obtain more detail information on these parameters. An improvement in the retrieval functions is the object of this paper. In order to manage discharge scenarios efficiently and conveniently, a remote discharge scenarios management system based on Web input is presented in this paper. The system takes advantage of database technology to implement the functions of scenario
http://dx.doi.org/10.1016/j.fusengdes.2016.04.015 0920-3796/© 2016 Elsevier B.V. All rights reserved.
Please cite this article in press as: W.T Chai, et al., The design of remote discharge scenario management system on EAST, Fusion Eng. Des. (2016), http://dx.doi.org/10.1016/j.fusengdes.2016.04.015
G Model FUSION-8713; No. of Pages 6 2
ARTICLE IN PRESS W.T Chai et al. / Fusion Engineering and Design xxx (2016) xxx–xxx
Fig. 1. Discharge scenario calling and retrieval in EAST PCS.
Fig. 2. The existing scenario management on EAST.
Fig. 3. System architecture of RDSMS.
verification, scenario classification, scenario query, scenario calling and actual discharge scenario. Furthermore, the operator can use
this system to formulate a discharge schedule based on an automatically generated optimal scenario.
Please cite this article in press as: W.T Chai, et al., The design of remote discharge scenario management system on EAST, Fusion Eng. Des. (2016), http://dx.doi.org/10.1016/j.fusengdes.2016.04.015
G Model FUSION-8713; No. of Pages 6
ARTICLE IN PRESS W.T Chai et al. / Fusion Engineering and Design xxx (2016) xxx–xxx
3
Fig. 4. The workflow of RDSMS.
Fig. 5. Interface design of discharge schedule management.
2. Existing scenario management on EAST EAST PCS is a PC cluster with four nodes (one host node and three real-time nodes) [5]. An IDL user interface is provided for
users to input discharge parameters [7] and contains three control modules respectively called “future shot”, “next shot” and “shared shot” [8], among these, “future shot” and “next shot” related to scenario management. The “future shot” module allows individ-
Please cite this article in press as: W.T Chai, et al., The design of remote discharge scenario management system on EAST, Fusion Eng. Des. (2016), http://dx.doi.org/10.1016/j.fusengdes.2016.04.015
G Model FUSION-8713; No. of Pages 6 4
ARTICLE IN PRESS W.T Chai et al. / Fusion Engineering and Design xxx (2016) xxx–xxx
Fig. 6. Initial implementation of the system (a)Home page (b)Unfold of advanced search.
ual users to set up parameters for a “future” shot and store the parameters setting information in form of PCS setup files in a PCS public directory area with a file name associated with the user and identifier (e.g.user vde 37992.wa10) [6]. This module is for preset scenarios only and is not used for discharging and testing, so the scenarios in this module only contain parameters setting information. The “next shot” module not only edit the next shot parameters directly (will stored as file called “Nextshot.wa10”), but also call PCS setup files that archived by “future shot” module or pcs east for
actual discharge or simulation test, after actual discharge or simulation test, the scenarios contain parameters setting information and experimental data and simulation data would store in pcs east. As shown in Fig. 2, the IDL user interface connects the PCS server thorough socket communication. After parameters are set up through the IDL user interface, the PCS will archive actual discharge parameters, experimental data and simulation data after discharge. Operators have access to these previous discharge and simulation parameters through the PCS public directories or pcs east. How-
Please cite this article in press as: W.T Chai, et al., The design of remote discharge scenario management system on EAST, Fusion Eng. Des. (2016), http://dx.doi.org/10.1016/j.fusengdes.2016.04.015
G Model FUSION-8713; No. of Pages 6
ARTICLE IN PRESS W.T Chai et al. / Fusion Engineering and Design xxx (2016) xxx–xxx
ever, as shown in Fig. 1, it is hard to obtain detail parameters setting information (e.g. IP, density, pulse length, discharge type, etc.) in PCS interface to optimize the next shot parameters based on the experimental data and simulation data. 3. System overview The architecture of proposed remote discharge scenarios management system is shown in Fig. 3, which is the extension function module of WebPCS [9]. The WebPCS is a web-based user interface for EAST PCS, which can acquire waveform information of specified scenario from RDSMS and make it display on its user interface through socket communication to EAST PCS. Instead of IDL user interface of previous PCS, the RDSMS is based on a web interface like WebPCS and it allows remote and local operators access to the system by a secure web browser interface. It connects the users using a Graphical User Interface (GUI) using standard HTTP protocol and shares the EAST PCS and MDSplus scenario files by means of Network File System (NFS). It contains five parts as shown in Fig. 3. The “prepared scenarios management” and “actual discharge scenarios management” is the extension of “future shot” and “next shot” concept; the “discharge schedule management”, “scenarios verification” and “user management” are new parts for selecting an optimal discharge schedule. The next chapter will introduce the detail design of these five parts. The GUI is implemented in languages HTML and CSS [7] and Javascript, jQuery and Ajax are used to optimize the interaction, operation and display on the web. Server side development is accomplished with PHP, which implements client-server communications. MySQL and Apache HTTP server provide database storage and web service, respectively. 4. The detailed design of remote discharge scenarios management system The workflow of RDSMS is shown in Fig. 4, in which the green boxes represent different modules of RDSMS. The following sections will describe these modules in detail. 4.1. User management Four levels of user privileges are available for system security: (1) Common user: this level is for basic PCS users who can set scenarios on “prepared scenario management” module and call scenarios from scenario database for simulation test. However, they cannot put information into system for actual discharge. (2) Scenario verification operator: the users in this level mainly verify discharge scenarios submitted by common users, so they should be experienced operators. Moreover, they can put in actual shot data for PCS operation. (3) Discharge schedule operator: the users in this level have right to formulate discharge schedule and submit the pending shot data for active operation of the PCS.
5
Table 1 Design of prepared scenario table. Field Name
Field Description
Comment
ID Title User IP Shape Density Pulse Heating Discharge type Description Adddate
Scenario ID Scenario Name UserName IP Value(KA) Plasma Shape Density Value(e19 /m3 ) Pulse length(s) Heating or not Discharge Type Scenario description Scenario Creation time
Primary Key Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null Allow Null Not Null
(4) Administrator: user administrators manage all other users and participate in development of the system. They manage all aspects of the PCS implementation at the local site including the permissions for each particular user. 4.2. Scenario verification In order to reject unexpected scenarios, the scenarios submitted by the common user must pass through both verification tests before being archived in the database. There are two types of verification, namely system verification and scenario verification. First, the system examines the legitimacy and rationality of all parameters automatically to eliminate abnormal parameters. Active page feedback is given to the user if parameters do not pass this verification test. Scenarios that pass the system verification test will enter approval status, and the scenario verification operator will verify the scenarios validity. 4.3. Prepared scenario management The prepared scenario management is an extension of “future shot” and manages the “future shot” scenario by database technology. The data flow of this module is shown in Fig. 4. After verification a common user submits the scenario through WebPCS and it is stored in the database according to specific categories. The database technology provides basic database manipulation such as scenario query and scenario deletion. In particular, the operator can query a scenario using some key words or plasma parameters and obtain more detail information. The design of a prepared scenario table is shown in Table 1. The table contains 12 fields with the primary key “ID” identifying a particular scenario. The “Title” is a scenario name created by the “User”. The “IP”, “Shape”, “Density”, “Pulse”, “Heating”, “Discharge type” are scenario parametric description. The “Description” field provides additional scenario information. The “Adddate” field is used to identify the scenario creation date. 4.4. Actual discharge scenario management The actual discharge scenario management is an extension of “next shot”. In the current EAST system, convenient data analysis
Table 2 Design of actual discharge scenario table. Field Name
Field Description
Comment
Shot num Scenario ID IP experiment Density experiment Pulse experiment Status Discharge time
Shot number Scenario ID Experimental data of IP(KA) Experimental data of Density (e19 /m3 ) Experimental data of Pulse length(s) Discharge status Discharge date
Primary Key Foreign Key of ID in prepared scenario table Not Null Not Null Not Null Not Null Not Null
Please cite this article in press as: W.T Chai, et al., The design of remote discharge scenario management system on EAST, Fusion Eng. Des. (2016), http://dx.doi.org/10.1016/j.fusengdes.2016.04.015
G Model FUSION-8713; No. of Pages 6
ARTICLE IN PRESS W.T Chai et al. / Fusion Engineering and Design xxx (2016) xxx–xxx
6
and visualization tools such as ReviewPlus, Logbook, jScope, WebScope [10–13] are available for physicists and engineering experts to view operational status and data from the device. In the same way, as show in Fig. 4, the setup parameters and experimental data are also extracted from MDSplus and archive in a scenario database for optimal scenario selection and for the purpose of scenario optimization and data query. The system compares these two parts and then decides the merits of scenario. Table 2 reports the actual discharge scenario table which contains experimental data, the “Scenario ID” will as foreign key of “ID” in prepared scenario table for setup parameters. The meaning of other field is the same with Table 1. 4.5. Discharge schedule management During EAST experimental discharge period, there are different discharge requirements, which demand discharge schedule management conveniently and a discharge schedule module is being developed to meet these requirements. Fig. 5 shows the interface design of this module, which formulates a discharge schedule according to the date. The “RESTORE” button will select scenarios from prepared scenarios or actual discharge scenarios to set up a discharge schedule directly. In addition, operators can set discharge parameters according to their requirements, the “optimize search” button will jump to scenario selection page and the system will provide several optimal scenarios from which the operator can choose. The interface provides a list of date based scenarios and basic database functions such as add, delete, update and query are available to the operator. 5. The preliminary constructing of website The present system is building on for use on the EAST website and the initial implementations shown in Fig. 6 [10]. The five parts of this system are distributed on the home page (Fig. 6(a)). The prepared scenario management, provides a common search function for quick search and also a means for advance search function (Fig. 6(b)) in which operator can search scenario for a range of parameters or for a combination of some conditions for a more complex search. In addition, the scenario list and basic database functions are provided for users to query, add, delete and update the scenario. Furthermore, detail information is available based on selection within certain scenario parameters. 6. Conclusion The RDSMS is being implemented for operation on EAST. The system provides PCS and data access for both local and remote users. It provides many useful functions for managing discharge scenarios and formulating the discharge schedule. Operators can use this system to formulate discharge schedule based on automatic generation of optimal scenarios.
In the future, we will combine with actual discharge data using data mining technology to acquire optimal configurations, and to generate an expert database for the guiding experiment. Acknowledgments This work is supported by the National Magnetic Confinement Fusion Research Program of China under Grant No. 2014GB103000, the National Nature Science Foundation of China with contract number 11205200, the External Cooperation Program of BIC, Chinese Academy of Sciences, Grant No. GJHZ201303. The authors would like to thank all of the colleagues of the Computer Application Division at the Institute of Plasma Physics, Chinese Academy of Sciences, for their contributions. References [1] O. Barana, R. Nouailletas, S. Brémond, P. Moreau, L. Allegretti, S. Balme, N. Ravenel, S. Mannori, B. Guillerminet, F. Leroux, D. Douai, E. Nardon, P. Hertout, F. Saint-Laurent, Conceptual design of a generic pulse schedule and event handling editor for improved fusion device operation, Fusion Eng. Des. 88 (2013) 1078–1081. [2] T. Yamamoto, I. Yonekawa, K. Ohta, H. Hosoyama, Y. Hashimoto, A. Wallander, A. Winter, T. Sugie, Y. Kusama, Y. Kawano, R. Yoshino, Designing a prototype of the ITER pulse scheduling system, Fusion Eng. Des. 87 (2012) 2016–2019. [3] G. Neu, A. Buhler, K. Engelhardt, J.C. Fuchs, O. Gruber, V. Mertens, G. Raupp, J. Schweinzer, W. Treutterer, D. Zasche, T. Zehetbauer, A.U. Team, Experiment planning and execution workflow at ASDEX Upgrade, Fusion Eng. Des. 86 (2011) 1072–1075. [4] T. Totsuka, Y. Suzuki, S. Sakata, T. Oshima, K. Iba, Web-based java application to advanced JT-60 man-machine interfacing system for remote experiments, Fusion Eng. Des. 83 (2008) 287–290. [5] B.J. Xiao, D.A. Humphreys, M.L. Walker, A. Hyatt, J.A. Leuer, D. Mueller, B.G. Penaflor, D.A. Pigrowski, R.D. Johnson, A. Welander, Q.P. Yuan, H.Z. Wang, J.R. Luo, Z.P. Luo, C.Y. Liu, L.Z. Liu, K. Zhang, EAST plasma control system, Fusion Eng. Des. 83 (2008) 181–187. [6] R.R. Zhang, The remote participation and data visualization of EAST plasma control system, in: PhD Dissertation of Institute of Plasma Physics, Chinese Academy of Sciences, 2013. [7] B.G. Penaflor, J.R. Ferron, M.L. Walker, D.A. Humphreys, J.A. Leuer, D.A. Piglowski, R.D. Johnson, B.J. Xiao, S.H. Hahn, D.A. Gates, Worldwide collaborative efforts in plasma control software development, Fusion Eng. Des. 83 (2008) 176–180. [8] M.W. John Ferron, Ben Penaflor, Bob Johnson, Application Programmer’s Guide to the Plasma Control System (preliminary draft), DIII-D documents, 2011. [9] R.R. Zhang, B.J. Xiao, Q.P. Yuan, F. Yang, Y. Zhang, R.D. Johnson, B.G. Penaflor, The web-based user interface for EAST plasma control system, Fusion Eng. Des. 89 (2014) 558–562. [10] J. Schachter, Q. Peng, D.P. Schissel, Data analysis software tools for enhanced collaboration at the DIII-D National Fusion Facility, Fusion Eng. Des. 48 (2000) 91–98. [11] F. Yang, B.J. Xiao, Web-based logbook system for EAST experiments, Plasma Sci. Technol. 12 (2010) 632–635. [12] G. Manduchi, C. Taliercio, A. Luchetta, The java interface of MDSplus: towards a unified approach for local and remote data access, Fusion Eng. Des. 48 (2000) 163–170. [13] F. Yang, N.N. Dang, B.J. Xiao, WebScope: a new tool for fusion data analysis and visualization, Plasma Sci. Technol. 12 (2010) 253–256.
Please cite this article in press as: W.T Chai, et al., The design of remote discharge scenario management system on EAST, Fusion Eng. Des. (2016), http://dx.doi.org/10.1016/j.fusengdes.2016.04.015