Data type deduction method for flight control system design model simulation

Abstract

The invention belongs to the technical field of flight control system design model simulation, and particularly relates to a data type deduction method for flight control system design model simulation. By deducing and detecting the data type of the design model, the deterministic data type is provided for all ports of the design model, and the reliability and safety of the design model in the current design and development process of the model-based flight control system are improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of flight control system design model simulation, and in particular refers to a data type deduction method for flight control system design model simulation. Background Art

[0002] As a safety-critical and complex system, the flight control system is gradually changing from manual code development to model-based design and automatic code generation. Compared with the former, model-based design can assist designers to complete the design work more quickly and iterate repeatedly. In addition, the design model is more readable and easier to maintain than the code.

[0003] As a safety-critical system, the flight control system requires the highest level of development assurance level A in civil aircraft scenarios, that is, the probability of a catastrophic accident is less than 10. -9 . Therefore, when designers are developing, the flight control system model design needs to have stronger certainty and stability than the ordinary model design. Among them, the certainty and immutability of data types is an important aspect. In ordinary designs, floating point numbers can often be converted to integers, or 16-bit integers can be converted to 8-bit integers at will. However, this type of simplification may cause valid data bits to be truncated, thereby affecting the expected output; conversely, arbitrarily expanding Boolean values ​​to integers, or converting 16-bit floating point numbers to 32-bit floating point numbers, the simulator and compiler may introduce meaningless random number padding, resulting in unexpected calculation results. Summary of the invention

[0004] Purpose of the invention: The present invention provides a data type deduction method for flight control system design model simulation. By deducing and detecting the data type of the design model, a deterministic data type is provided for all ports of the design model, so as to improve the reliability and safety of the design model in the current model-based flight control system design and development process.

[0005] Technical solution:

[0006] A data type deduction method for flight control system design model simulation, comprising:

[0007] S1, parse the design model, obtain all module attribute configurations and connection relationships; define port data type requirements for different types of modules; define data type priorities as a basis for data deduction;

[0008] S2, starting from the port with the determined data type, determine the data type of the associated port according to the connection relationship. When the data types of the ports at both ends of the same connection are inconsistent, report the conflict and jump to S5;

[0009] S3, for the module whose input port data types have been determined, check whether the input data port data type conflicts with the module attribute configuration according to the module attribute configuration, if there is no conflict, determine the data type of the associated output port, otherwise jump to S5;

[0010] S4, judging whether the port data types of all modules in the design model have been determined, if they have been determined, the analysis ends; otherwise, repeating steps S2 and S3 until the port data types of all modules in the design model have been determined.

[0011] S5: Terminate the simulation process, report the design model conflict problem and the port location where the conflict occurs, and the analysis ends.

[0012] Furthermore, step S1 specifically includes:

[0013] By parsing the model configuration file, the modules and their attribute information of all hierarchical systems are extracted, and the connection relationship of all modules is extracted.

[0014] Furthermore, step S1 specifically includes:

[0015] Extract all subsystem modules and organize the subsystems hierarchically to form a tree data structure with the top-level system of the model as the root node;

[0016] Use the depth-first search algorithm to traverse the tree data structure and obtain the module data flow connection relationship;

[0017] The data flow relationship within the subsystem is analyzed normally according to the ordinary design model, and the data flow relationship at the subsystem boundary is flattened.

[0018] Furthermore, step S1 specifically includes:

[0019] When there are subsystems in the design model, the subsystems are flattened; the port type of the module outside the subsystem is directly associated with the input port data type inside the subsystem through a connection relationship; the output port data type of the subsystem is associated with the relevant module according to the connection relationship of the output port outside the subsystem.

[0020] Furthermore, the processing in S2 includes: starting from the port of known data type, there are the following three cases:

[0021] S201, during initialization, check whether all input module data types in the design model have been defined. If there are undefined model input modules, prompt the designer to add them;

[0022] S202, according to the module connection relationship, if the output port type of module A in the connection relationship is determined, and the input port of model B at the other end is not determined, set the port to be consistent with the data type of the output port of A;

