Serious accident data visualization method and system for nuclear power plant

Abstract

The invention discloses a nuclear power plant serious accident data visualization method and system, and the method comprises the steps: enabling a rear-end simulator to be in communication connection with a rear-end first server, enabling the rear-end simulator to transmit the data of a simulation result to the rear-end first server, enabling the rear-end first server to be in communication connection with a rear-end database, and enabling the rear-end database to be in communication connection with the rear-end simulator; the back-end first server caches the data to a back-end database, the back-end database is in communication connection with a back-end second server, the back-end second server reads the data from the back-end database for processing, and the back-end second server is in communication connection with front-end visual software running in the web browser. And the rear-end second server sends the processed data to front-end visual software, and the front-end visual software displays a simulation result of the rear-end simulator in a web browser. Compared with the prior art, the method has the advantages that the use of the software is realized through the browser, the installation and maintenance process is simplified, and a user can use the software on other equipment through the browser only by deploying the back-end server.

Description

Technical Field

[0001] The present invention relates to the field of visualization software technology, and in particular to a method and system for visualization of severe accident data in a nuclear power plant. Background Art

[0002] In the existing technology, the severe accident visualization software adopts the C / S architecture, that is, the client-server architecture. These software are usually developed using Unity and run on a single PC platform, and data is transmitted through TCP-based Socket communication technology. The simulator sends data to the TCP server, and the server is responsible for distribution after receiving the data. The data bridge connects the visualization software and the TCP server, receives and processes the distributed data, and then sends it to the visualization software for display. Among them, the TCP server and the data bridge are both exe executable files developed in C++. In addition, this product structure or technology has several shortcomings, mainly manifested in: the software can only run locally on a single machine, resulting in the need to install them separately when multiple computers are used; each software update must be operated on each computer; there are high requirements for computer hardware configuration; and after the data items in the external Json configuration file are changed, the software cannot be updated immediately and must be restarted to take effect. Summary of the invention

[0003] The technical problem to be solved by the present invention is to provide a method and system for visualizing severe accident data of a nuclear power plant in view of at least one defect of the related technology mentioned in the above background technology: the software needs to be installed locally and has high requirements on hardware.

[0004] The technical solution adopted by the present invention to solve the technical problem is: constructing a method for visualizing severe accident data of a nuclear power plant, comprising the following steps:

[0005] The back-end simulator is connected to the back-end first server for communication, and the back-end simulator sends the simulation result data to the back-end first server;

[0006] The first backend server is connected to the backend database for communication, and the first backend server caches the data in the backend database;

[0007] The back-end database is connected to the back-end second server for communication, and the back-end second server reads data from the back-end database for processing;

[0008] The back-end second server is connected to the front-end visualization software running in the web browser, and the back-end second server sends the processed data to the front-end visualization software, and the front-end visualization software displays the simulation results of the back-end simulator in the web browser.

[0009] In some embodiments, the method for visualizing severe accident data of a nuclear power plant further includes: the front-end visualization software sends instructions to the back-end second server to switch the state of the back-end second server, and the state of the back-end second server includes running state, pause state, recording state and playback state.

[0010] In some embodiments, the front-end visualization software sends an instruction to the back-end second server to switch the state of the back-end second server to a recording state, including:

[0011] The front-end visualization software sends a recording instruction to the back-end second server. The back-end second server checks whether the folder used to store the recorded data file exists according to the recording instruction. If not, the back-end second server automatically creates a folder and checks whether the current state is a recording state. If so, the back-end second server collects all current data in real time, generates a recorded data file, and stores it in the folder.

[0012] In some embodiments, the front-end visualization software sends an instruction to the back-end second server to switch the state of the back-end second server to the playback state, including:

[0013] The front-end visualization software sends a playback instruction to the back-end second server. The back-end second server reads the data saved in the folder according to the instruction and sends the data to the front-end visualization software according to the current speed. If it is played normally, each piece of data is sent; if it is played at double speed, the data is sent according to the speed interval.

