Data structure design method of heat pipe micro-stack system analysis software

Abstract

The invention provides a data structure design method for heat pipe micro-stack system analysis software. The data structure design method comprises the steps that data variables involved in the system analysis software are divided according to categories according to a heat pipe micro-stack structure and data meanings; constructing global data according to the category, and establishing local data corresponding to the global data through mapping; data streams of the global data and the local data are designed, and the data streams comprise the steps that before each step of transient calculation is conducted, data in the global data are copied to the local data; calculating data in the local data to obtain data of a next time step; and transmitting the data of the next time step back to the global data.

Description

Technical Field

[0001] The invention mainly relates to the technical field of nuclear reactors, and in particular to a data structure design method for heat pipe micro-reactor system analysis software. Background Art

[0002] The heat pipe micro reactor is a unique small reactor system. Compared with traditional reactors, the heat pipe micro reactor is significantly reduced in power, size, weight, etc. It has the characteristics of factory prefabrication, transportable device, and self-regulation in operation.

[0003] The development of new reactor types requires the use of system analysis software for safety analysis. Since the core geometry of heat pipe micro-reactors is quite different from that of traditional reactors, and an off-reactor reactivity control method (such as a control drum, sliding reflector, etc.) is used, the software needs to have the ability to model irregular geometry cores. Heat pipe micro-reactors have high operating temperatures, and thermal expansion deformation contributes significantly to reactivity changes, so deformation reactivity effects also need to be considered. Heat pipe micro-reactors are different from traditional reactors. They use all-solid cores and heat pipes as heat extraction devices, so traditional safety analysis software is not applicable. Since there is no mature software available directly in China, it is necessary to develop system analysis software suitable for heat pipe micro-reactors for the safety analysis of heat pipe micro-reactors. The software has transient calculation functions and can accurately simulate parameter changes of heat pipe micro-reactors under transient and accident conditions.

[0004] Aiming at the current situation that heat pipe micro-reactor lacks safety analysis software, the present invention proposes a data structure design method for heat pipe micro-reactor system analysis software based on the demand for safety analysis, which is used to guide software development. Summary of the invention

[0005] Aiming at the problem that the current heat pipe micro-pile lacks safety analysis software, the present invention provides a data structure design method for heat pipe micro-pile system analysis software.

[0006] To solve the above technical problems, the present invention provides a data structure design method for heat pipe micro-pile system analysis software, including: dividing the data variables involved in the system analysis software into categories according to the heat pipe micro-pile structure and data meaning; constructing global data according to the categories, and establishing local data corresponding to the global data through mapping; designing the data flow of the global data and the local data, including: before performing each step of transient calculation, copying the data in the global data to the local data; calculating the data in the local data to obtain the data of the next time step; and transmitting the data of the next time step back to the global data.

[0007] Optionally, dividing the data variables involved in the system analysis software into categories according to the heat pipe micro-stack structure and the data meaning includes: dividing the data variables into a first category according to the heat pipe micro-stack structure, the first category including core category, heat pipe category, main heat exchanger category, and exhaust heat exchanger category; dividing the data variables into a second category according to the data meaning, the second category including geometry category, physics category, thermal engineering category, and control category; combining the first category and the second category to obtain a final category.

[0008] Optionally, the final category includes five main categories, namely core category, heat pipe category, main heat exchanger category, exhaust heat exchanger category and control category. The core category includes geometry category, physics category and thermal engineering category, and the heat pipe category, main heat exchanger category and exhaust heat exchanger category all include geometry category and thermal engineering category.

[0009] Optionally, transmitting the data of the next time step back to the global data includes: updating the data of the next time step to the local data, and the local data maps the data of the next time step to the global data.

[0010] Optionally, the data flow further includes: after the local data maps the data of the next time step to the global data, the local data is released.

[0011] Optionally, the data flow further includes: before transmitting the data of the next time step back to the global data, performing a data check on the data of the next time step.