[0023] S203, according to the module connection relationship, if the output port type of module A in the connection relationship is determined, and the input port of the other end model B is also determined, if the data types are inconsistent, report a type conflict.

[0024] Furthermore, in S3, when the data types of all input ports of a module have been determined, the data types of all output ports can be determined, including the following three cases:

[0025] S301, during initialization, according to the module types in the attribute configuration of all modules, predefine some port data types, the output port type of the comparison module should be Boolean type, and the control port type of the switch module should be Boolean type;

[0026] S302, when all input port data types of a module have been determined, determine whether they meet all requirements of the module on port data types according to the module attribute configuration. If they meet, define the module output port data type according to the module input port data type and the module attribute configuration. For example, when the module is a gain module Gain, the output data type is consistent with the input port data type.

[0027] S303, when the data types of all input ports of a module have been determined, determine whether they meet all the requirements of the module for the port data type according to the module attribute configuration. If not, jump to S5 to report the model data type conflict;

[0028] S304, when the data types of all input ports of a module have been determined, and according to the module attribute configuration, the data type of the output port is a variety of situations, the data type is defined for the output port according to the data type priority. For example, when the input type of the control port of the switch selection module must be a Boolean value and the data types of the other data input ports remain consistent, the output port data type is determined as the data type of the data input port; when the data types of the other data input ports are inconsistent, the output port is defined as the data type with the highest priority according to the data type priority definition.

[0029] Furthermore, in S4, when the input and output port data types of all elements in the model are determined and no conflict is reported, the deduction result is output; when there are still undetermined port data types, return to step S2 and continue the deduction.

[0030] Furthermore, the design model adopted by S1 is generated by a graphical design interface and analyzed by a simulation solver. The graphical interface and the simulation solver agree on a common configuration file definition standard.

[0031] Beneficial effects:

[0032] The present invention provides a data type deduction method for flight control system design model simulation. The method can deduce the data types of the remaining unknown ports based on the static structure information and module configuration information of the design model of the flight control system and based on the defined port data types. In combination with the attribute requirements of the modules in the design model, a definite data type is given for all intermediate results and final output results of the design model. The method can provide feedback to the model designer on problems such as port data type conflicts, inconsistent connection data types, and ambiguous data type definitions, so as to facilitate the designers to quickly locate and iterate the design, thereby forming a design model with higher security, and providing a more reliable design model product for a series of activities such as automatic code generation for subsequent models and modularity-in-the-loop experiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments of the present invention. It is obvious that the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0034] Figure 1 A schematic flow chart of a data type deduction method for flight control system design model simulation provided by the present invention;

[0035] Figure 2 This is a schematic diagram of a design model for Embodiment 1 of the present invention;

[0036] Figure 3 Schematic diagram of the design model of the second embodiment of the present invention. DETAILED DESCRIPTION

[0037] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0038] In order to avoid the above situation, the present invention designs a pre-simulation data type deduction method, which provides a fixed data type for all ports in the design model to ensure that the design model provides stable output; at the same time, when the designer has set the data type of some ports in advance according to the requirements, or the module used has special requirements for the input and output ports, the method can detect the situation when the setting type and the deduction result conflict, and prompt the model designer to make modifications, and finally form a design model that is safer and more reliable in data type. Provide a reliable product for a series of subsequent work such as model verification and model code generation.

[0039] This method can improve the reliability and credibility of the flight control system design model and provide strong support for the design of a high-safety model of the flight control system.

[0040] The present invention provides a data type deduction method for flight control system design model simulation, comprising the following steps:

[0041] S1, parse the design model, obtain all module attribute configurations and connection relationships; define the port data type requirements for different types of modules; define the data type priority as one of the bases for data deduction.

[0042] S2, starting from the port with the determined data type, determine the data type of the associated port according to the connection relationship. When the data types of the ports at both ends of the same connection are inconsistent, report the conflict and jump to S5;