[0014] In some embodiments, the front-end visualization software sends an instruction to the back-end second server to switch the state of the back-end second server to the playback state, and also includes: in the playback state, the front-end visualization software sends time parameters to the back-end second server according to the position of the progress bar dragged or the input time point, and the back-end second server fast-forwards to the position or time point at the maximum playback speed according to the time parameters and then resumes normal playback.

[0015] In some embodiments, the front-end visualization software sends instructions to the back-end second server to switch the state of the back-end second server to the playback state, and also includes: in the playback state, the back-end second server pauses playback according to the instructions of the front-end visualization software.

[0016] In some embodiments, the front-end visualization software sends instructions to the back-end second server to switch the state of the back-end second server to the playback state, and also includes: in the playback state, the back-end second server exits the playback according to the instructions of the front-end visualization software.

[0017] In some embodiments, data communication between the backend second server and the frontend visualization software is transmitted in a data frame, and the data frame includes a header and a body; the header includes the information type and the current state of the backend second server.

[0018] In some embodiments, the back-end simulator sends data to the back-end first server, which includes: the simulation software of the back-end simulator simulates the nuclear power accident scenario according to a preset nuclear power system model to obtain the data required for visual display.

[0019] The present invention provides a nuclear power plant severe accident data visualization system, comprising a back-end simulator for implementing any of the above-mentioned nuclear power plant severe accident data visualization methods, a back-end first server, a back-end database, a back-end second server and a front-end visualization software running in a web browser.

[0020] By implementing the present invention, the following beneficial effects are achieved:

[0021] The present invention provides a method and system for visualizing severe accident data of a nuclear power plant, wherein a back-end simulator is connected in communication with a first back-end server, the back-end simulator sends data of simulation results to the first back-end server, the first back-end server is connected in communication with a back-end database, the first back-end server caches data to the back-end database, the back-end database is connected in communication with a second back-end server, the second back-end server reads data from the back-end database for processing, the second back-end server is connected in communication with a front-end visualization software running in a web browser, the second back-end server sends processed data to the front-end visualization software, and the front-end visualization software displays the simulation results of the back-end simulator in the web browser. Compared with the prior art, the present invention realizes the use of software through a browser, simplifies the installation and maintenance process, and only requires the back-end server to be deployed, and the user can use the software through a browser on other devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:

[0023] Figure 1 A schematic diagram of a front-end and back-end communication scheme in an embodiment of a method for visualizing severe accident data of a nuclear power plant according to the present invention is shown;

[0024] Figure 2 A schematic diagram of the front-end and back-end communication data formats in an embodiment of a method for visualizing severe accident data of a nuclear power plant according to the present invention is shown;

[0025] Figure 3 A recording flow chart of an embodiment of a method for visualizing severe accident data of a nuclear power plant according to the present invention is shown;

[0026] Figure 4 A playback flow chart of an embodiment of a method for visualizing severe accident data of a nuclear power plant according to the present invention is shown;

[0027] Figure 5A flowchart of dragging a progress bar in an embodiment of a method for visualizing severe accident data of a nuclear power plant according to the present invention is shown;

[0028] Figure 6 A front-end interface effect diagram of an embodiment of a method for visualizing severe accident data of a nuclear power plant according to the present invention is shown. DETAILED DESCRIPTION

[0029] In order to have a clearer understanding of the technical features, purposes and effects of the present invention, specific embodiments of the present invention are now described in detail with reference to the accompanying drawings.

[0030] It should be noted that the flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor do they have to be executed in the order described. For example, some operations / steps can be decomposed, while some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0031] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0032] Some embodiments of the present invention disclose a method for visualizing severe accident data of a nuclear power plant, such as Figure 1 As shown, the following steps are included:

[0033] The back-end simulator is connected to the back-end first server for communication, and the back-end simulator sends the simulation result data to the back-end first server;

[0034] The first backend server is connected to the backend database for communication, and the first backend server caches the data in the backend database;

[0035] The back-end database is connected to the back-end second server for communication, and the back-end second server reads data from the back-end database for processing;

