Multi-physics field problem solving method
By adopting the common keyword and hierarchical data format HDF5 in the multi-physics solver system, the expansion and loading problems caused by the differences in the data format of different physics are solved, and the loosely coupled expansion and loading of the multi-physics solver system is realized. , improves the solution efficiency and system scalability.
Patent Information
- Application Number
- CN202411069474.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-05
- Publication Date
- 2025-01-03
AI Technical Summary
The data format differences in different physics hinder the expansion and loading of multi-physics solver systems, limiting their application in the era of Industrial Manufacturing 4.0.
Use common keywords to define common settings information between multiple physics fields, and build a computing model through the first data format (including model keywords, analysis step keywords, global parameter keywords and grid keywords), supporting loosely coupled expansion and Load, use the hierarchical data format HDF5 to store grid-related data.
The general data format of the multi-physics solver system is realized, which improves the solution efficiency of multi-physics problems and the scalability of the system, and supports loosely coupled expansion and loading between different physics fields.
Smart Images
Figure CN119249683A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computational simulation technology, and in particular to a method for solving multi-physics field problems. Background Art
[0002] With the advent of the Industrial Manufacturing 4.0 era, digitalization has become the core key to enabling industrial manufacturing companies to upgrade, and industrial software is the core foundation supporting this transformation. For example, multi-physics solver systems (taking computer aided engineering (CAE) systems as an example) can be used to solve complex multi-physics problems. However, if the data formats of different physical fields are different, this will hinder the expansion and loading of multi-physics solver systems. Summary of the invention
[0003] An embodiment of the present application provides a method for solving multi-physics field problems.
[0004] In a first aspect, an embodiment of the present application provides a method for solving a multi-physics field problem, the method comprising:
[0005] Read the solver input file, which includes simulation data of multi-physics fields;
[0006] Build a computational model based on simulation data in the solver input file;
[0007] Solve multiphysics problems based on simulation data in solver input files;
[0008] The format of the simulation data is a first data format, and the first data format includes common keywords, which are used to represent the common simulation data of the multi-physical fields, and the common keywords include:
[0009] The first model keyword is used to represent the basic information of the model for solving multi-physics problems;
[0010] The first analysis step keyword is used to indicate the analysis steps and their sequence for solving multi-physics problems;
[0011] The first global parameter keyword is used to represent the global physics related parameters for solving multi-physics problems;
[0012] The first grid keyword is used to represent grid-related data for solving multi-physics field problems. The storage format of the grid-related data is the hierarchical data format HDF5.
[0013] Optionally, the first model keyword includes:
[0014] The first name keyword is used to indicate the name of the model;
[0015] The first version keyword is used to indicate the version of the model;
[0016] The first timestamp keyword is used to indicate the timestamp of the model;
[0017] The first dimension keyword is used to indicate the highest solution dimension of the model;
[0018] The first physics keyword is used to indicate the multiphysics involved in the model.
[0019] Optionally, the first analysis step keywords include:
[0020] The first entry point keyword is used to indicate the ID of the first analysis step to start;
[0021] The first sub-analysis step keyword is used to indicate the basic information of a single analysis step.
[0022] Optionally, the first sub-analysis step keywords include:
[0023] The first analysis step ID keyword is used to indicate the ID of a single analysis step;
[0024] The first analysis step name keyword is used to indicate the name of a single analysis step;
[0025] The first next analysis step keyword is used to represent all possible analysis step IDs of the next step of a single analysis step;
[0026] The first analysis step type keyword is used to indicate the type of a single analysis step.
[0027] Optionally, the first sub-analysis step keyword also includes a keyword used to represent information related to the analysis step logic, and the information related to the analysis step logic is determined by the first analysis step type keyword.
[0028] Optionally, the first global parameter keyword includes:
[0029] The first gravity acceleration keyword is used to indicate the magnitude of gravity acceleration;
[0030] The first unit keyword is used to indicate the size relationship between the current unit system and the international unit system. The current unit system is calculated based on one or more international units.
[0031] Optional first-order unit keywords include:
[0032] The first coefficient keyword is used to indicate that the coefficient of the currently used unit system is calculated using the units in the International System of Units;
[0033] The first offset keyword is used to indicate the offset of the current unit system compared to the product of the unit and coefficient in the International System of Units.
[0034] Optionally, the first grid keyword includes:
[0035] The first coordinate keyword is used to represent the coordinates of the unit nodes in the grid-related data;
[0036] The first unit keyword is used to represent the basic information of the unit in the grid-related data;
[0037] The first set keyword is used to represent the set of elements used to solve the multiphysics problem.
[0038] Optionally, the first unit keywords include:
[0039] The first unit type keyword is used to indicate the type of each basic unit that constitutes the unit;
[0040] The first unit node keyword is used to represent the node array of each basic unit in the component unit;
[0041] The first unit starting offset keyword is used to indicate the index range of the nodes of each basic unit in the component unit in the array.
[0042] Optionally, the first data format also includes physical field-specific keywords, where the physical field-specific keywords are used to represent specific information of different physical fields.
[0043] Based on the multi-physics field problem solving method of the present application, common setting information between different physical fields is defined by using common keywords in the first data format, which can effectively support loosely coupled expansion and loading of a general multi-physics field solver system. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for describing the embodiments are briefly introduced below.
[0045] Figure 1 It is a schematic flowchart of the multi-physics field problem solving method provided in an embodiment of the present application.
[0046] Figure 2 It is an example diagram of a unit in the multi-physics field solver system provided in an embodiment of the present application.
[0047] Figure 3 This is an example diagram of the multi-physical field synchronous coupling method provided in an embodiment of the present application. DETAILED DESCRIPTION
[0048] The technical solution of the embodiment of the present invention will be described below in conjunction with the accompanying drawings in the embodiment of the present invention.
[0049] With the advent of the era of industrial manufacturing 4.0, digitalization has become the core key to empowering industrial manufacturing enterprises to upgrade, and industrial software is the core foundation to support this transformation and has become a new pearl in the field of industrial manufacturing. With the continuous development and evolution of software engineering standards, large-scale software must have a software architecture system with high cohesion, loose coupling, plug-in, and full test coverage, and be built in accordance with the basic SOLID software design principles such as the single responsibility principle (SRP), open close principle (OCP), Liskov substitution principle (LSP), interface segregation principle (ISP), and dependency inversion principle (DIP). Only in this way can the readability, scalability, reusability, portability, maintainability, and testability of the software be fully guaranteed, and the systematic development of software can be supported. For example, a multi-physics solver system (taking the CAE system as an example) can be used to solve complex multi-physics problems. However, if the data formats of different physical fields are different, this will hinder the expansion and loading of the multi-physics solver system.
[0050] Based on this, the embodiment of the present application provides a method for solving a multi-physics problem. As an example, the method can be used in a multi-physics solver system. Figure 1 As shown, the method includes steps S110-S130.
[0051] In step S110, the solver input file is read. The solver input file is a key file used by the multi-physics solver system for simulation analysis. For example, if the solver system is CAE software, the solver input file can be an input file generated by the Poisson CAE software pre-processing module. The solver input file may include simulation data of multiple physical fields (such as structural fields, fluid fields, etc.), such as common data of multiple physical fields or special data of each physical field. As an example, the common data of multiple physical fields can be information such as unit system and physical grid data.
[0052] In step S120, a computational model is constructed according to the simulation data in the solver input file. For example, constructing the computational model may involve constructing mesh data in a computer memory, including loading mesh node data, loading unit topology relationships, and the like.
[0053] In step S130, a multi-physics problem is solved based on the simulation data in the solver input file. The multi-physics problem may include static equilibrium problems, modal analysis, dynamic problems, etc. of the structure.
[0054] Among them, the format of the simulation data is a first data format, the first data format includes common keywords, the common keywords are used to represent the common simulation data of the multi-physical fields, and the common keywords may include a first model keyword, a first analysis step keyword, a first global parameter keyword, and a first grid keyword.
[0055] Among them, the first model keyword can be used to represent the basic information of the model for solving multi-physics problems, such as the name and version of the model. The first analysis step keyword can be used to represent the analysis steps and their sequence for solving multi-physics problems. The first global parameter keyword can be used to represent the global physics-related parameters for solving multi-physics problems, such as gravity acceleration. The first grid keyword can be used to represent grid-related data for solving multi-physics problems. The storage format of grid-related data can be a hierarchical data format (hierarchical data formal, also known as HDF5).
[0056] It is worth noting that the above-mentioned first data format can be used as a universal data format for a multi-physics field solver system.
[0057] Based on the multi-physics field problem solving method of the present application, common setting information between different physical fields is defined by using common keywords in the first data format, which can effectively support loosely coupled expansion and loading of a general multi-physics field solver system.
[0058] Optionally, the first model keyword may include a first name keyword, a first version keyword, a first timestamp keyword, a first dimension keyword, and a first physical field keyword. Among them, the first name keyword can be used to represent the name of the model, and the first version keyword can be used to represent the version of the model. The first timestamp keyword can be used to represent the timestamp of the model, such as the timestamp of model creation, the timestamp of model modification, etc. The first dimension keyword can be used to represent the highest solution dimension of the model, such as 3 dimensions. The first physical field keyword can be used to represent the multiple physical fields involved in the model, such as multi-body fields, fluid fields, etc. The main program of the solver can dynamically load the dynamic library of the same name at runtime according to the keywords in the first physical field keyword. Based on the first model keyword, the detailed information of the model can be represented, which helps to improve the efficiency of solving multi-physical field problems.
[0059] Optionally, the first analysis step keyword may include a first entry point keyword and a first sub-analysis step keyword. Among them, the first entry point keyword can be used to represent the identity (identity, ID) of the first analysis step started. It is worth noting that the number of the first analysis step started is not limited. If the first analysis step started includes multiple analysis steps, the order between these multiple analysis steps is not limited. The first sub-analysis step keyword can be used to represent the basic information of a single analysis step, such as the ID, name, next analysis step, etc. of the analysis step. Based on the first analysis step keyword, the analysis steps and their order can be represented, which helps to improve the efficiency of solving multi-physics field problems.
[0060] Optionally, the first sub-analysis step keyword may include a first analysis step ID keyword, a first analysis step name keyword, a first next analysis step keyword, and a first analysis step type keyword. Among them, the first analysis step ID keyword can be used to represent the ID of a single analysis step. The first analysis step name keyword can be used to represent the name of a single analysis step. The first next analysis step keyword can be used to represent all possible analysis step IDs of the next step of a single analysis step, and whether to execute the next analysis step is controlled by the current single analysis step. If the next analysis step keyword is empty, it means that there is no next analysis step. The first analysis step type keyword can be used to represent the type of a single analysis step, which is processed by a specific physical field library. As an example, the naming rule of the first analysis step type keyword can be determined by the "physical field type + physical analysis type" of a single analysis step. Taking "MSDynamics" as an example, "MS" represents Multibody Simulation, that is, multi-body analysis, and "Dynamics" represents dynamic analysis, then the analysis type represented by "MSDynamics" is multi-body dynamic analysis. Based on the first sub-analysis step keyword, the basic information of a single analysis step can be represented, which helps to improve the efficiency of solving multi-physics field problems.
[0061] Optionally, the first sub-analysis step keyword may also include keywords that can be used to represent analysis step logic-related information, and the analysis step logic-related information is determined by the first analysis step type keyword. For example, the analysis step logic-related information may be analysis step-related parameters, such as the start time and end time required for dynamic analysis. The analysis step logic-related information may be processed by the physical field library corresponding to the first analysis step type keyword. Through this mechanism, some complex analysis step execution logic can be implemented. For example, different methods of multi-physical field weak coupling can be implemented through this mechanism.
[0062] Optionally, the first global parameter keyword may include a first gravity acceleration keyword and a first system of units keyword. Among them, the first gravity acceleration keyword can be used to indicate the magnitude of gravity acceleration. The first system of units keyword can be used to indicate the magnitude relationship between the currently used system of units and the international system of units, and the currently used system of units can be calculated by one or more of the international systems of units. The international system of units can be international systems of units such as time, length, mass, temperature, mole, current intensity, and light intensity. For example, if the mass system of units currently used is pounds in a non-international system of units, then the first system of units keyword can indicate the magnitude relationship between pounds and kilograms. Based on the first global parameter keyword, global physics field related parameters for solving multi-physics field problems can be represented, thereby helping to improve the efficiency of solving multi-physics field problems.
[0063] Optionally, the first system of units keyword may include a first coefficient keyword and a first offset keyword. Among them, the first coefficient keyword can be used to indicate the use of the units in the International System of Units to calculate the coefficients of the currently used system of units. The first offset keyword can be used to indicate the offset of the currently used system of units compared to the product of the units in the International System of Units and the above coefficients. For example, 1 pound = 0.45392 kilograms, then the value of the first coefficient keyword corresponding to the mass is 0.45392, and the value of the first offset keyword is 0. Based on the first system of units keyword, the size relationship between the first currently used system of units and the International System of Units can be expressed, which helps to improve the efficiency of solving multi-physics field problems.
[0064] Optionally, the first grid keyword may include a first coordinate keyword, a first unit keyword, and a first set keyword. Among them, the first coordinate keyword can be used to represent the coordinates of the unit nodes in the grid-related data. The first unit keyword can be used to represent the basic information of the unit in the grid-related data, such as the unit type, the nodes that make up the unit, etc. The first set keyword can be used to represent the unit set used to solve multi-physics field problems. Based on the first grid keyword, the grid-related data for solving multi-physics field problems can be represented, which helps to improve the efficiency of solving multi-physics field problems.
[0065] Optionally, the first unit keyword may include a first unit type keyword, a first unit node keyword, and a first unit start offset keyword. The first unit type keyword may be used to indicate the type of each basic unit that constitutes the unit. Figure 2 Taking the unit shown in the figure as an example, the basic unit types that make up the unit are all two-node beam units. It is worth noting that the naming method of the basic unit type is not limited and can be defined by yourself. As an example, it can be named by a 3-digit Arabic array, such as 202 to represent a two-node beam unit. The first unit node keyword can be used to represent the node array of each basic unit in the component unit, such as Figure 2 The node array of each basic unit in the unit shown is [0,1,1,2,2,3]. The first unit starting offset keyword can be used to indicate the index range of the nodes of each basic unit in the constituent unit in the above node array, as Figure 2 Taking the unit shown in the figure as an example, the index ranges of the nodes that make up each unit in the above node array are [0,2), [2,4), [4,6) respectively, so the first unit starting offset keyword can be expressed as [0,2,4,6]. Based on the first unit keyword, the basic information of the unit in the grid-related data can be expressed, which helps to improve the efficiency of solving multi-physics field problems.
[0066] Optionally, the first data format may further include physical field-specific keywords, which may be used to represent specific information of different physical fields. For example, for a multi-body physical field, it may include body, marker, force, etc. Based on the physical field-specific keywords, it may be used to represent specific information of the physical field, thereby helping to adapt to the needs of different physical fields.
[0067] Combine the following Figure 1 and Figure 2 , taking the multi-physics solver system as a CAE system as an example, the first data format in the multi-physics problem solving method of the embodiment of the present application is introduced by example. As an example, the first data format can be defined as follows, and the first data format definition can generally adopt the JavaScript object notation (json) file format.
[0068]
[0069] Among them, the common module keywords include the "Model" keyword, the "Simulation" keyword, the "GlobalParams" keyword, and the "Mesh" keyword. The "Model" keyword is the first model keyword, the "Simulation" keyword is the first analysis step keyword, the "GlobalParams" keyword is the first global parameter keyword, and the "Mesh" keyword is the first mesh keyword. The "Multibody" and "Fluid" keywords are the physical field-specific keywords for multi-body fields and fluid fields, respectively.
[0070] "Model" keyword
[0071] Exemplarily, the format of the "Model" keyword may be defined as follows.
[0072]
[0073]
[0074] The "Model" keyword defines the basic information of the multi-physics model, where "ModelName" represents the first name keyword, which is used to specify the model name, such as "doublepeduluen". "Version" represents the first version keyword, which specifies the model version, such as version 1.0.0. "Timestamp" represents the first timestamp keyword, which is used to specify the timestamp of the model. "Create" and "Modified" specify the timestamps of model creation and modification, respectively. "Dimension" represents the first dimension keyword, which is used to specify the highest dimension to be solved. "PhysicsField" represents the first physical field keyword, which is used to explicitly specify the multi-physics fields involved in the current solution model. The main program of the general solver will dynamically load the dynamic library with the same name at runtime based on the keywords.
[0075] "Simulation" keyword
[0076] Exemplarily, the format of the "Simulation" keyword may be defined as follows.
[0077]
[0078]
[0079] The "Simulation" keyword is used to specify the analysis steps and their sequence, where "EntryPoints" represents the first entry point keyword, specifying that the IDs of the first analysis steps are 2 and 3. "1", "2", "3", and "4" are the first sub-analysis step keywords of the analysis steps with IDs 1, 2, 3, and 4, respectively, and are used to represent the basic information of a single analysis step. The format can be defined as follows.
[0080]
[0081] The keyword "Id" is the first analysis step ID keyword, which specifies the ID keyword of this analysis step. The keyword "Name" is the first analysis step name keyword, which specifies the name of this analysis step. The keyword "NextStep" is the first next analysis step keyword, which is used to specify all possible analysis step IDs for the next step. Whether to execute the next analysis step is controlled by the current analysis step. If there is no such keyword, there is no next analysis step. The keyword "SimType" is the first analysis step type keyword, which specifies the analysis step type and is handled by the specific physical field library. In terms of naming rules, the analysis step type can be composed of "physical field type abbreviation" + "specific analysis type". Taking "MSDynamics" as an example, "MS" means Multibody Simulation, that is, multi-body dynamics simulation analysis, and "Dynamics" means dynamics analysis. The analysis type represented by "MSDynamics" is multi-body dynamics analysis.
[0082] The first sub-analysis step keyword can also contain other information, that is, information related to the analysis step logic. The type of this information is determined by "SimType" and is processed by the physical field library corresponding to "SimType". Through this mechanism, some complex analysis step execution logic can be implemented. For example, different ways of multi-physics weak coupling can be implemented through this mechanism.
[0083] "GlobalParams" keyword
[0084] Exemplarily, the format of the "GlobalParams" keyword may be defined as follows.
[0085]
[0086] The "GlobalParams" keyword is used to specify some global physical field related parameters, among which "Gravity" is the first gravity acceleration keyword, which specifies the magnitude of gravity acceleration. "UnitSys" is the first unit system keyword, which specifies the unit system information. It is two arrays of length 7 ("factor" and "offset"), which are used to describe the relationship between the current unit system and the seven international units of time, length, mass, temperature, mole, current intensity, and light intensity. "factor" is the first coefficient keyword, which is used to indicate that the coefficient of the current unit system is calculated using the units in the international system of units. "offset" is the first offset keyword, which is used to indicate the offset of the current unit system compared to the product of the units and coefficients in the international system of units. Based on "factor" and "offset", the size of the current unit system is calculated as follows.
[0087] The current unit size = factor * SI size + offset
[0088] For example, 1 pound = 0.45392 kilograms, so the corresponding factor for mass is 0.45392, and offset is 0; 1 degree Celsius = 1 Kelvin -273.15, so the corresponding factor for temperature is 1, and offset is -273.15. Non-SI units that appear in input and output files can be composed of one or more of the seven SI units listed above.
[0089] "Mesh" keyword
[0090] Exemplarily, the format of the "Mesh" keyword can be defined as follows, and the definition format of its data is similar to json.
[0091] Grid-related data is characterized by large scale. To improve the efficiency of loading large-scale data, this type of data can be stored in HDF5 format.
[0092]
[0093] "Coordinates": [1., 2.,],
[0094] "Elements": {
[0095] "ElementsType":[202,202,202...],
[0096] "ElementStartOffset":[0,2,4...],
[0097] "ElementConnection":[0,1,1,2,3,2...]
[0098] },
[0099] "Set":[1,4,3...]
[0100] }
[0101] The "Coordinates" array stores the coordinates of the unit nodes, and the "Elements" array stores unit-related information. Figure 2 Take the beam element shown in the figure as an example. "Coordinates" stores the coordinates of the four nodes 0, 1, 2, and 3. For three-dimensional coordinates, the array length is 4x3=12. "ElementsType" stores the type of the basic element, and the array length is equal to the number of elements. For example, the number 202 represents a two-node beam element. Figure 2There are three beam elements in total, so the data stored in "ElementsType" is [202,202,202]. Since in actual storage, the grid data is stored in HDF5 compression format, the data stored in "ElementType" has the characteristic of high probability. Compared with the original data before compression, the actual data storage scale after compression has a better compression ratio, and the actual space occupied is not large. "ElementConnection" is used to store which nodes the basic unit in the current unit is composed of. Figure 2 The corresponding array data is: [0,1,1,2,2,3]. "ElementStartOffset" is used to store the starting position of the node number that constitutes the basic unit in the "ElementConnection" array, which is the number of units plus 1. The corresponding array in the above figure is: [0,2,4,6]. Taking the second unit stored in the grid as an example, the type of the second unit is determined by the second number of the ElementsType array (index starts from 0 and index is 1) 202. The index starting position of the nodes that constitute the second unit is determined by the second and third numbers in the "ElementStartOffset" array. The index range of the nodes that constitute the second unit is [2,4). According to this range, the second and third numbers are obtained in the "ElementConnection" array: 1, 2. Through the two numbers in "ElementConnection", it can be determined that the second unit is composed of node 1 and node 2. The "Set" keyword is the first set keyword, which is used to represent the unit set used to solve multi-physics field problems.
[0102] Combine the following Figure 3 , an example is given to introduce the multi-physics field synchronous coupling method implemented by the "Simulation" keyword. For example, Figure 3 The corresponding data blocks for the "Simulation" keyword are as follows.
[0103]
[0104] In the above data block, two analysis steps A and B are defined. After the program starts, according to the analysis step ID specified in "EntryPoints": [1,2], analysis steps A and B are used as the entry points for analysis step execution, and the two analysis steps A and B are executed synchronously. After the end of analysis step A or B, you can choose whether to execute the next analysis step based on the execution status of the current analysis step.
[0105] In the specific implementation, taking fluid-solid coupling as an example, analysis step A is fluid dynamics analysis, and analysis step B is structural mechanics analysis. When the calculation reaches time tn, the current structural and fluid mechanics analysis starts at the same time. Generally speaking, the structural mechanics analysis will first calculate to time tn+1, end the calculation of the current analysis step, and send the calculation results of this analysis step to the fluid analysis step. After sending the calculation results, since the calculation of the fluid analysis step has not yet ended, waiting for the completion of the current analysis step calculation of the fluid will enter the calculation of time tn+1.
[0106] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.
[0107] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.
[0108] As used in the specification and appended claims of this application, the term "if" can be interpreted as "when" or "uponce" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "uponce it is determined" or "in response to determining" or "uponce [described condition or event] is detected" or "in response to detecting [described condition or event]", depending on the context.
[0109] In addition, in the description of the present application specification and the appended claims, the terms "first", "second", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.
[0110] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.
Claims
1. A method for solving multi-physics field problems, characterized in that: The method comprises: Reading a solver input file, wherein the solver input file includes simulation data of multiple physical fields; constructing a computational model based on the simulation data in the solver input file; solving a multiphysics problem based on simulation data in the solver input file; The format of the simulation data is a first data format, and the first data format includes common keywords, and the common keywords are used to represent the common simulation data of the multi-physical fields, and the common keywords include: A first model keyword, used to represent basic information of a model for solving the multi-physics field problem; The first analysis step keyword is used to indicate the analysis steps and their sequence for solving the multi-physics problem; A first global parameter keyword, used to represent global physics field related parameters for solving the multi-physics field problem; The first grid keyword is used to represent grid-related data for solving the multi-physics field problem, and the storage format of the grid-related data is the hierarchical data format HDF5.
2. The method according to claim 1, characterized in that: The first model keywords include: A first name keyword, used to indicate the name of the model; A first version keyword, used to indicate the version of the model; A first timestamp keyword, used to represent the timestamp of the model; The first dimension keyword is used to indicate the highest solution dimension of the model; The first physics field keyword is used to indicate the multiple physics fields involved in the model.
3. The method according to claim 2, characterized in that The keywords of the first analysis step include: The first entry point keyword is used to indicate the ID of the first analysis step to start; The first sub-analysis step keyword is used to indicate the basic information of a single analysis step.
4. The method according to claim 3, characterized in that The first sub-analysis step keywords include: The first analysis step ID keyword is used to represent the ID of the single analysis step; The first analysis step name keyword is used to indicate the name of the single analysis step; A first next analysis step keyword, used to represent all possible analysis step IDs of the next step of the single analysis step; The first analysis step type keyword is used to indicate the type of the single analysis step.
5. The method according to claim 4, characterized in that The sub-analysis step keyword also includes a keyword for representing information related to analysis step logic, and the information related to analysis step logic is determined by the first analysis step type keyword.
6. The method according to claim 5, characterized in that The first global parameter keyword includes: The first gravity acceleration keyword is used to indicate the magnitude of gravity acceleration; The first unit keyword is used to indicate the size relationship between the currently used unit system and the international unit system, and the currently used unit system is calculated by one or more of the international units.
7. The method according to claim 6, characterized in that The first unit system keywords include: A first coefficient keyword, used to indicate that the coefficient of the currently used unit system is calculated using the units in the international unit system; The first offset keyword is used to represent the offset of the currently used unit system compared to the product of the unit in the international unit system and the coefficient.
8. The method according to claim 7, characterized in that The first grid keywords include: A first coordinate keyword, used to represent the coordinates of the unit nodes in the grid-related data; A first unit keyword, used to represent basic information of a unit in the grid-related data; The first set keyword is used to represent the unit set used to solve the multi-physics field problem.
9. The method according to claim 8, characterized in that The first unit keywords include: The first unit type keyword is used to indicate the type of each basic unit constituting the unit; The first unit node keyword is used to represent the node array that constitutes each basic unit in the unit; The first unit starting offset keyword is used to indicate the index range of the nodes constituting each basic unit in the unit in the array.
10. The method according to claim 9, characterized in that The first data format also includes physical field-specific keywords, and the physical field-specific keywords are used to represent specific information of different physical fields.