[0043] S3, for the module whose input port data types have been determined, check whether the input data port data type conflicts with the module attribute configuration according to the module attribute configuration, if there is no conflict, determine the data type of the associated output port, otherwise jump to S5;

[0044] S4, judging whether the port data types of all modules in the design model have been determined, if they have been determined, the analysis ends; otherwise, repeating steps S2 and S3 until the port data types of all modules in the design model have been determined.

[0045] S5: Terminate the simulation process, report the design model conflict problem and the port location where the conflict occurs, and the analysis ends.

[0046] Furthermore, the step S1 specifically includes:

[0047] The design model used in step S1 is generated by a graphical design interface and parsed by a simulation solution device. The graphical interface and the simulation solution device agree on a common configuration file definition standard.

[0048] Step S1 extracts all modules and their attribute configuration information as well as the connection relationship of all modules by parsing the model configuration file.

[0049] In particular, for design models with nested subsystems, all module configuration information and their connection relationships within the subsystems should also be parsed. The specific method for extracting the module configuration information and their connection relationships within all subsystems is:

[0050] 1) First, establish a subsystem hierarchical data structure: extract all subsystems in the model, organize them according to their levels, and form a tree data structure with the top-level system of the model as the root node. According to the subsystem position of each module, associate each module with a specific node of the tree data structure; use the depth-first search method to traverse the tree data structure to obtain the data flow connection relationship between subsystems;

[0051] 2) The data flow relationship within the subsystem is analyzed normally according to the common design model;

[0052] 3) Flatten the data flow relationship at the subsystem boundary: the port type of the module outside the subsystem is directly associated with the input port data type inside the subsystem through the connection relationship; the subsystem output port data type is associated with the relevant module according to the subsystem external output port connection relationship.

[0053] Furthermore, the processing in step S2 includes: starting from the port of known data type, there are the following three situations:

[0054] S201, during initialization, check whether the data types of all input modules in the design model have been defined. If there are undefined model input modules, prompt the designer to add them; check whether there are dangling and unconnected model ports. If there are, prompt the designer to add them;

[0055] S202, according to the module connection relationship, if the output port type of module A in the connection relationship is determined, and the input port of model B at the other end is not determined, set the port to be consistent with the data type of the output port of A;

[0056] S203, according to the module connection relationship, if the output port type of module A in the connection relationship is determined, and the input port of the other end model B is also determined, if the data types are inconsistent, report a type conflict;

[0057] Furthermore, in step S3, when the data types of all input ports of a module have been determined, the data types of all output ports thereof can be determined, specifically including the following three situations:

[0058] S301, during initialization, according to the module types in the attribute configuration of all modules, predefine some port data types, for example, the output port type of the comparison module should be Boolean type, the control port type of the switch module should be Boolean type, etc.;

[0059] S302, when all input port data types of a module have been determined, determine whether they meet all requirements of the module on port data types according to the module attribute configuration. If they meet, define the module output port data type according to the module input port data type and the module attribute configuration. For example, when the module is a gain module Gain, the output data type is consistent with the input port data type.

[0060] S303, when all the input port data types of a module have been determined, determine whether they meet all the requirements of the module for the port data type according to the module attribute configuration. If not, jump to S5 and report the model data type conflict. For example, the output module has been defined as double, but its input port is defined as int16 according to the connection data type deduction in step S2, and a type conflict needs to be reported;

[0061] S304, when the data types of all input ports of a module have been determined, and according to the module attribute configuration, the data type of the output port is a variety of situations, the data type is defined for the output port according to the data type priority. For example, when the input type of the control port of the switch selection module must be a Boolean value and the data types of the other data input ports remain consistent, the output port data type is determined as the data type of the data input port; when the data types of the other data input ports are inconsistent, the output port is defined as the data type with the highest priority according to the data type priority definition.

[0062] Furthermore, in step S4, when the input and output port data types of all elements in the model are determined and no conflict is reported, the deduction result is output; when there are still undetermined port data types, return to step S2 and continue the deduction.