[0012] Optionally, performing data check on the data of the next time step includes: determining whether the data of the next time step has a "not a number" value or an "infinity" value, and if so, not transmitting the data of the next time step back to the global data.

[0013] Optionally, the data flow further includes: using the global data to input and output data.

[0014] Optionally, the global data and the local data are organized in the form of arrays.

[0015] Optionally, the array is a dynamic array.

[0016] Compared with the prior art, the present invention has the following advantages:

[0017] The data structure design method of the heat pipe micro-pile system analysis software of the present invention divides all parameters into categories according to the structure and data meaning of the heat pipe micro-pile, which is convenient for management and reference; adopts the data structure of "global data-local data" to avoid the tampering of the global data by the sub-module, thereby protecting the data security; the present invention designs a data flow suitable for the heat pipe micro-pile system analysis software, and the software development work can be carried out according to the data flow. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings are included to provide a further understanding of the present application. They are included and constitute a part of the present application. The accompanying drawings illustrate embodiments of the present application and together with the present specification serve to explain the principles of the present invention. In the accompanying drawings:

[0019] Figure 1 It is a flow chart of a method for designing a data structure of heat pipe micro-pile system analysis software according to an embodiment of the present invention.

[0020] Figure 2 Schematic diagram of data classification according to an embodiment of the present invention.

[0021] Figure 3 4 is a schematic diagram of mapping global data and local data according to an embodiment of the present invention.

[0022] Figure 4 It is a flowchart of the entire data flow of the heat pipe micro-pile system analysis software according to an embodiment of the present invention. DETAILED DESCRIPTION

[0023] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for the description of the embodiments. Obviously, the drawings described below are only some examples or embodiments of the present application. For ordinary technicians in this field, the present application can also be applied to other similar scenarios based on these drawings without creative work. Unless it is obvious from the language environment or otherwise explained, the same reference numerals in the figures represent the same structure or operation.

[0024] Flowcharts are used in the present application to illustrate the operations performed by the system according to the embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed accurately in order. On the contrary, various steps may be processed in reverse order or simultaneously. At the same time, other operations may be added to these processes, or one or more operations may be removed from these processes.

[0025] Figure 1 FIG. 1 is a flow chart of a method for designing a data structure of heat pipe micro-pile system analysis software according to an embodiment of the present invention. Figure 1 As shown, the data structure design method 100 of the heat pipe micro-pile system analysis software includes the following steps:

[0026] Step S11: Divide the data variables involved in the system analysis software into categories according to the heat pipe micro-stack structure and data meaning.

[0027] Based on the design characteristics of the heat pipe micro-reactor and the data requirements in safety analysis, the data variables involved in the system analysis software are divided by category according to the modular software design concept. According to the structure of the heat pipe micro-reactor, it can be divided into core type, heat pipe type, main heat exchanger type, and exhaust heat exchanger type. According to the meaning of the data, it can be divided into geometry type, physics type, thermal engineering type, and control type. Combining these two division methods covers all the main data in the software operation process.

[0028] Figure 2 FIG. 1 is a schematic diagram of data classification according to an embodiment of the present invention. Figure 2 As shown in the figure, the data variables in the heat pipe micro-reactor system analysis software are divided into five main categories, namely core category, heat pipe category, main heat exchanger category, exhaust heat exchanger category and control category. The data variables in each main category are further divided into subcategories such as geometry category, physics category and thermal engineering category according to the characteristics of the data meaning. In this embodiment, the core category includes geometry category, physics category and thermal engineering category, and the heat pipe category, main heat exchanger category and exhaust heat exchanger category all include geometry category and thermal engineering category.

[0029] The meaning of each category is as follows:

[0030] Core geometry: geometric length of core components, channel adjacent relationship, etc.;

[0031] Core physics: neutron kinetic parameters and reactivity feedback parameters required for core physics calculations;

[0032] Core thermal engineering: temperature and heat transfer of core components;

[0033] Heat pipe geometry: heat pipe axial length, radial layer thickness, porosity, etc.

