Rule-based nuclear emergency event database construction method and device

Abstract

The present disclosure belongs to the technical field of nuclear power, and particularly relates to a rule-based nuclear emergency event database construction method and device. The rule-based nuclear emergency event database construction method can realize automatic acquisition, machine translation, classification coding, screening and arrangement of nuclear emergency related event data, form a nuclear emergency event database, and provide data support for nuclear emergency decision-making. The present disclosure fills the current domestic blank, can realize quick and accurate positioning, quantitative analysis and evaluation of events in the occurrence of nuclear emergency events, and provides data support for nuclear emergency decision-making of nuclear facility departments at all levels in the first time.

Description

Technical Field

[0001] This invention belongs to the field of nuclear power technology, specifically relating to a rule-based method and apparatus for constructing a nuclear emergency event database. Background Technology

[0002] With the development of my country's nuclear industry, the number of nuclear facilities is increasing, and the safety challenges will become greater. It is crucial to be able to analyze, assess, and respond promptly and accurately when anomalies or incidents occur at nuclear facilities. This necessitates the construction of a nuclear emergency event database applicable to Chinese nuclear facilities to provide data support for nuclear emergency decision-making.

[0003] The amount of safety supervision data at each stage of nuclear facilities is large and the types of data are numerous. They are also scattered across different websites or systems. Relying solely on manual acquisition is inefficient and fails to meet the timeliness requirements for response when nuclear emergency-related incidents actually occur.

[0004] The IAEA (International Atomic Energy Agency) stipulates in its Nuclear and Radiation Emergency Preparedness and Response Standards that the actions taken to explain the current emergency to the public during a nuclear accident should be compared and analyzed with the actions recommended by other countries. The main source of international data related to nuclear emergencies is IAEA event reports; however, a large amount of foreign language data still needs translation, and using general translation tools has limitations in terms of inaccurate translation of nuclear terminology.

[0005] Nuclear emergency-related event data, including event reports from nuclear power plants, research reactors, and civilian nuclear fuel cycle facilities, lacks corresponding nuclear emergency event codes and a nuclear emergency event classification and coding system has not yet been established, making it impossible to carry out the construction of a nuclear emergency event database.

[0006] For the reasons mentioned above, there is an urgent need to be able to quickly and accurately locate, quantitatively analyze, and assess accidents in the event of a nuclear emergency. Summary of the Invention

[0007] To overcome the problems existing in related technologies, a rule-based method and apparatus for constructing a nuclear emergency event database are provided.

[0008] According to one aspect of the embodiments of this disclosure, a rule-based method for constructing a nuclear emergency event database is provided, the method comprising the following steps:

[0009] Step 1, Obtain kernel event data;

[0010] Step 2: Machine translation is performed on the foreign language nuclear event data in the nuclear event data to obtain the Chinese translation;

[0011] Step 3: Establish automatic classification and coding for nuclear event data;

[0012] Step 4: Automatic classification and coding are used to filter and arrange nuclear event data and Chinese translations to form a nuclear emergency event database.

[0013] In one possible implementation, step 1 includes:

[0014] Step 11: Obtain foreign language nuclear event data, which includes nuclear safety-related event data from domestic and foreign nuclear power plants and research reactors;

[0015] Step 12: Obtain relevant event data from domestic nuclear power plants. This data includes nuclear power plant operation event reports, nuclear power plant construction event reports, and nuclear power plant internal event reports.

[0016] Step 13: Obtain relevant event data for domestic research reactors, including research reactor operation event reports and research reactor construction event reports;

[0017] Step 14: Obtain relevant event data for domestic civilian nuclear fuel cycle facilities.

[0018] In one possible implementation, step 2 includes:

[0019] Step 21: Call the API interface to translate non-core technical terms;

[0020] Step 22: Acquire and organize professional terms in the nuclear industry to form a nuclear professional terminology database;

[0021] Step 23: Based on calling the API interface, add a replacement and proofreading function for the core professional lexicon, combine it with the conventional translation model, and use the core industry corpus for machine learning to build a core professional translation tool with replacement function to realize machine translation of foreign language core event data;

[0022] Step 24: Arrange the translated Chinese results from the English fields according to the language arrangement of the corresponding Chinese fields and store them in the database.