[0063] The technical solution provided by the embodiment of the present invention provides model data type pre-checking and determination for model simulation solution in the field of flight control, supports the determination of model data type, and enhances the reliability of high-safety system design.

[0064] The following two specific embodiments are used to schematically illustrate the implementation of the data type deduction of the flight control system design model simulation provided by the present invention. The following description of the embodiments is only for providing a better understanding of the present invention by showing examples of the present invention.

[0065] Embodiment 1

[0066] Figure 2 This is a schematic diagram of the module connection relationship of an embodiment of the present invention. This embodiment describes the specific process of solving the design model according to the data type deduction scheme of the design model.

[0067] Figure 1 A flow chart of the data type deduction process of the flight control system design model simulation provided by the embodiment of the present invention, for the above Figure 2 The data type deduction process of the design model in can include the following steps:

[0068] Step 1: Extract the basic element modules and data flow connection relationships in the design model from the design model and map them to the memory; mark the number of input and output ports and special type requirements of the basic modules. For example, parse the switch module and gain module from the model, mark their port numbers and model types to identify their special attribute requirements:

[0069] Input Module:

[0070] {ID: 1;

[0071] Name: Enter 1;

[0072] Type:Inport;

[0073] Outport1: double;};

[0074] Switch module:

[0075] {ID:2

[0076] Name: switch;

[0077] Type: Switch

[0078] Inport1: Unknown;

[0079] Inport2: Unknown;

[0080] Inport3: Unknown;

[0081] Outport: Unknown;};

[0082] Gain Block:

[0083] {ID:3

[0084] Name: Gain module;

[0085] Type: Gain;

[0086] Inport: Unknown;

[0087] Outport: Unknown;};

[0088] Model connection relationships mark source and target ports, such as:

[0089] Connection 1: {src: switch.Outport, dest: output1.Inport};

[0090] Connection 2: {src: gain.Outport, dest: switch.Inport1};

[0091] Create a port data type collection to count all port data types:

[0092] {Input 1.Outport: Unknown; Input 2.Outport: Unknown;

[0093] Gain.Inport: Unknown; Gain.Outport: Unknown;

[0094] Constant.Outport:Unknown; Switch.Outport:Unknown;

[0095] Switch.Inport1:Unknown; Switch.Inport2:Unknown; Switch.Inport3:Unknown;

[0096] output.inport:Unknown;};

[0097] Step 2: During initialization, check that all input module data types in the design model have been defined, determine that the input port type has been defined based on the input module attribute configuration, and refresh the data type list:

[0098] {Input1.Outport: double; Input2.Outport: double;

[0099] Gain.Inport: Unknown; Gain.Outport: Unknown;

[0100] Constant.Outport:Unknown; Switch.Outport:Unknown;

[0101] Switch.Inport1:Unknown; Switch.Inport2:Unknown; Switch.Inport3:Unknown;

[0102] output.inport:Unknown;};

[0103] Step 3, during initialization, determine all modules and predefine some port data types according to different types. It is known that the switch module requires its input port 2, Inport2, to be a Boolean value in order to determine which output to select.

[0104] {Input1.Outport: double; Input2.Outport: double;

[0105] Gain.Inport: Unknown; Gain.Outport: Unknown;

[0106] Constant.Outport:double; Switch.Outport:Unknown;

[0107] Switch.Inport1:Unknown; Switch.Inport2:boolean; Switch.Inport3:Unknown;

[0108] output.inport:Unknown;};

[0109] Step 4: Check that the data types of all module ports have not been completely solved, and continue to deduce the data types;

[0110] Step 5, according to the module connection relationship, if the output port type of module A in the connection relationship is determined, and the input port of model B at the other end is not determined, set the port to be consistent with the data type of the output port of A; according to the connection relationship connection 1: {src: input 1.Outport, dest: gain.Inport}, it is known that the input 1.Outport data type is double, it can be determined that the gain.Inport data type is also double, and the port data type table is updated:

[0111] {Input1.Outport: double; Input2.Outport: double;

[0112] gain.Inport: double; gain.Outport: Unknown;

[0113] Constant.Outport:Unknown; Switch.Outport:Unknown;

[0114] Switch.Inport1:Unknown; Switch.Inport2:boolean; Switch.Inport3:Unknown;

[0115] output.inport:Unknown;};

[0116] Step 6: According to the module connection relationship, if the output port type of module A in the connection relationship is determined, and the input port of model B at the other end is also determined, if the data types are inconsistent, report a type conflict; in this case, it is known that the data type of input 2.Outport is double, the data type of switch.Inport2 is boolean, and the connection relationship is {src: input 2.Outport, dest: switch.Inport2}. The data types conflict, and report the conflict;

[0117] Step 7: During the data type deduction process, it was found that the data type definition of input 2 was incorrect, and there was a hidden danger to the model security. For a high-security system, the simulation solver cannot be allowed to convert data types at will. When the input port does not match, a data conflict error is reported and the deduction is terminated.

[0118] Embodiment 2

[0119] Figure 3 This is a schematic diagram of the module connection relationship of an embodiment of the present invention. This embodiment describes the specific process of solving the design model according to the data type deduction scheme of the design model.

[0120] Figure 1 A flow chart of the data type deduction process of the flight control system design model simulation provided by the embodiment of the present invention, for the above Figure 3 The sorting solution process of the design model in can include the following steps:

[0121] Step 1: Extract the basic element modules and data flow connection relationships in the design model from the design model and map them to the memory; mark the number of input and output ports and special type requirements of the basic modules. For example, parse the switch module and gain module from the model, mark their port numbers and model types to identify their special attribute requirements:

[0122] Input Module:

[0123] {ID: 1;

[0124] Name: Enter 2;

[0125] Type:Inport;

[0126] Outport1: boolean;};

[0127] Switch module:

[0128] {ID:2

[0129] Name: switch;

[0130] Type: Switch

[0131] Inport1: Unknown;

[0132] Inport2: Unknown;

[0133] Inport3: Unknown;

[0134] Outport: Unknown;};

[0135] Gain Block:

[0136] {ID:3

[0137] Name: Gain module;

[0138] Type: Gain;

[0139] Inport: Unknown;

[0140] Outport: Unknown;};

[0141] Model connection relationships mark source and target ports, such as:

[0142] Connection 1: {src: switch.Outport, dest: output1.Inport};

[0143] Connection 2: {src: gain.Outport, dest: switch.Inport1};

[0144] Create a port data type collection to count all port data types:

[0145] {Input 1.Outport: Unknown; Input 2.Outport: Unknown;

[0146] Gain.Inport: Unknown; Gain.Outport: Unknown;

[0147] Constant.Outport:Unknown; Switch.Outport:Unknown;

[0148] Switch.Inport1:Unknown; Switch.Inport2:Unknown; Switch.Inport3:Unknown;

[0149] output.inport:Unknown;};

[0150] Step 2: During initialization, check that all input module data types in the design model have been defined, determine that the input port type has been defined based on the input module attribute configuration, and refresh the data type list:

[0151] {Input1.Outport: double; Input2.Outport: boolean;

[0152] Gain.Inport: Unknown; Gain.Outport: Unknown;

[0153] Constant.Outport:Unknown; Switch.Outport:Unknown;

[0154] Switch.Inport1:Unknown; Switch.Inport2:Unknown; Switch.Inport3:Unknown;

[0155] output.inport:Unknown;};

[0156] Step 3, during initialization, determine all modules and predefine some port data types according to different types. It is known that the switch module requires its input port 2, Inport2, to be a Boolean value in order to determine which output to select.

[0157] {Input1.Outport: double; Input2.Outport: boolean;

[0158] Gain.Inport: Unknown; Gain.Outport: Unknown;

[0159] Constant.Outport:double; Switch.Outport:Unknown;

[0160] Switch.Inport1:Unknown; Switch.Inport2:boolean; Switch.Inport3:Unknown;

[0161] output.inport:Unknown;};