[0036] The back-end second server is connected to the front-end visualization software running in the web browser, and the back-end second server sends the processed data to the front-end visualization software, and the front-end visualization software displays the simulation results of the back-end simulator in the web browser.

[0037] In some embodiments, a communication connection refers to a communication path established between devices, allowing the devices to transfer data to each other.

[0038] In some embodiments, the front end is responsible for the parts that users can see and interact with, while the back end is responsible for processing data and business logic.

[0039] In some embodiments, the back-end simulator sends data to the back-end first server, which includes: the simulation software of the back-end simulator simulates the nuclear power accident scenario according to a preset nuclear power system model to obtain the data required for visual display.

[0040] In some embodiments, the first backend server is a TCP (Transmission Control Protocol) server, the backend database is a Redis (Remote Dictionary Server) database, and the second backend server is a WebSocket server. During the data transmission process, the simulator first sends data to the first backend server (TCP server), and the first backend server (TCP server) temporarily stores the data in the backend database (Redis database) after receiving the data. Subsequently, the second backend server (WebSocket server) extracts the data from the backend database (Redis database), performs necessary processing, and finally transmits the data to the visualization software for display.

[0041] For example: the simulation software on the back-end simulator can simulate the nuclear power accident scenario according to the preset nuclear power system model, and provide the required data for visualization. These data are packaged into a float array and sent to the back-end first server (TCP server). The back-end first server (TCP server) establishes a connection with the simulator, receives these data and caches them in the back-end database (Redis database). The back-end database (Redis database) is responsible for storing these data so that the back-end second server (WebSocket server) can read them. Subsequently, the back-end second server (WebSocket server) extracts data from the back-end database (Redis database) and sends it to the front-end visualization software to realize real-time display of the data. This process ensures efficient data flow from simulation to display. It should be noted here that the back-end database (Redis database) is necessary in the system. Although the back-end first server (TCP server) and the back-end second server (WebSocket server) can communicate directly, data packet loss is found in the communication test. In order to solve this problem, the back-end database (Redis database) is introduced to store data to ensure the stability and integrity of data transmission. In this way, the data is first cached in the backend database (Redis database), and then the backend second server (WebSocket server) reads the data from the backend database (Redis database), thereby avoiding the data loss problem that may be caused by direct communication.

[0042] In some embodiments, data communication between the backend second server and the frontend visualization software is transmitted in a data frame, the data frame includes a header and a body, the header includes the information type and the current state of the backend second server.

[0043] For example, the data communication between the back-end second server and the front-end visualization software is carried out in the form of binary byte stream data frames, such as Figure 2 As shown, each data frame consists of two parts: a header and a body. The header contains two 4-byte UInt32 (Unsigned 32-bit Integer) type data, of which the first four bytes are used to identify the type of information, such as status type, normal play data, and playback signal; the following four bytes indicate the current status of the back-end second server, including running status, paused status, recording status, and playback status. Such a structural design enables the data frame to clearly convey the information type and server status, ensuring the accuracy and efficiency of front-end and back-end communication. The two 4-byte UInt32 type data, status type, normal play data, playback signal, running status, paused status, recording status, and playback status here are only examples and are not intended to be limiting of this application.

[0044] In some embodiments, the method for visualizing severe accident data of a nuclear power plant also includes: the front-end visualization software sends instructions to the back-end second server to switch the state of the back-end second server, and the state of the back-end second server includes running state, pause state, recording state and playback state.

[0045] In some embodiments, the front-end visualization software sends an instruction to the back-end second server to switch the state of the back-end second server to a recording state, including: the front-end visualization software sends a recording instruction to the back-end second server, and the back-end second server checks whether a folder for storing recording data files exists according to the recording instruction. If not, the back-end second server automatically creates a folder and checks whether the current state is a recording state. If so, the back-end second server collects all current data in real time, generates a recording data file, and stores it in the folder.