[0023] In one possible implementation, step 3 includes:

[0024] Step 31: Construct an automatic classification code applicable to nuclear power plants, research reactors, and civilian nuclear fuel cycle facilities. The automatic classification code includes two levels: nuclear emergency level 1 code and nuclear emergency level 2 code.

[0025] Among them, after refining the consequences of nuclear emergencies in the classification criteria related to nuclear power plant emergency events and the classification criteria related to research reactor emergency events, and using data verification using IAEA event reports, nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, and research reactor construction event reports, a first-level code for nuclear emergency events applicable to nuclear power plants and research reactors was summarized, including: increased heat discharge from the secondary loop system, decreased heat discharge from the secondary loop system, decreased reactor coolant system flow rate, abnormal reactivity and power distribution, unexpected increase in reactor coolant charge, unexpected decrease in reactor coolant charge, abnormal radioactive effluent / radiation levels, and expected transients where emergency shutdown was not achieved.

[0026] After refining the causes of nuclear emergency events related to the classification criteria for nuclear power plant emergency events and the classification criteria for nuclear reactor emergency events, and verifying the data using IAEA event reports, nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, and research reactor construction event reports, a secondary code for nuclear emergency events applicable to nuclear power plants and research reactors was summarized. The secondary code for nuclear emergency events with increased heat exhaust in the secondary loop system, which is a primary code for nuclear emergency events, includes: decreased feedwater temperature, increased feedwater flow rate, increased steam flow rate, steam generator safety valve / steam generator release valve / steam discharge valve stuck in the open position, and steam pipe rupture inside and outside the containment.

[0027] By refining the types of nuclear facilities involved in nuclear emergencies in the classification criteria related to emergency events of civilian nuclear fuel cycle facilities, and verifying the data using the operational event reports of civilian nuclear fuel cycle facilities, a first-level code for nuclear emergency events applicable to civilian nuclear fuel cycle facilities was summarized, including: typical accidents of uranium conversion facilities, typical accidents of centrifuge separation facilities, typical accidents of pressurized water reactor nuclear fuel manufacturing facilities, and typical accidents of spent fuel reprocessing facilities.

[0028] By extracting the accident consequences of nuclear facility types involved in nuclear emergencies from the classification criteria related to emergency events at civilian nuclear fuel cycle facilities, and verifying the data using operational event reports of civilian nuclear fuel cycle facilities, a secondary code for nuclear emergency events applicable to civilian nuclear fuel cycle facilities was summarized. The secondary codes for typical accidents in uranium conversion facilities under the primary code for nuclear emergency events include: large-scale UF6 release accidents, HF leak accidents, F2 leak accidents, hydrogen explosion accidents, criticality accidents, and fire accidents.

[0029] Step 32: Establish an automatic classification and coding system based on logical rules, including setting logical rules for each nuclear emergency level 2 code under each nuclear emergency level 1 code, for IAEA event reports, nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, research reactor construction event reports, and civilian nuclear fuel cycle facility operation event reports, so as to realize the automatic classification and coding of nuclear event data obtained in Step 2 and machine translated in Step 3.

[0030] In one possible implementation, step 4 includes:

[0031] Step 41: Based on the classification and coding results of the nuclear event data in Step 3, filter out the nuclear event data whose nuclear emergency event codes are not empty, and use them as the original nuclear emergency event data;

[0032] Step 42: Based on the meaning of fields in the selected raw nuclear emergency event data from IAEA event reports, nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, research reactor construction event reports, and civilian nuclear fuel cycle facility operation event reports, the data is rearranged to form nuclear emergency event data with unified fields. The unified fields include: event source, domestic / foreign, operating unit name, nuclear facility name, event name, event date, nuclear emergency primary code, nuclear emergency secondary code, event overview, event consequences, event cause, and measures taken. Finally, a nuclear emergency event database is constructed.

[0033] According to another aspect of the embodiments of this disclosure, a rule-based nuclear emergency event database construction apparatus is provided, the apparatus comprising:

[0034] The acquisition module is used to acquire kernel event data;

[0035] The translation module is used to perform machine translation on foreign language nuclear event data in the nuclear event data to obtain Chinese translations;