[0162] Step 4: Check that the data types of all module ports have not been completely solved, and continue to deduce the data types;

[0163] Step 5, according to the module connection relationship, if the output port type of module A in the connection relationship is determined, and the input port of model B at the other end is not determined, set the port to be consistent with the data type of A output port; according to the connection relationship connection 1: {src: input 1.Outport, dest: gain.Inport}, it is known that the input 1.Outport data type is double, and it can be determined that the gain.Inport data type is also double; according to the connection relationship connection 1: {src: constant.Outport, dest: switch.Inport3}, it is known that the constant.Outport data type is double, and it can be determined that the switch.Inport3 data type is also double; update the port data type table:

[0164] {Input1.Outport: double; Input2.Outport: boolean;

[0165] gain.Inport: double; gain.Outport: Unknown;

[0166] Constant.Outport:double; Switch.Outport:Unknown;

[0167] Switch.Inport1:Unknown; Switch.Inport2:boolean; Switch.Inport3:double;

[0168] output.inport:Unknown;};

[0169] Step 6: According to the module connection relationship, if the output port type of module A in the connection relationship is determined, and the input port of model B at the other end is also determined, if the data types are inconsistent, report a type conflict; in this case, it is known that the data type of input 2.Outport is boolean, the data type of switch.Inport2 is boolean, and the connection relationship is {src: input 2.Outport, dest: switch.Inport2}. The data types before and after are consistent, and the calculation continues;

[0170] Step 7, when the data types of all input ports of a module have been determined, determine whether they meet all the requirements of the module type according to the module attributes. If they meet the requirements, define the module output port data type according to the module input port and model attributes; Gain Based on the module with all known input port data types, according to its type characteristics, the output port data type should be consistent with the input, and the gain can be obtained. The Outport data type is double, and the data type of the other port of its related connection is unknown. The inference can be obtained that the switch. Inport1 data type is also double, and the refresh type statistics table can be obtained:

[0171] {Input1.Outport: double; Input2.Outport: boolean;

[0172] gain.Inport: double; gain.Outport: double;

[0173] Constant.Outport:double; Switch.Outport:Unknown;

[0174] switch.Inport1: double; switch.Inport2: boolean; switch.Inport3: double;

[0175] output.inport:Unknown;};

[0176] Step 8: The data types of all input ports of the switch module are determined. The control port data is a Boolean value that meets the requirements. The two data input port types are double, which is consistent and meets the requirements. According to the module properties, its output data type is consistent with the input data, and the switch.Outport data type is double. Then, the connection relationship {src: switch.Outport, output.Inport} is obtained, and the output 1.Inport data type is double. Refresh the port data type statistics to get

[0177] {Input1.Outport: double; Input2.Outport: boolean;

[0178] gain.Inport: double; gain.Outport: double;

[0179] Constant.Outport:double; Switch.Outport:double;

[0180] switch.Inport1: double; switch.Inport2: boolean; switch.Inport3: double;

[0181] output.inport:double;};

[0182] Step 9: When the input and output ports of all elements in the model are determined and no conflicts are reported, the data type check passes and the deduction results are output:

[0183] {Input1.Outport: double; Input2.Outport: boolean;

[0184] gain.Inport: double; gain.Outport: double;

[0185] Constant.Outport:double; Switch.Outport:double;

[0186] switch.Inport1: double; switch.Inport2: boolean; switch.Inport3: double;

[0187] Output.Inport: double;}.

[0188] The advantages and effects of the present invention are:

[0189] 1. Assist in discovering type conflicts caused by port type configuration errors or module usage errors in the design model, and enhance the confidence of the design;

[0190] 2. Improve the output certainty of the design model, provide effective detection means and simulation assistance mechanism for high-security system model design, and help the dynamic characteristics of the design model meet the requirements;

[0191] 3. It is convenient for designers to quickly locate problems, while reducing the workload of subsequent verification personnel and increasing test efficiency and accuracy;

[0192] 4. Improved the quality and reliability of flight control system design.