[0034] Heat pipe thermal engineering: heat pipe temperature, heat transfer, start position, etc.;

[0035] Main heat exchanger geometry: main heat exchanger flow area, heat exchange area, fin size, etc.;

[0036] Thermal engineering of main heat exchanger: inlet and outlet fluid temperature, heat transfer coefficient, heat transfer amount, etc. of main heat exchanger;

[0037] Exhaust heat exchanger geometry: Exhaust heat exchanger flow area, heat exchange area, fin size, etc.;

[0038] Thermal engineering of exhaust heat exchanger: inlet and outlet fluid temperature, heat transfer coefficient, heat transfer amount, flow rate, etc. of exhaust heat exchanger;

[0039] Control category: main heat exchanger and waste exhaust opening control, output control, calculation step and total time control, accident process control, etc.

[0040] The above embodiment divides the data into categories according to the heat pipe micro-repile structure and the meaning of the data. In another embodiment, the granularity of the division can be larger or smaller. For example, the core category can be further divided into fuel rod category, air gap category, matrix category, control rod category, etc.

[0041] Step S12: construct global data according to the categories, and establish local data corresponding to the global data through mapping.

[0042] The heat pipe micro-stack structure has strong symmetry and is modeled using the channel equivalence method. The data structures of different channels are the same. Therefore, an array is used as the data organization mode. In other words, global data is organized in the form of an array. Preferably, the data is organized in the form of a dynamic array. The advantages are:

[0043] 1) Fast element search by index;

[0044] 2) It is convenient to traverse the array according to the index;

[0045] 3) The number of program variables can be dynamically adjusted according to the size of the modeling scope.

[0046] In the invention, a "global-local" separated data structure is used for data partitioning. Global data is used as the input and output object of the user and stores all calculation data; in actual calculation, the mapping module first creates a mirror module of the global variable, called "local data", and then downloads the global data to the corresponding local data. Figure 3 Schematic diagram of mapping global data and local data according to an embodiment of the present invention. Figure 3 As shown, the global data includes multiple global variables, namely Global_Y1, Global_Y2, Global_Y3, ..., Global_YN. Establishing local data corresponding to the global data by mapping includes: first, establishing local variables corresponding to the global variables by the mapping module, for example, the global variable Global_Y1 is mapped to the local variable Local_Y1, the global variable Global_Y2 is mapped to the local variable Local_Y2, ... the global variable Global_YN is mapped to the local variable Local_YN. Then, the value of the global variable is copied to the value of the local variable. For example, the value of the global variable Global_Y1 is copied to the value of the local variable Local_Y1, the value of the global variable Global_YN is copied to the value of the local variable Local_YN, and so on, which will not be repeated here.

[0047] Step S13: Designing the data flow of global data and local data, including: before performing each step of transient calculation, copying the data in the global data to the local data; calculating the data in the local data to obtain the data of the next time step; transmitting the data of the next time step back to the global data.

[0048] Data flow is a process that describes the process of converting input into output after being processed by the system from the perspective of data transmission and processing. Optionally, returning the data of the next time step to the global data includes: updating the data of the next time step to the local data, and the local data maps the data of the next time step to the global data. In some embodiments, the data flow also includes: after the local data maps the data of the next time step to the global data, the local data is released. Exemplarily, for local data, it is established at the beginning of a time step and released after the mapping to the global data is completed at the end of the calculation, reducing the memory usage of the program.

[0049] Optionally, the data flow further includes: performing data checking on the data of the next time step before transmitting the data of the next time step back to the global data.

[0050] In this application, the addresses and data transmitted between the interfaces of each submodule of the logic calculation part are derived from local data, and all modification operations are also performed on local data. After the calculation cycle is completed, the mapping module uploads the updated data back to the global data. The advantages of this data structure construction method are:

[0051] 1) Prevent sub-modules from tampering with global data and protect data security;

[0052] 2) When a calculation error occurs, the erroneous data will not overwrite the last correct calculation data;