[0036] Establish a module for creating automatic classification and coding of nuclear event data;

[0037] The arrangement module is used to filter and arrange nuclear event data and Chinese translations using automatic classification coding to form a nuclear emergency event database.

[0038] According to another aspect of the embodiments of this disclosure, a rule-based nuclear emergency event database construction apparatus is provided, the apparatus comprising:

[0039] processor;

[0040] Memory used to store processor-executable instructions;

[0041] The processor is configured to execute the above-described method.

[0042] According to another aspect of the present disclosure, a non-volatile computer-readable storage medium is provided, on which computer program instructions are stored, which, when executed by a processor, implement the above-described method.

[0043] The beneficial effects of this disclosure are as follows: The rule-based nuclear emergency event database construction method disclosed herein can automatically acquire, machine translate, classify, encode, filter, and arrange nuclear emergency-related event data to form a nuclear emergency event database, providing data support for nuclear emergency decision-making. This fills a current domestic gap, enabling rapid and accurate location, quantitative analysis, and assessment of nuclear emergency events, providing immediate data support for nuclear emergency decision-making by nuclear facility management departments at all levels. Attached Figure Description

[0044] Figure 1 This is a flowchart illustrating a rule-based method for constructing a nuclear emergency event database according to an exemplary embodiment.

[0045] Figure 2 This is a block diagram illustrating a rule-based nuclear emergency event database construction apparatus according to an exemplary embodiment. Detailed Implementation

[0046] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0047] Figure 1 This is a flowchart illustrating a rule-based method for constructing a nuclear emergency event database according to an exemplary embodiment. The method can be executed by a terminal device, which can be, for example, a server, desktop computer, laptop computer, tablet computer, etc. This disclosure does not limit the type of terminal device. Figure 1 As shown, the method includes the following steps:

[0048] Step 1: Obtain kernel event data. For example, Step 1 may include Steps 11 through 14.

[0049] Step 11: Obtain foreign language nuclear event data, which may include IAEA event reports. IAEA event reports are retrieved from the IAEA website using preset strategies according to the IRS coding manual (Joint IAEA / NEA International Reporting System for Operating Experience). These reports mainly include nuclear safety-related event data from domestic and international nuclear power plants and research reactors.

[0050] Step 12: Obtain relevant event data for domestic nuclear power plants. This data includes nuclear power plant operation event reports, nuclear power plant construction event reports, and nuclear power plant internal event reports.

[0051] The National Nuclear Safety Administration's nuclear safety regulations specify clear requirements for reporting nuclear power plant operating events and construction events. HAF001 / 02 / 01, the "Reporting System for Nuclear Power Plant Operators," clearly outlines requirements and regulations for reporting operating events and construction events prior to 2020; the "Regulations on Nuclear Safety Reporting for Nuclear Power Plant Operators" and the "Guidelines for Nuclear Safety Reporting for Nuclear Power Plant Operators" clearly stipulate requirements and regulations for reporting operating events and construction events from 2021 onwards. Nuclear power plant operating event reports and nuclear power plant construction event reports are retrieved from the National Nuclear Safety Administration's website using a pre-defined strategy, in accordance with the aforementioned regulations.

[0052] Among them, internal incident reports of nuclear power plants that do not meet the reporting criteria of nuclear safety regulations are also a very important type of incident from the perspective of nuclear emergency events. These incidents are worth learning from and referencing, and have experience feedback value. They can be captured from the nuclear power experience feedback platform of the National Energy Administration through preset strategies.

[0053] Step 13: Obtain relevant event data for domestic research reactors, including research reactor operation event reports and research reactor construction event reports.

[0054] The National Nuclear Safety Administration's nuclear safety regulations have clear requirements for reporting research reactor operation events and research reactor construction events. Specifically, HAF001 / 02 / 02, "Research Reactor Operating Unit Reporting System," specifies the requirements and regulations for reporting research reactor operation events and research reactor construction events. These reports are retrieved from the National Nuclear Safety Administration's website using a pre-defined strategy, in accordance with the aforementioned regulations.

[0055] Step 14: Obtain relevant event data for domestic civilian nuclear fuel cycle facilities, including operational event reports for civilian nuclear fuel cycle facilities.