[0046] For example: after the recording function is started in the visualization interface, the front-end visualization software will send a command to start recording to the back-end second server (WebSocket server) and switch its own state to the recording state. When the front-end visualization software sends a command to stop recording to the back-end second server (WebSocket server), the back-end second server (WebSocket server) terminates the recording process. Figure 3As shown, when the second back-end server (WebSocket server) is started, it will check whether there is a local path for storing the recorded data file; if the path already exists, the server will prompt that the folder already exists; if the path does not exist, the second back-end server (WebSocket server) will automatically create a new folder specifically for storing the recorded data file. During the recording process, the second back-end server (WebSocket server) will check every second whether it is currently in the recording state. If so, all data will be collected in real time, and data will be written every four bytes, and finally a .dat format file will be generated, which will be saved in a pre-set local path. This process ensures the flexibility of the recording function and the orderliness of data storage. The .dat format here is only an example and is not intended to be a limitation of this application.

[0047] In some embodiments, the front-end visualization software sends an instruction to the back-end second server to switch the state of the back-end second server to the playback state, including: the front-end visualization software sends a playback instruction to the back-end second server, the back-end second server reads the data saved in the folder according to the instruction, and sends the data to the front-end visualization software according to the current speed. If it is played normally, each piece of data is sent; if it is played at double speed, the data is sent according to the speed interval.

[0048] For example: after selecting a data file in the visualization interface and starting playback, the front-end visualization software will send a playback instruction to the back-end second server (WebSocket server) and then enter the playback state. Figure 4 As shown, after receiving the playback instruction, the back-end second server (WebSocket server) will read the data stored in the corresponding .dat file according to the provided file name, and each reading will be in units of 4 bytes, and the data items in the point table will be read in a group. Subsequently, the back-end second server (WebSocket server) will send data according to the current speed setting, and the maximum playback speed supported is 128 times the speed. Under normal playback speed, the back-end second server (WebSocket server) will send each data one by one; and when playing at a speed, the back-end second server (WebSocket server) will send data according to the speed interval, for example, when playing at 128 times the speed, every 128 data will be sent once, but the frequency of sending data will remain unchanged. The front-end visualization software will be displayed in real time after receiving the data, and during the playback process, the back-end second server (WebSocket server) will no longer send and display data from the back-end simulator. This process ensures the smoothness of playback and the accuracy of data, and allows users to select different playback speeds as needed. The 4 bytes, .dat files and 128 times the speed here are only examples and are not intended to limit this application.

[0049] In some embodiments, the front-end visualization software sends an instruction to the back-end second server to switch the state of the back-end second server to the playback state, and also includes: in the playback state, the front-end visualization software sends time parameters to the back-end second server according to the position of the progress bar dragged or the input time point, and the back-end second server fast-forwards to the position or time point at the maximum playback speed according to the time parameters and then resumes normal playback.

[0050] For example: Figure 5 As shown in the figure, in the playback state, the front-end visualization software captures the time parameter according to the position of the progress bar on the user interface and sends this parameter to the back-end second server (WebSocket server). After receiving the time parameter, the back-end second server (WebSocket server) will quickly locate the corresponding time point at the maximum playback speed, then resume the normal playback speed and continue to send data in real time. If you choose to enter a time point, the server will quickly jump and continue playback according to the input time parameter. This function allows users to flexibly control the playback progress and provides a more personalized viewing experience.

[0051] In some embodiments, the front-end visualization software sends instructions to the back-end second server to switch the state of the back-end second server to the playback state, and also includes: in the playback state, the back-end second server pauses playback according to the instructions of the front-end visualization software.

[0052] In some embodiments, the front-end visualization software sends instructions to the back-end second server to switch the state of the back-end second server to the playback state, and also includes: in the playback state, the back-end second server exits the playback according to the instructions of the front-end visualization software.

[0053] The present invention provides a nuclear power plant severe accident data visualization system, comprising a back-end simulator for implementing a nuclear power plant severe accident data visualization method as described in any of the above embodiments, a back-end first server, a back-end database, a back-end second server, and a front-end visualization software running in a web browser.