[0053] 3) Interfaces only need to pass addresses, regardless of the dimension, to ensure that the computing objects are highly abstract;

[0054] 4) Enhance the scalability of the program and reduce the impact of increasing / decreasing the amount of data on the original interface and scheduling method.

[0055] Figure 4 400 is a flow chart of the entire data flow of the heat pipe micro-pile system analysis software according to an embodiment of the present invention. The entire data flow 400 of the heat pipe micro-pile system analysis software includes:

[0056] Step S41: The software reads input data such as control parameters, heat pipe micro-stack geometric parameters, and physical thermal parameters from the input file.

[0057] In this embodiment, an input file is used as a method for importing data into the software. In other embodiments, direct input and other methods may also be used.

[0058] Step S42: The software performs a data check on the input data to ensure that there are no logical errors in the input data.

[0059] Step S43: Process the input data to construct control type, core type, heat pipe type, main heat exchanger type and residual heat exchanger type data. These five types of data together constitute the global data.

[0060] Step S44: establishing local data, the local data and the global data have the same variables, and mapping the global data to the local data;

[0061] Step S45: Control judgment, based on the set accident condition occurrence control conditions, determine whether the accident condition occurs. If yes, proceed to step S46.

[0062] Step S46: the calculation module performs numerical calculations based on local data;

[0063] Step S47: directly updating the calculation result in the local data;

[0064] Step S48: Check and map local data to global data;

[0065] Step S49: According to the setting of the control parameters, the global data is processed and output according to certain rules.

[0066] For ease of understanding Figure 4 The transmission process of the data flow in the software is described below by taking the heat pipe failure accident condition as an example to explain the transmission of the main data in the software. The content of the present invention is introduced by taking a single heat pipe failure condition as an example. This condition simulates the temperature changes of various parts of the reactor when a single heat pipe is damaged and heat cannot be extracted during normal operation of the heat pipe reactor.

[0067] First, prepare the input card, which contains the key parameters of the established heat pipe model, including the size of each reactor structure, meshing method, thermal conditions, reactor physical conditions, control conditions, etc. In this case, the control condition is the operating state of the heat pipe. That is, it is set that at a certain moment, the specified heat pipe is damaged and cannot export heat.

[0068] After the software reads the parameters in the input card, it performs a data check to check whether the input data has format errors, range errors, or data inconsistencies. For example, the input heat pipe condensation section length should be the same as the heat exchanger length, and the sum of the power of each channel should be the same as the total power.

[0069] Then, data initialization is performed to process the input data and convert it into data that directly participates in the calculation. For example, the total length and number of grids are given in the input card regarding grid division, and the length of each grid needs to be calculated. Finally, all global data is obtained according to the data class.

[0070] During the calculation process, transient calculations are performed in a time-step manner. Before each transient calculation, a copy of the global data is made, called local data, and the calculation is performed using the local data. For example, if there is a T Global，基体，n , create a T Local，基体，n and assign the same value.

[0071] According to the set heat pipe failure control conditions, determine whether the heat pipe failure occurs at the current time step and obtain the failure position. For the simulation of heat pipe failure conditions, it is considered that the heat pipe cannot bear the function of heat extraction. The heat transfer from the substrate to the heat pipe wall is zero. For the transient temperature differential control equation:

[0072] ρc p VT' Local，基体，n =Q IN -Q OUT (1)

[0073] Where ρ is the density, c o is the specific heat capacity, V is the volume, T Local，基体，n is the temperature of the substrate at the current time step. In the control volume where the substrate is close to the wall of the heat pipe, the heat cannot be exported, and the value of QOUT is set to 0; in the control volume where the wall of the heat pipe is close to the substrate, the heat cannot enter the control volume, and the value of QOUT is set to 0. IN is 0.

[0074] Then, a suitable numerical calculation method is used to perform numerical calculations based on the current local data to obtain the value of the next time step and update it into the local data. Take the explicit integration method as an example:

[0075] T Local，基体，n+1 =aT Local，基体，n +hbT' Local，基体，n (2)

[0076] Among them, a and b are coefficients related to the integration method, h is the integration step size, and T Local，基体，n+1 is the temperature of the substrate in the next time step, T Local，基体，n is the temperature of the matrix at the current time step.

[0077] In order to prevent the calculation from failing due to severe working conditions or other reasons, the returned data will be tampered with the correct data. Before the local data is returned to the global data, the local data T Local，基体，n+1 Check the data to see if there is a "not a number" value (NaN) or an "infinite" value (inf). If so, do not pass the data for the next time step back to the global data. When the local data is passed back to the global data, the calculation of a time step is completed. The global data T Global，基体，n Successfully updated to the value T of the next time stepGlobal，基体，n+1 . At this point, data processing and output can be performed as needed.

[0078] The calculated temperature changes of the fuel rods, matrix and other parts of the core after a heat pipe failure accident can be used to compare whether the temperatures of these key parts exceed the safety limit, which can be used to analyze whether the current design meets safety requirements.

[0079] In the above embodiments, all global data have a corresponding local data. However, some data do not actually change during the calculation process, such as some geometric parameters of the reactor. Therefore, the "global-local" data structure may not be used for the geometric parameters to reduce the overall data volume of the program.

[0080] The data structure design method of the heat pipe micro-pile system analysis software of the present invention divides all parameters into categories according to the structure and data meaning of the heat pipe micro-pile, which is convenient for management and reference; adopts the data structure of "global data-local data" to avoid sub-modules from tampering with global data and protect data security; and designs a data flow suitable for the heat pipe micro-pile system analysis software, and software development work can be carried out based on the data flow.

[0081] The basic concepts have been described above. Obviously, for those skilled in the art, the above invention disclosure is only used as an example and does not constitute a limitation of the present application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements and amendments to the present application. Such modifications, improvements and amendments are suggested in the present application, so such modifications, improvements and amendments still belong to the spirit and scope of the exemplary embodiments of the present application.

[0082] At the same time, the present application uses specific words to describe the embodiments of the present application. For example, "one embodiment", "an embodiment", and / or "some embodiments" refer to a certain feature, structure or characteristic related to at least one embodiment of the present application. Therefore, it should be emphasized and noted that "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more in different positions in this specification does not necessarily refer to the same embodiment. In addition, some features, structures or characteristics in one or more embodiments of the present application can be appropriately combined.

[0083] Some aspects of the present application may be performed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above hardware or software may be referred to as "data blocks", "modules", "engines", "units", "components" or "systems". The processor may be one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or combinations thereof. In addition, various aspects of the present application may be expressed as computer products located in one or more computer-readable media, which include computer-readable program codes. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, tapes ...), optical disks (e.g., compact disks CDs, digital versatile disks DVDs ...), smart cards, and flash memory devices (e.g., cards, sticks, key drives ...).

[0084] A computer-readable medium may include a propagated data signal containing computer program code, such as in baseband or as part of a carrier wave. The propagated signal may have a variety of manifestations, including electromagnetic, optical, etc., or a suitable combination. A computer-readable medium may be any computer-readable medium other than a computer-readable storage medium, which may be connected to an instruction execution system, device or apparatus to communicate, propagate or transmit a program for use. The program code on the computer-readable medium may be propagated via any suitable medium, including radio, cable, fiber optic cable, radio frequency signal, or similar medium, or any combination of the above mediums.

[0085] Similarly, it should be noted that in order to simplify the description of the disclosure of this application and thus help understand one or more embodiments of the invention, in the above description of the embodiments of this application, multiple features are sometimes combined into one embodiment, figure or description thereof. However, this disclosure method does not mean that the features required by the object of this application are more than the features mentioned in the claims. In fact, the features of the embodiments are less than all the features of the single embodiment disclosed above.