[0056] The National Nuclear Safety Administration's nuclear safety regulations have clear requirements for emergency reporting of nuclear accidents at civilian nuclear fuel cycle facilities. Specifically, HAF001 / 02 / 03, "Reporting System for Nuclear Fuel Cycle Facilities," specifies the requirements and regulations for emergency reporting of nuclear accidents at civilian nuclear fuel cycle facilities. Reports of operational events at civilian nuclear fuel cycle facilities are retrieved from the National Nuclear Safety Administration's website using a pre-defined strategy, in accordance with the aforementioned regulations.

[0057] Step 2: Machine translation is performed on the foreign language data in the nuclear event data to obtain Chinese translations.

[0058] For example, step 2 may include steps 21 to 24.

[0059] Step 21: Call the API interface to translate non-core technical terms.

[0060] Step 22: Acquire and organize professional terms in the nuclear industry to form a nuclear professional terminology database.

[0061] Step 23: Based on the API call, add a replacement and proofreading function for the core professional lexicon. Combine with the conventional translation model, use the core industry corpus for machine learning to build a core professional translation tool with replacement function, and realize machine translation of IAEA event report data.

[0062] Step 24: Arrange the translated Chinese results of the English fields according to the language arrangement of the corresponding Chinese fields and store them in the database. For example, the language arrangement of Chinese fields may include country (nation name), plant name (plant name), unit code (unit code), subject (subject), event date (event date), event summary (event summary), event description (event desc), cause analysis (analysis), lessons learned and corrective actions (event lessons). The Chinese translations can be arranged according to this arrangement and then stored in the database.

[0063] Step 3: Establish classification codes for nuclear event data. For example, Step 3 may include Steps 31 and 32.

[0064] Step 31: Construct a classification coding system for nuclear emergency events applicable to nuclear power plants, research reactors, and civilian nuclear fuel cycle facilities. The classification coding includes two levels: a primary nuclear emergency code and a secondary nuclear emergency code. Specifically:

[0065] The classification criteria related to nuclear power plant emergency events include: International Nuclear Event Scale (IAEA and International Nuclear Energy Experts), GB 6249-2011 "Regulations for Environmental Radiation Protection of Nuclear Power Plants", "Classification of Operating and Accident Conditions of Pressurized Water Reactor Nuclear Power Plants" (EJ 312-88), NB / T 20103-2012 "Accident Analysis and Safety Criteria for Pressurized Water Reactor Nuclear Power Plants", "Emergency Status Classification Criteria for Nuclear Power Plants" (EAL), HAD002 / 01-2019 "Emergency Preparedness and Emergency Response of Nuclear Power Plant Operating Units", NB / T 20529-2018 "Radiation Protection Design Criteria for Pressurized Water Reactor Nuclear Power Plants", HAF002 "Regulations on Emergency Management of Nuclear Accidents in Nuclear Power Plants", and GB / T17680 "Guidelines for Emergency Planning and Preparedness of Nuclear Power Plants".

[0066] The classification criteria related to emergency events at research reactors include: "Emergency-Related Parameters for Research Reactors" (HJ843-2017), HAF201 "Safety Regulations for Research Reactor Design", HAF202 "Safety Regulations for Research Reactor Operation", and HAF001 / 02 / 02 "Research Reactor Operating Unit Reporting System (Appendix II to the Implementation Rules of the Regulations on Supervision and Management of Civil Nuclear Facilities of the People's Republic of China)".

[0067] The classification criteria related to emergency events at civilian nuclear fuel cycle facilities include: "Emergency-Related Parameters for Nuclear Fuel Cycle Facilities" (HJ 844-2017).

[0068] The Level 1 coding system for nuclear emergency events applicable to nuclear power plants and research reactors was developed by extracting the consequences of nuclear emergencies from the classification criteria related to nuclear power plant emergency events and research reactor emergency events. This system was validated using data from IAEA event reports, nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, and research reactor construction event reports. The system includes: Increased secondary coolant discharge (SHI), Decreased secondary coolant discharge (SHR), Reduced reactor coolant system flow (CFD), Reactivity and power distribution anomalies (RPA), Unexpected increase in reactor coolant charge (RCI), Unexpected decrease in reactor coolant charge (RCD), Radioactive effluent / radiation level anomalies (RRA), and Expected transients without emergency shutdown (FST).