[0054] The following is a specific embodiment of the present invention:

[0055] The present invention includes front-end technology, back-end technology and deployment technology.

[0056] The front-end technologies are as follows:

[0057] In order to cope with the large-scale real-time data update of the Web front end, the visualization software was reconstructed and a cache strategy was implemented. The software was developed based on the Unity WebGL technology platform because Unity's WebGL project option allows Unity content to be published as a JavaScript program, using HTML5 (HyperText Markup Language 5) technology and WebGL rendering API (Application Programming Interface) to run in a web browser. The front-end visualization software effect is as follows: Figure 6 shown.

[0058] When migrating Unity's PC platform Shader to the WebGL platform, the syntax and functions of the Shader need to be adjusted to adapt to the limitations and differences of the WebGL platform. At the same time, the WebGL platform also has limited support for material properties, and the original material properties need to be checked and modified to meet the requirements of the WebGL platform.

[0059] There are also differences between WebGL and PC platforms in terms of file I / O stream reading. The browser environment of the WebGL platform restricts direct file read and write operations, so conventional file I / O classes cannot be used. On the WebGL platform, the WWW class is usually used for network requests and file loading operations. These classes load and send data through HTTP (HyperText Transfer Protocol) or HTTPS (HTTP Secure, secure hypertext transfer protocol) protocols, allowing files to be loaded from the server, network requests to be sent, and files to be downloaded and uploaded.

[0060] In addition, the UnityWebRequest class can implement networking functions in WebGL. Unity uses the browser to process web requests through the JavaScriptFetch API, but in this case, security restrictions are imposed on accessing cross-domain resources. Therefore, in order to access cross-domain web resources in WebGL, the server needs to authorize these resources using Cross-Origin Resource Sharing (CORS).

[0061] Backend technology includes communication schemes, data formats, and data processing, as follows:

[0062] Communication solution: The visualization software adopts B / S architecture (browser / server architecture). This architecture only requires the installation and maintenance of one server, and the client runs the software through the browser. It has the advantages of strong distribution, easy maintenance, simple development, strong sharing and low overall cost. The software uses the WebSocket protocol to achieve real-time data communication and display. This is a low-latency, full-duplex and long-term network protocol based on TCP. It simplifies the data exchange between the client and the server and allows the server to actively push data. The WebSocket API enables the browser and the server to create a persistent connection and perform two-way data transmission after completing a handshake. In order to realize the function of the back-end second server (WebSocket server), Node.js is selected as the operating environment, and the back-end database (Redis database) is combined to cache the data to improve the data reading efficiency. The back-end database (Redis database) provides faster reading and writing speeds and higher performance with its memory storage characteristics. When recording data, the front-end visualization software Unity sends recording instructions to the back-end second server (WebSocket server), and the server obtains data from the back-end database (Redis database) every second and writes it locally. When playing back the data, the back-end second server (WebSocket server) reads the .dat format data file from the local computer and sends the data at the current speed. This technology selection and architecture design ensures the software's advantages in data real-time, accuracy and performance.

[0063] Data format: Data communication between the front-end and back-end is carried out in the form of binary byte stream data frames, where each data frame consists of two parts: header and body. As shown in Table 1, the type of information recorded in the header determines the specific content of the body, so that the data frame can carry corresponding data according to different types of information.

[0064] Table 1 Correspondence between information types and subject contents

[0065]

[0066] Data processing: When performing visual playback in Web mode, due to the huge amount of data, it may cause data pressure on the system, resulting in data disorder and cache breakdown problems. In order to alleviate these problems, the data pressure can be reduced by optimizing the writing and reading methods during data recording and playback. Due to the limitations of the browser and Unity editor version, cache breakdown may occur when processing large amounts of data, which can be avoided as much as possible by upgrading the Unity editor version and expanding the browser cache. In addition, other measures can be taken to reduce data pressure in Web mode, such as using asynchronous resource loading, using XMLHttpRequest or fetch API to avoid main thread jams; compressing images, CSS and JavaScript files to reduce resource loading time and improve performance; and preloading necessary resources when the page is loaded, by using tags or JavaScript to preload resources and reduce subsequent loading waiting time. These methods work together to effectively improve the performance and stability of visual playback in Web mode. The method of reducing data pressure here is only an example and is not intended to be a limitation of this application.