[0086] As shown in this application and claims, unless the context clearly indicates an exception, the words "a", "an", "an" and / or "the" do not refer to the singular and may also include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0087] Unless otherwise specifically stated, the relative arrangement, numerical expressions and numerical values ​​of the parts and steps set forth in these embodiments do not limit the scope of the present application. At the same time, it should be understood that, for ease of description, the sizes of the various parts shown in the accompanying drawings are not drawn according to the actual proportional relationship. The technology, method and equipment known to those of ordinary skill in the relevant field may not be discussed in detail, but in appropriate cases, the technology, method and equipment should be considered as a part of the authorization specification. In all examples shown and discussed here, any specific value should be interpreted as being merely exemplary, rather than as a limitation. Therefore, other examples of exemplary embodiments may have different values. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so that once a certain item is defined in an accompanying drawing, it does not need to be further discussed in subsequent drawings.

[0088] In addition, it should be noted that the use of words such as "first" and "second" to define components is only for the convenience of distinguishing the corresponding components. If not otherwise stated, the above words have no special meaning and cannot be understood as limiting the scope of protection of this application. In addition, although the terms used in this application are selected from well-known and commonly used terms, some terms mentioned in the specification of this application may be selected by the applicant at his or her discretion, and their detailed meanings are explained in the relevant parts of the description of this article. In addition, it is required to understand this application not only by the actual terms used, but also by the meaning implied by each term.

[0089] Although the present application has been described with reference to the current specific embodiments, ordinary technicians in this technical field should recognize that the above embodiments are only used to illustrate the present application, and various equivalent changes or substitutions may be made without departing from the spirit of the present application. Therefore, as long as the changes and modifications to the above embodiments are within the essential spirit of the present application, they will fall within the scope of the claims of the present application.

Claims

1. A data structure design method for heat pipe micro-pile system analysis software, characterized in that: include: The data variables involved in the system analysis software are divided into categories according to the heat pipe micro-pile structure and data meaning; Constructing global data according to the categories, and establishing local data corresponding to the global data through mapping; Designing the data flow of the global data and the local data includes: before performing each step of transient calculation, copying the data in the global data to the local data; Calculate the data in the local data to obtain the data of the next time step; and transmit the data of the next time step back to the global data.

2. The data structure design method according to claim 1, characterized in that: According to the heat pipe micro-pile structure and data meaning, the data variables involved in the system analysis software are divided into categories, including: Dividing the data variables into a first category according to the heat pipe micro-reactor structure, the first category including a core category, a heat pipe category, a main heat exchanger category, and a residual heat exchanger category; Dividing the data variables into second categories according to the meaning of the data, the second categories including geometry, physics, thermal engineering, and control; The first category and the second category are combined to obtain a final category.

3. The data structure design method according to claim 2, characterized in that: The final category includes five main categories, namely core category, heat pipe category, main heat exchanger category, exhaust heat exchanger category and control category. The core category includes geometry category, physics category and thermal engineering category, and the heat pipe category, main heat exchanger category and exhaust heat exchanger category all include geometry category and thermal engineering category.

4. The data structure design method according to claim 1, characterized in that: Transmitting the data of the next time step back to the global data includes: updating the data of the next time step to the local data, and the local data maps the data of the next time step to the global data.

5. The data structure design method according to claim 4, characterized in that: The data flow further includes: after the local data maps the data of the next time step to the global data, the local data is released.

6. The data structure design method according to claim 1, characterized in that: The data flow further includes: performing data checking on the data of the next time step before transmitting the data of the next time step back to the global data.

7. The data structure design method according to claim 6, characterized in that: Performing data checking on the data of the next time step includes: It is determined whether the data of the next time step has a "not a number" value or an "infinity" value. If so, the data of the next time step is not returned to the global data.

8. The data structure design method according to claim 1, characterized in that: The data flow also includes: using the global data to input and output data.

9. The data structure design method according to any one of claims 1 to 8, characterized in that: The global data and the local data are organized in the form of arrays.

10. The data structure design method according to claim 9, characterized in that: The array is a dynamic array.

Images