[0069] The secondary codes for nuclear emergency events applicable to nuclear power plants and research reactors were developed by extracting the causes of events related to the consequences of nuclear emergencies from the classification criteria for nuclear power plant emergency events and the classification criteria for research reactor emergency events. This was then validated using data from IAEA event reports, nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, and research reactor construction event reports. For example, the primary nuclear emergency code "Increased Heat Dissipation in the Secondary Circuit (SHI)" includes the following secondary nuclear emergency codes: decreased feedwater temperature (SHI1), increased feedwater flow rate (SHI2), increased steam flow rate (SHI3), steam generator safety valve / steam generator release valve / steam discharge valve stuck in the open position (SHI4), and ruptured steam pipes inside and outside the containment (SHI5).

[0070] The Level 1 coding system for nuclear emergency events applicable to civilian nuclear fuel cycle facilities was developed by refining the types of nuclear facilities involved in nuclear emergencies from the classification criteria related to emergency events at civilian nuclear fuel cycle facilities, and validating the data using operational event reports from civilian nuclear fuel cycle facilities. It includes: Typical Accidents (UCA) at uranium conversion facilities, Typical Accidents (CSA) at centrifuge facilities, Typical Accidents (PMA) at pressurized water reactor nuclear fuel manufacturing facilities, and Typical Accidents (SAA) at spent fuel reprocessing facilities.

[0071] The secondary codes for nuclear emergency events applicable to civilian nuclear fuel cycle facilities are derived by extracting the accident consequences included in the types of nuclear facilities involved in nuclear emergencies in the classification criteria related to nuclear emergency events of civilian nuclear fuel cycle facilities, and verifying the data using operational event reports of civilian nuclear fuel cycle facilities. For example, the primary nuclear emergency code "Typical Accident (UCA) of Uranium Conversion Facility" includes the following secondary nuclear emergency codes: large UF6 release accident (UCA1), HF leak accident (UCA2), F2 leak accident (UCA3), hydrogen explosion accident (UCA4), criticality accident (UCA5), and fire accident (UCA6).

[0072] Step 32, Classification and Coding Based on Logical Rules. For IAEA event reports, nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, research reactor construction event reports, and civilian nuclear fuel cycle facility operation event reports, logical rules are set for the nuclear emergency secondary codes under each primary nuclear emergency code. This is to achieve classification and coding of the nuclear event data obtained in Step 2 and machine-translated in Step 3. Wherein:

[0073] The logical rules include matching fields, matching keywords, and the position of the keywords in the text. For example, for an IAEA event report, the nuclear emergency level 1 code "increased heat discharge from the secondary loop system (SHI)" and the nuclear emergency level 2 code "increased steam flow (SHI3)" correspond to the event name (subject), summary (event_summary), and event description (event_desc) in the IAEA event report data; the matching keywords include keyword 1: "steam flow" or "steam pipeline flow" or "VVP flow" or "TSM flow", and keyword 2: "increased" or "increased"; keyword 1 and keyword 2 appear in the same sentence in the text (the sentence is separated by full-width or half-width commas, periods, and exclamation marks), and keyword 1 is located before keyword 2 in the sentence.

[0074] Step 4 involves using classification coding to filter and organize nuclear event data and Chinese translations to form a nuclear emergency event database. For example, Step 4 includes Steps 41 and 42.

[0075] Step 41: Based on the classification and coding results of the nuclear event data in Step 3, filter out the nuclear event data whose nuclear emergency event codes are not empty, and use them as the original nuclear emergency event data.

[0076] Step 42: The selected raw nuclear emergency event data is reorganized according to the field meanings in IAEA event reports, nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, research reactor construction event reports, and civilian nuclear fuel cycle facility operation event reports to form nuclear emergency event data with unified fields. These unified fields include: event source, domestic / foreign, operating unit name, nuclear facility name, event name, event date (e.g., year, month, day), nuclear emergency level 1 code, nuclear emergency level 2 code, event overview, event consequences, event cause, and measures taken. This process ultimately constructs a nuclear emergency event database. The mapping relationships between the different unified fields are as follows:

[0077] The unified field "Event Source" corresponds to the source of nuclear event data, namely "IAEA Event Report", "Nuclear Power Plant Operation Event Report", "Nuclear Power Plant Construction Event Report", "Nuclear Power Plant Internal Event Report", "Research Reactor Operation Event Report", "Research Reactor Construction Event Report" and "Civil Nuclear Fuel Cycle Facility Operation Event Report".

[0078] The unified field "Domestic / Foreign" is used to determine the country (nation Name) for IAEA event report data; however, for nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, research reactor construction event reports, and civilian nuclear fuel cycle facility operation event reports, the field "Domestic" is used.

[0079] The unified field "Operating Unit Name" corresponds to the following fields: "Plant Name" for IAEA event report data; "Plant" for nuclear power plant operation event report data; "Plant Name" for nuclear power plant construction event report data; "Nuclear Power Plant Name" for nuclear power plant internal event report data; and "Operating Unit Name" for research reactor operation event reports, research reactor construction event reports, and civil nuclear fuel cycle facility operation event reports.

[0080] The unified field "Nuclear Facility Name" corresponds to the field "Unit Code" for IAEA event report data; the field "Unit Number" corresponds to the field "Unit Code" for nuclear power plant operation event reports, nuclear power plant construction event reports, and nuclear power plant internal event reports; and the field "Nuclear Facility Name" corresponds to the field "Research Reactor Operation Event Report, Research Reactor Construction Event Report, and Civil Nuclear Fuel Cycle Facility Operation Event Report data."

[0081] The unified field "Event Name" corresponds to the field "Event Name (subject)" for IAEA event report data; and it also corresponds to "Event Name" for nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, research reactor construction event reports, and civil nuclear fuel cycle facility operation event reports.

[0082] The unified field "Event Date" corresponds to the following data: IAEA event report data; nuclear power plant operation event report data and nuclear power plant internal event report data; and nuclear power plant construction event report data, research reactor operation event report, research reactor construction event report, and civil nuclear fuel cycle facility operation event report data.

[0083] The unified fields “Nuclear Emergency Level 1 Code” and “Nuclear Emergency Level 2 Code” correspond to the “Nuclear Emergency Level 1 Code” and “Nuclear Emergency Level 2 Code” in IAEA event report data, nuclear power plant operation event report, nuclear power plant construction event report, nuclear power plant internal event report, research reactor operation event report, research reactor construction event report, and civil nuclear fuel cycle facility operation event report data, respectively.

[0084] The unified field "Event Overview" corresponds to the following fields: "Event Summary" for IAEA event report data; "Summary" for nuclear power plant operation event report data; "Report Summary" for nuclear power plant construction event reports, research reactor operation event reports, and research reactor construction event reports; "Event Description" for internal nuclear power plant event report data; and "Event Description" for civil nuclear fuel cycle facility operation event report data.

[0085] The unified field "Event Consequences" has no corresponding field for IAEA event reports, research reactor construction event reports, and civilian nuclear fuel cycle facility operation event reports; however, it does exist for nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, and research reactor operation event reports.

[0086] The unified field "Cause of the Incident" corresponds to the field "Analysis" for IAEA incident report data; for nuclear power plant operation incident reports and nuclear power plant internal incident reports, it corresponds to the field "Direct Cause" plus the field "Root Cause"; for nuclear power plant construction incident report data, it corresponds to the field "Direct Cause of the Incident" plus the field "Root Cause of the Incident"; for research reactor operation incident report data, there is no corresponding field; for research reactor construction incident report data, it corresponds to the field "Cause of the Incident and Lessons Learned"; and for civilian nuclear fuel cycle facility operation incident report data, it corresponds to the field "Cause of the Incident".

[0087] The unified field "Measures Taken" corresponds to the following fields: "Lessons Learned and Corrective Actions" for IAEA event report data; "Corrective Actions and Corrective Action Plans" for nuclear power plant operation event report data; "Corrective Actions" for nuclear power plant construction event report data; no corresponding field for nuclear power plant internal event report data; "Lessons Learned and Corrective Measures" for research reactor operation event report data; "Corrective Measures" for research reactor construction event report data; and "Corrective Measures and Lessons Learned" for civil nuclear fuel cycle facility operation event report data.