[0067] Deployment techniques include single device access, multi-device LAN access, and software updates, as follows:

[0068] Single device access: First, you need to prepare a computer and install Redis and Node.js on it. Then, copy the server folder and the Web package folder to this computer. The startup process starts with running the first back-end server (TCP server) (serv.exe), then starting the simulator program to establish a connection with the first back-end server (TCP server), and finally starting the second back-end server (WebSocket server), where the first back-end server (TCP server) requires the support of Redis, and the second back-end server (WebSocket server) requires the support of Redis and Node.js. After completing these steps, run HTML5LaunchHelper.exe in the Web package folder, which will provide a local address http: / / localhost:8000 / . Finally, access this address in the Edge browser and click the index.html file to start local access. The Edge browser is selected here for example only and is not intended to be a limitation of this application.

[0069] LAN access for multiple devices: First, you need to prepare several computers, one of which is used as the main server. Run the backend first server, backend database, and backend second server on the device for local access. On the main server, you need to install Java and Apache-tomcat, and place the Web package folder in the WebApps folder of Apache-tomcat. After completing the single-device access steps, run the startup.bat file to start the service. Next, build a LAN, open the StreamingAssets folder in the Web package on the main server, modify the Config.json file, and change the data server address and web server IP address to the LAN IP address. Finally, access http: / / [IP address]:8080 / [Web package folder name] in the browser of other devices in the LAN to open the visual interface. You can achieve LAN access between multiple devices without running the server.

[0070] Software update: To update the server function, you only need to deploy the updated code file and restart the server. For the data display items on the visual interface, you can change them by modifying the external Json (JavaScript Object Notation) configuration file, while other visual screen updates require the project files to be packaged in the Unity engine before deployment. All these update operations only need to be completed on the server side, without having to be performed on each client computer, which greatly simplifies the update process and avoids the tedious steps of updating each computer under the traditional client architecture.

[0071] By implementing the present invention, the following beneficial effects are achieved: the present invention discloses a method and system for visualizing severe accident data of a nuclear power plant, including: a back-end simulator is connected in communication with a first back-end server, the back-end simulator sends the data of the simulation result to the first back-end server, the first back-end server is connected in communication with a back-end database, the first back-end server caches the data to the back-end database, the back-end database is connected in communication with a second back-end server, the second back-end server reads the data from the back-end database for processing, the second back-end server is connected in communication with the front-end visualization software running in a web browser, the second back-end server sends the processed data to the front-end visualization software, and the front-end visualization software displays the simulation results of the back-end simulator in the web browser. Compared with the prior art, the present invention upgrades the severe accident visualization software from the traditional C / S architecture to the B / S architecture by using WebGL technology, realizes the networking of simulator products, and provides more diversified technical options to adapt to the technological development of the industrial Internet. This transformation improves the convenience of software use, allowing users to use the software by accessing web pages through a browser without installation, which facilitates the development of simulator training.

[0072] At the same time, the present invention maintains the original functions and three-dimensional special effects of the software, supports cross-platform use, and can perform data deduction of recorded data files at 128 times the speed of playback. In addition, each software update only requires replacing the files on the server, which simplifies the maintenance and update process. When modifying the data items in the external Json configuration file, the user only needs to refresh the page to complete the update, further improving the convenience of software use and the efficiency of maintenance.

[0073] It is understandable that the above embodiments only express some implementation methods of the present invention, and the description thereof is relatively specific and detailed, but it cannot be understood as limiting the scope of the patent of the present invention. It should be pointed out that for ordinary technicians in this field, without departing from the concept of the present invention, the above embodiments or technical features can be freely combined, and several deformations and improvements can be made, which all belong to the protection scope of the present invention, that is, the embodiments described in "some embodiments" can be freely combined with any of the above and below embodiments. Therefore, all equivalent changes and modifications made to the scope of the claims of the present invention should belong to the scope of the claims of the present invention.