Claims

1. A data type deduction method for flight control system design model simulation, characterized in that: include: S1, parse the design model to obtain all module attribute configurations and connection relationships; Define port data type requirements for different types of modules; Define data type priorities as the basis for data deduction; S2, starting from the port with the determined data type, determine the data type of the associated port according to the connection relationship. When the data types of the ports at both ends of the same connection are inconsistent, report the conflict and jump to S5; S3, for the module whose input port data types have been determined, check whether the input data port data type conflicts with the module attribute configuration according to the module attribute configuration, if there is no conflict, determine the data type of the associated output port, otherwise jump to S5; S4, judging whether the port data types of all modules in the design model have been determined, and if they have been determined, the analysis ends; Otherwise, repeat steps S2 and S3 until the port data types of all modules in the design model have been determined; S5: Terminate the simulation process, report the design model conflict problem and the port location where the conflict occurs, and the analysis ends.

2. The method according to claim 1, characterized in that Step S1 specifically includes: By parsing the model configuration file, the modules and their attribute information of all hierarchical systems are extracted, and the connection relationship of all modules is extracted.

3. The method according to claim 2, characterized in that Step S1 specifically includes: Extract all subsystem modules and organize the subsystems hierarchically to form a tree data structure with the top-level system of the model as the root node; Use the depth-first search algorithm to traverse the tree data structure and obtain the module data flow connection relationship; The data flow relationship within the subsystem is analyzed normally according to the ordinary design model, and the data flow relationship at the subsystem boundary is flattened.

4. The method according to claim 3, characterized in that Step S1 specifically includes: When there are subsystems in the design model, the subsystems are flattened; the port type of the module outside the subsystem is directly associated with the input port data type inside the subsystem through a connection relationship; the output port data type of the subsystem is associated with the relevant module according to the connection relationship of the output port outside the subsystem.

5. The method according to claim 1, characterized in that The processing in S2 includes: starting from the port of known data type, there are three cases: S201, during initialization, check whether all input module data types in the design model have been defined. If there are undefined model input modules, prompt the designer to add them; S202, according to the module connection relationship, if the output port type of module A in the connection relationship is determined, and the input port of model B at the other end is not determined, set the port to be consistent with the data type of the output port of A; S203, according to the module connection relationship, if the output port type of module A in the connection relationship is determined, and the input port of the other end model B is also determined, if the data types are inconsistent, report a type conflict.

6. The method according to claim 1, characterized in that In S3, when the data types of all input ports of a module have been determined, the data types of all output ports can be determined, including the following three cases: S301, during initialization, according to the module types in the attribute configuration of all modules, predefine some port data types, the output port type of the comparison module should be Boolean type, and the control port type of the switch module should be Boolean type; S302, when all input port data types of a module have been determined, determine whether they meet all requirements of the module on port data types according to the module attribute configuration. If they meet, define the module output port data type according to the module input port data type and the module attribute configuration. For example, when the module is a gain module Gain, the output data type is consistent with the input port data type. S303, when the data types of all input ports of a module have been determined, determine whether they meet all the requirements of the module for the port data type according to the module attribute configuration. If not, jump to S5 to report the model data type conflict; S304, when the data types of all input ports of a module have been determined, and according to the module attribute configuration, the data type of the output port is a variety of situations, the data type is defined for the output port according to the data type priority. For example, when the input type of the control port of the switch selection module must be a Boolean value and the data types of the other data input ports remain consistent, the output port data type is determined as the data type of the data input port; when the data types of the other data input ports are inconsistent, the output port is defined as the data type with the highest priority according to the data type priority definition.

7. The method according to claim 1, characterized in that In S4, when the input and output port data types of all elements in the model are determined and no conflict is reported, the deduction result is output; when there are still undetermined port data types, return to step S2 and continue the deduction.

8. The method according to claim 1, characterized in that The design model used by S1 is generated by a graphical design interface and analyzed by a simulation solver. The graphical interface and the simulation solver agree on a common configuration file definition standard.

Images