[0088] In one possible implementation, a rule-based nuclear emergency event database construction apparatus is provided, the apparatus comprising:

[0089] The acquisition module is used to acquire kernel event data;

[0090] The translation module is used to perform machine translation on foreign language nuclear event data in the nuclear event data to obtain Chinese translations;

[0091] Establish a module for creating automatic classification and coding of nuclear event data;

[0092] The arrangement module is used to filter and arrange nuclear event data and Chinese translations using automatic classification coding to form a nuclear emergency event database.

[0093] The description of the above-mentioned apparatus has already been elaborated in the description of the above-mentioned method, and will not be repeated here.

[0094] Figure 2 This is a block diagram illustrating a rule-based nuclear emergency event database construction apparatus according to an exemplary embodiment. For example, apparatus 1900 may be provided as a server. (Refer to...) Figure 2 The apparatus 1900 includes a processing component 1922, which further includes one or more processors, and memory resources represented by memory 1932 for storing instructions, such as application programs, that can be executed by the processing component 1922. The application programs stored in memory 1932 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 1922 is configured to execute instructions to perform the methods described above.

[0095] Device 1900 may also include a power supply component 1926 configured to perform power management of device 1900, a wired or wireless network interface 1950 configured to connect device 1900 to a network, and an input / output (I / O) interface 1958. Device 1900 can operate on an operating system stored in memory 1932, such as Windows Server™, MacOS X™, Unix™, Linux™, FreeBSD™, or similar.

[0096] In an exemplary embodiment, a non-volatile computer-readable storage medium is also provided, such as a memory 1932 including computer program instructions that can be executed by a processing component 1922 of the device 1900 to perform the above-described method.

[0097] This disclosure can be a system, method, and / or computer program product. A computer program product may include a computer-readable storage medium having computer-readable program instructions loaded thereon for causing a processor to implement various aspects of this disclosure.

[0098] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example—but not limited to—electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital multifunction disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination thereof. The computer-readable storage media used herein are not to be construed as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires.

[0099] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0100] Computer program instructions used to perform the operations of this disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing the status information of the computer-readable program instructions to implement various aspects of this disclosure.

[0101] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0102] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0103] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0104] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0105] The various embodiments of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or improvement of the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A rule-based method for constructing a nuclear emergency event database, characterized in that, The method includes the following steps: Step 1, Obtain kernel event data; Step 2: Machine translation is performed on the foreign language nuclear event data in the nuclear event data to obtain the Chinese translation; Step 3: Establish automatic classification and coding for nuclear event data; Step 4: Automatic classification and coding are used to filter and arrange nuclear event data and Chinese translations to form a nuclear emergency event database; Step 2 includes: Step 21: Call the API interface to translate non-core technical terms; Step 22: Acquire and organize professional terms in the nuclear industry to form a nuclear professional terminology database; Step 23: Based on calling the API interface, add a replacement and proofreading function for the core professional lexicon, combine it with the conventional translation model, and use the core industry corpus for machine learning to build a core professional translation tool with replacement function to realize machine translation of foreign language core event data; Step 24: Arrange the translated Chinese results from the English fields according to the language arrangement of the corresponding Chinese fields and store them in the database; Step 3 includes: Step 31: Construct an automatic classification code applicable to nuclear power plants, research reactors, and civilian nuclear fuel cycle facilities. The automatic classification code includes two levels: nuclear emergency level 1 code and nuclear emergency level 2 code. Step 32: Establish an automatic classification and coding system based on logical rules, including: setting logical rules for each nuclear emergency level 2 code under each nuclear emergency level 1 code for IAEA event reports, nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, research reactor construction event reports, and civilian nuclear fuel cycle facility operation event reports, so as to realize the automatic classification and coding of nuclear event data obtained in Step 2 and machine translated in Step 3. Step 4 includes: Step 41: Based on the classification and coding results of the nuclear event data in Step 3, filter out the nuclear event data whose nuclear emergency event codes are not empty, and use them as the original nuclear emergency event data; Step 42: Based on the meaning of fields in the selected raw nuclear emergency event data from IAEA event reports, nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, research reactor construction event reports, and civilian nuclear fuel cycle facility operation event reports, the data is rearranged to form nuclear emergency event data with unified fields. The unified fields include: event source, domestic / foreign, operating unit name, nuclear facility name, event name, event date, nuclear emergency primary code, nuclear emergency secondary code, event overview, event consequences, event cause, and measures taken. Finally, a nuclear emergency event database is constructed.