Claims

1. A method for visualizing severe accident data of a nuclear power plant, characterized in that: The following steps are involved: The back-end simulator is connected to the back-end first server for communication, and the back-end simulator sends the simulation result data to the back-end first server; The first backend server is connected to the backend database for communication, and the first backend server caches the data in the backend database; The back-end database is connected to the back-end second server for communication, and the back-end second server reads data from the back-end database for processing; The back-end second server is connected to the front-end visualization software running in the web browser, and the back-end second server sends the processed data to the front-end visualization software, and the front-end visualization software displays the simulation results of the back-end simulator in the web browser.

2. The method for visualizing severe accident data of a nuclear power plant according to claim 1, characterized in that: The method for visualizing severe accident data of a nuclear power plant also includes: the front-end visualization software sends an instruction to the back-end second server to switch the state of the back-end second server, and the state of the back-end second server includes running state, pause state, recording state and playback state.

3. The method for visualizing severe accident data of a nuclear power plant according to claim 2, characterized in that: The front-end visualization software sends an instruction to the back-end second server to switch the state of the back-end second server to the recording state, including: The front-end visualization software sends a recording instruction to the back-end second server. The back-end second server checks whether the folder used to store the recorded data file exists according to the recording instruction. If it does not exist, the back-end second server automatically creates a folder and checks whether the current state is a recording state. If so, the back-end second server collects all current data in real time, generates a recorded data file, and stores it in the folder.

4. The method for visualizing severe accident data of a nuclear power plant according to claim 2, characterized in that: The front-end visualization software sends an instruction to the back-end second server to switch the state of the back-end second server to the playback state, including: The front-end visualization software sends a playback instruction to the back-end second server. The back-end second server reads the data saved in the folder according to the instruction and sends the data to the front-end visualization software according to the current speed. If it is played normally, each piece of data is sent; if it is played at double speed, the data is sent according to the speed interval.

5. The method for visualizing severe accident data of a nuclear power plant according to claim 4, characterized in that: The front-end visualization software sends instructions to the back-end second server to switch the state of the back-end second server to the playback state, and also includes: in the playback state, the front-end visualization software sends time parameters to the back-end second server according to the position of the progress bar dragged or the input time point, and the back-end second server fast-forwards to the position or time point at the maximum playback speed according to the time parameters and then resumes normal playback.

6. The method for visualizing severe accident data of a nuclear power plant according to claim 5, characterized in that: The front-end visualization software sends an instruction to the back-end second server to switch the state of the back-end second server to the playback state, and also includes: in the playback state, the back-end second server pauses the playback according to the instruction of the front-end visualization software.

7. The method for visualizing severe accident data of a nuclear power plant according to claim 6, characterized in that: The front-end visualization software sends an instruction to the back-end second server to switch the state of the back-end second server to the playback state, and also includes: in the playback state, the back-end second server exits the playback according to the instruction of the front-end visualization software.

8. The method for visualizing severe accident data of a nuclear power plant according to claim 1, characterized in that: The data communication between the back-end second server and the front-end visualization software is transmitted in a data frame, and the data frame includes a header and a body; the header includes the information type and the current state of the back-end second server.

9. The method for visualizing severe accident data of a nuclear power plant according to claim 1, characterized in that: The back-end simulator sends the data to the back-end first server, which includes: the simulation software of the back-end simulator simulates the nuclear power accident scenario according to the preset nuclear power system model to obtain the data required for visual display.

10. Nuclear power plant severe accident data visualization system, characterized in that: The invention comprises a back-end simulator for realizing the nuclear power plant severe accident data visualization method as claimed in any one of claims 1 to 9, a back-end first server, a back-end database, a back-end second server and a front-end visualization software running in a web browser.

Images