2. The method according to claim 1, characterized in that, Step 1 includes: Step 11: Obtain foreign language nuclear event data, which includes nuclear safety-related event data from domestic and foreign nuclear power plants and research reactors; Step 12: Obtain relevant event data from domestic nuclear power plants. This data includes nuclear power plant operation event reports, nuclear power plant construction event reports, and nuclear power plant internal event reports. Step 13: Obtain relevant event data for domestic research reactors, including research reactor operation event reports and research reactor construction event reports; Step 14: Obtain relevant event data for domestic civilian nuclear fuel cycle facilities.

3. The method according to claim 1, characterized in that, In step 31, the consequences of nuclear emergencies in the classification criteria related to nuclear power plant emergency events and the classification criteria related to research reactor emergency events are extracted. Data verification is performed using IAEA event reports, nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, and research reactor construction event reports. A first-level code for nuclear emergency events applicable to nuclear power plants and research reactors is summarized, including: increased heat discharge from the secondary loop system, decreased heat discharge from the secondary loop system, decreased reactor coolant system flow rate, abnormal reactivity and power distribution, unexpected increase in reactor coolant charge, unexpected decrease in reactor coolant charge, abnormal radioactive effluent / radiation levels, and expected transients where emergency shutdown is not possible. After refining the causes of nuclear emergency events related to the classification criteria for nuclear power plant emergency events and the classification criteria for nuclear reactor emergency events, and verifying the data using IAEA event reports, nuclear power plant operation event reports, nuclear power plant construction event reports, nuclear power plant internal event reports, research reactor operation event reports, and research reactor construction event reports, a secondary code for nuclear emergency events applicable to nuclear power plants and research reactors was summarized. The secondary code for nuclear emergency events with increased heat exhaust in the secondary loop system, which is a primary code for nuclear emergency events, includes: decreased feedwater temperature, increased feedwater flow rate, increased steam flow rate, steam generator safety valve / steam generator release valve / steam discharge valve stuck in the open position, and steam pipe rupture inside and outside the containment. By refining the types of nuclear facilities involved in nuclear emergencies in the classification criteria related to emergency events of civilian nuclear fuel cycle facilities, and verifying the data using the operational event reports of civilian nuclear fuel cycle facilities, a first-level code for nuclear emergency events applicable to civilian nuclear fuel cycle facilities was summarized, including: typical accidents of uranium conversion facilities, typical accidents of centrifuge separation facilities, typical accidents of pressurized water reactor nuclear fuel manufacturing facilities, and typical accidents of spent fuel reprocessing facilities. By extracting the accident consequences of nuclear facility types involved in nuclear emergencies from the classification criteria related to emergency events at civilian nuclear fuel cycle facilities, and verifying the data using operational event reports of civilian nuclear fuel cycle facilities, a secondary code for nuclear emergency events applicable to civilian nuclear fuel cycle facilities was summarized. The secondary codes for typical accidents in uranium conversion facilities, which are classified as primary nuclear emergency codes, include: large-scale UF6 release accidents, HF leakage accidents, F2 leakage accidents, hydrogen explosion accidents, criticality accidents, and fire accidents.

4. A rule-based nuclear emergency event database construction device, characterized in that, The device includes: The acquisition module is used to acquire kernel event data; The translation module is used to perform machine translation on foreign language nuclear event data in the nuclear event data to obtain Chinese translations; Establish a module for creating automatic classification and coding of nuclear event data; The arrangement module is used to filter and arrange nuclear event data and Chinese translations using automatic classification coding to form a nuclear emergency event database; The device further includes: processor; Memory used to store instructions executed by the processor; The processor is configured to perform the method according to any one of claims 1 to 3.

5. A non-volatile computer-readable storage medium storing computer program instructions thereon, characterized in that, When the computer program instructions are executed by the processor, they implement the method described in any one of claims 1 to 3.

Images