Conflict feasible region reconstruction method for steel structure code

Abstract

The application relates to the technical field of computer-aided architectural design, and discloses a steel structure specification conflict feasible domain reconstruction method, which comprises the following steps: acquiring a target steel structure design object, a target design scene space and a conflict rule group, generating a rule condition coverage relation table and dividing a sub-design scene, performing variable normalization on formula type rules, constructing a feasible domain under unified variable space and common applicable conditions, and outputting a consistency constraint set or a rollback sequence; the application can reduce specification rule applicable condition mismatch and formula variable caliber mismatch, and improve the accuracy and executability of steel structure design parameter feasible domain reconstruction and automatic review results.

Description

Technical Field

[0001] This application relates to the field of computer-aided architectural design technology, specifically to a method for reconstructing feasible domains in conflict with steel structure specifications. Background Technology

[0002] Steel structure design is an important application scenario in computer-aided design and digital structural design for architectural engineering. In the design process of buildings, bridges, production facilities, and other engineering objects, engineering CAD, CAAD, BIM modeling software, steel structure design models, and automatic review systems are capable of parametric modeling and rule-based checks on aspects such as component sections, connection nodes, stress combinations, seismic design, fire protection requirements, and construction drawing verification. Existing automatic review systems for steel structure design typically convert engineering code clauses into rule records, and then handle conflicts between multiple code constraints according to rule priority, code level, local strictest values, or manually preset strategies to provide design parameter ranges for downstream parameter generation modules.

[0003] However, in the design of target steel structures such as steel beams, steel columns, steel braces, and node connections, multiple engineering codes or different clauses of the same engineering code are often not simply superimposed constraints of the same type. Different rule records may have different applicable conditions, such as different seismic resistance levels, fire resistance levels, component types, stress states, design stages, and load combinations. Different rule records may also use different formula variable definitions, for example, the variable names may be the same but the variable sources, units of measurement, section locations, stress combinations, or calculation stages may be different, or the variable names may be different but actually restrict the same engineering parameter. Existing processing methods, such as directly deleting rules according to a single priority, replacing rules according to the local strictest value, or merging rule records under different applicable conditions into the same calculation object, are prone to misjudging mutually exclusive but coexisting rules as conflicting rules, and are also prone to treating incomparable formula variables as the same variable. For example, variables with the same variable 'h', one representing the steel beam section height and the other representing the gusset plate thickness, if merged only by variable name, will lead to errors in the calculation of the width-to-thickness ratio of the steel beam.

[0004] Furthermore, in the process of parametric modeling of steel structures and automatic review of building structures, some code constraints do not only restrict a single design parameter, but also involve the coupling relationship between cross-sectional dimensions, slenderness ratio, width-to-thickness ratio, material strength, connection bearing capacity, and stability calculation parameters. If the existing system only takes the intersection of individual constraint parameters and fails to identify the reference and cross-reference relationships between constraint parameter fields and formula variable fields, it may result in an empty value space formed by multiple design parameters even when the most stringent constraints are met locally. It may also only prompt "no feasible solution" or "rule conflict" when the feasible domain is already empty, without indicating the range of upstream design variables that should be adjusted back, leading to the interruption of downstream steel structure parameter generation, scheme comparison, and construction drawing design verification processes.

[0005] Therefore, in scenarios involving computer-aided design of building engineering, engineering CAD, CAAD, and automatic review of steel structure design, existing technologies still have the following problems: When the same target steel structure design object hits multiple code rule records, the existing processing methods are unable to accurately determine the executable constraint range after the rule records work together, under different applicable conditions, different formula variable calibers, and multiple parameter coupling constraints. This can easily lead to problems such as rule deletion, formula mismatch, empty value space after the superposition of local strictest values, and lack of effective backoff basis for downstream design parameter generation. Summary of the Invention

[0006] To address the shortcomings of existing technologies, the purpose of this application is to provide a method for reconstructing the feasible domain of steel structure code conflicts. This method is used to solve the problem that existing automatic review methods for design rules are unable to accurately form the feasible domain of executable design parameters when the same target steel structure design object hits multiple code rule records during computer-aided architectural design, engineering CAD, CAAD, BIM modeling, and digital design of building structures, under the coexistence of different applicable conditions, different formula variable calibers, and multi-parameter coupling constraints.

[0007] This application generates a rule condition coverage relationship table based on the target design scenario space and applicable condition fields, divides sub-design scenarios based on the rule condition coverage relationship table, normalizes the variables of the formula-type rules in the sub-scenario rule set, and constructs a feasible domain under a unified variable space and common applicable conditions. This enables the result of code conflict handling in the parametric design of steel structures to form a consistent constraint set or a rollback sequence, thereby improving the accuracy and executability of design parameter generation, automatic code conflict review and feasible domain reconstruction in computer-aided design of building structures.

[0008] To achieve the above objectives, this application adopts the following technical solution:

[0009] Firstly, this application provides a method for reconstructing feasible domains in conflict with steel structure specifications, including:

[0010] Obtain the target steel structure design object, the target design scene space, and the conflict rule group. The conflict rule group includes multiple rule records that hit the same target steel structure design object. The rule record includes the applicable condition field, the formula variable field, the constraint parameter field, and the upstream design variable mapping field.

[0011] Based on the target design scenario space and applicable condition fields, generate a rule condition coverage relationship table;

[0012] Based on the rule condition coverage relationship table, the conflict rule group is divided into sub-design scenarios to obtain at least one sub-design scenario.

[0013] Determine the set of rules for each sub-design scenario and the common applicable conditions;

[0014] Normalize the variables of the formula-type rules in the sub-scene rule set to generate a unified variable space;

[0015] Under the conditions of a unified variable space and common applicability, the feasible domain of each sub-design scenario is constructed based on the constraint parameter field and the formula variable field;

[0016] When the feasible region is not empty, write the feasible region into the set of consistency constraints;

[0017] When the feasible domain is empty, the fallback order is generated based on the upstream design variable mapping field.

[0018] Output a set of consistency constraints or a rollback order.

[0019] Preferably, the method for generating the rule condition coverage relation table includes:

[0020] Divide the target design scenario space into at least one conditional unit;

[0021] The condition units covered by each rule record are determined based on the applicable condition fields of each rule record;

[0022] Record the same coverage relationship, containment relationship, intersection relationship and mutual exclusion relationship between the condition units covered by different rules, and generate a rule condition coverage relationship table.

[0023] Preferably, the method for obtaining the sub-scene rule set includes:

[0024] When multiple rule records cover non-intersecting condition units and their combined value equals the target design scenario space, a sub-design scenario is generated according to the boundary of the condition units.

[0025] By summarizing the rule records that cover the same sub-design scenario, we obtain the sub-scenario rule set.

[0026] Preferably, the method for determining common applicable conditions includes:

[0027] When a rule record covers one or more condition units, the range of values ​​in the applicable condition field of that rule record that intersect with the corresponding condition unit or the corresponding sub-design scenario are determined as common applicable conditions.

[0028] When at least two rule records cover the same condition unit, the applicable condition fields corresponding to the same condition unit are intersected to obtain the common applicable conditions.

[0029] Preferably, the method for generating the rule condition coverage relationship table further includes:

[0030] Convert the applicable condition fields into a condition expression tree;

[0031] Update the rule condition coverage table based on the inclusion, intersection, and mutual exclusion relationships between different condition expression trees.

[0032] Preferably, the method for normalizing variables in the formula-type rules of the sub-scene rule set includes:

[0033] Read the variable name, variable source, value unit, cross section location, force combination, calculation stage, variable physical meaning, variable category or standard parameter code from the formula variable field, and generate a variable caliber mapping table;

[0034] When two variable names in the variable caliber mapping table have the same variable source, value unit, cross-sectional location, force combination, and calculation stage, and the same standard parameter code, the two variable names are mapped to the same unified variable; when the standard parameter code is not read, two variable names with the same variable source, value unit, cross-sectional location, force combination, calculation stage, variable physical meaning, and variable category are mapped to the same unified variable, forming a unified variable space.

[0035] Preferably, the method for normalizing variables in the formulaic rules of the sub-scene rule set further includes:

[0036] When any variable name in a formulaic rule is not mapped to a unified variable, a variable scope branch corresponding to any variable name is generated in the unified variable space;

[0037] Write the formula-type rules, variable sources, value units, cross-sectional locations, force combinations, and calculation stages into the variable scope branch, and construct the feasible region based on the variable scope branch.

[0038] Preferably, the method for constructing the feasible domain of each sub-design scenario includes:

[0039] Calculate the single-parameter feasible region based on rule records where the constraint parameter field references only one formula variable field;

[0040] Rule records that reference at least two formula variable fields in their constraint parameter fields, or at least one rule record whose formula variable field references the constraint parameter field of another rule record, are grouped into a variable coupling rule group to calculate the multidimensional coupling feasible region.

[0041] The generated single-parameter feasible region and the generated multidimensional coupled feasible region are merged to obtain the feasible region. The ungenerated single-parameter feasible region or the ungenerated multidimensional coupled feasible region does not participate in the spatial domain determination of the feasible region.

[0042] The generated single-parameter feasible domain and the generated multi-dimensional coupled feasible domain are merged, including: intersecting the range of values ​​of the same unified variable, and writing the range of values ​​of different unified variables into the feasible domain of the same sub-design scenario.

[0043] Preferably, the method for calculating the multidimensional coupling feasible region includes:

[0044] A variable coupling relationship graph is generated by using the constraint parameter fields and formula variable fields in the variable coupling rule group as nodes and the reference relationships between the constraint parameter fields and formula variable fields in the rule record as edges.

[0045] Group interconnected nodes in the variable coupling graph into the same coupled variable group;

[0046] Within the set of coupled variables, the range of values ​​that simultaneously satisfy the rule records in the set of coupled variables is determined, thus obtaining the multidimensional coupled feasible region.

[0047] Preferably, the method for calculating the multidimensional coupling feasible region includes:

[0048] When at least two rule records have cross-references on at least two formula variable fields, the corresponding rule records are aggregated into a set of coupled rules;

[0049] Find the range of values ​​for the rule records in the set of coupling rules that simultaneously satisfy the condition, and obtain the multidimensional coupling feasible region.

[0050] Preferably, the method for writing the feasible domain into the consistency constraint set includes:

[0051] When the feasible region is not empty, the sub-design scenario, common applicable conditions, single-parameter feasible regions calculated and participating in the formation of the feasible region, multi-dimensional coupled feasible regions calculated and participating in the formation of the feasible region, and corresponding rule records are written into the consistency constraint set.

[0052] Preferably, the method for generating the rollback sequence includes:

[0053] When the feasible domain is empty, read the upstream design variable mapping field from the rule record that participated in forming the empty feasible domain, and generate candidate upstream design variables;

[0054] Change the value range of each candidate upstream design variable and recalculate the feasible region;

[0055] The difference between the range of values ​​of the candidate upstream design variable after the change and the range of values ​​before the change is defined as the variable change amount;

[0056] Sort the variables by the amount of change when the feasible region changes from empty to non-empty, from smallest to largest, and generate a rollback order.

[0057] Preferably, the method for generating the rollback order further includes:

[0058] Combine at least two candidate upstream design variables into candidate variable combinations;

[0059] Change the value range of the candidate upstream design variable in the candidate variable combination and recalculate the single-parameter feasible region or the multi-dimensional coupled feasible region respectively;

[0060] The candidate variable combinations that can transform the feasible region from empty to non-empty are sorted in ascending order of the number of candidate upstream design variables, and the sorting results are written into the fallback order.

[0061] Compared with the prior art, the beneficial effects achieved by this application are as follows:

[0062] First, this application obtains the target steel structure design object, the target design scene space, and the conflict rule group. It also ensures that the rule records in the conflict rule group simultaneously carry applicable condition fields, formula variable fields, constraint parameter fields, and upstream design variable mapping fields. This allows for the unified inclusion of scattered code applicable conditions, calculation formula variables, constraint parameters, and upstream design variables from the automatic review of building structure digital design and engineering CAD / CAAD design rules into a single processing object. Consequently, subsequent feasible domain reconstruction no longer relies solely on rule priority or local strictest values. Instead, it establishes a structured correspondence between code rule records and the design parameter generation process around the same target steel structure design object, reducing deviations in design parameter feasible domain judgment caused by scattered rule sources and inconsistent field semantics.

[0063] Secondly, this application generates a rule condition coverage relationship table based on the target design scenario space and applicable condition fields, and divides the sub-design scenarios based on the rule condition coverage relationship table. This enables the differentiation of the same coverage relationship, inclusion relationship, intersection relationship, and mutual exclusion relationship between multiple rule records in a computer-aided architectural design scenario. As a result, standard rule records with mutually exclusive conditions but applicable to different design scenarios will not be directly deleted as conflicting rules, and standard rule records with intersecting or inclusion conditions can be limited to the corresponding sub-design scenario for further processing. This reduces the risk of rule deletion and constraint scope misjudgment caused by mismatch of applicable conditions in the automatic review of engineering specifications.

[0064] Furthermore, this application determines the set of rules for each sub-design scenario and the common applicable conditions, and normalizes the formula-type rules in the set of rules for each sub-design scenario to generate a unified variable space. As a result, formula variables with the same variable name but different sources, units of value, cross-sectional locations, force combinations, calculation stages, physical meanings, categories, or standard parameter codes in the parametric design of steel structures will not be incorrectly merged. Formula variables with different variable names but consistent engineering meanings and variable scopes can be mapped to unified variables, thereby reducing the distortion in the construction of feasible domains caused by mismatches in formula variable scopes in computer-aided design of building structures.

[0065] Furthermore, under the unified variable space and common applicable conditions, this application constructs the feasible domain of each sub-design scenario based on the constraint parameter field and formula variable field, and calculates and merges the single-parameter feasible domain and the multi-dimensional coupled feasible domain separately. This allows the cross-sectional dimensions, slenderness ratio, width-to-thickness ratio, material strength, connection bearing capacity, and stability calculation parameters of target steel structure design objects such as steel beams, steel columns, steel supports, and node connections to be jointly constrained under common applicable conditions. Therefore, compared with the processing method of only taking the intersection of a single design parameter, this application can identify the actual executable design parameter range after the combined action of multi-parameter coupled constraints, reducing the risk that the value space is empty after the superposition of local strictest values, but the system continues to output incorrect design parameters.

[0066] Furthermore, this application writes the feasible domain into the consistency constraint set when the feasible domain is not empty, and saves the sub-design scenarios, common applicable conditions, single-parameter feasible domains, multi-dimensional coupled feasible domains, and corresponding rule records together. This enables the downstream steel structure parameter generation module to read the range of executable design parameters under the corresponding design scenario, and at the same time enables the automatic review system to trace the standard rule records corresponding to the consistency constraint set. As a result, this application can improve the consistency between the design parameter generation results and the basis for automatic standard review in the digital design of building structures, and make the feasible domain reconstruction results more suitable for continued use in engineering CAD, CAAD, and BIM parametric modeling processes.

[0067] Finally, this application generates a fallback order based on the upstream design variable mapping field when the feasible domain is empty, and sorts them according to the amount of variable change when the candidate upstream design variables make the feasible domain change from empty to non-empty. It can output adjustable upstream design variables and adjustment order when the feasible domain of design parameters cannot be formed. As a result, the computer-aided building design system no longer only outputs the results of "no feasible solution" or "rule conflict", but can provide a fallback basis for downstream steel structure parameter generation, scheme comparison and construction drawing design verification, thereby improving the continuity and executability of the automatic review of steel structure code conflicts and the reconstruction of the feasible domain of design parameters. Attached Figure Description

[0068] Figure 1 This is a schematic diagram of the implementation environment of this application;

[0069] Figure 2 A flowchart of the steel structure specification conflict feasible domain reconstruction method provided in Example 1;

[0070] Figure 3 A logical diagram for generating the rule condition coverage relationship table and dividing the sub-design scenarios;

[0071] Figure 4 A logic diagram generated for normalizing formula-type rule variables and branching variable scopes;

[0072] Figure 5 Logical graphs constructed for single-parameter feasible regions and multi-dimensional coupled feasible regions;

[0073] Figure 6 The logic diagram for the consistency constraint set and the backoff order output;

[0074] Figure 7 This is an example diagram of the overall processing in a steel beam application scenario. Detailed Implementation

[0075] The technical solution of this application will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments and specific features in the embodiments are detailed descriptions of the technical solution of this application, rather than limitations thereof.

[0076] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0077] It is understood that the terms "first" and "second" used in this application are used to distinguish similar technical objects; except where the order of processing, quantity relationship or execution order is explicitly defined in the embodiments of this application, the terms "first" and "second" do not indicate that there is an order of processing, quantity relationship or execution priority between the corresponding technical objects.

[0078] Here, "at least two" refers to two or more; when "at least two" is used to limit rule records, it means that the conflict rule group contains two or more rule records that hit the same target steel structure design object; when "at least two" is used to limit formula variable fields, it means that there are two or more formula variable fields participating in constraint calculation in the same rule record or different rule records; when "at least two" is used to limit candidate upstream design variables, it means that there are two or more candidate upstream design variables whose value range can be adjusted during the rollback sequence generation process; "each" refers to any single object in the corresponding set; when "each" is used to limit rule records, it means any single rule record in the conflict rule group; when "each" is used to limit sub-design scenarios, it means any single sub-design scenario among multiple sub-design scenarios; when "each" is used to limit unified variables, it means any single unified variable in the unified variable space; when "each" is used to limit candidate upstream design variables, it means any single candidate upstream design variable among the candidate upstream design variables.

[0079] It should be noted that engineering CAD, CAAD, BIM modeling software, steel structure design models, engineering code knowledge bases, parameter generation modules, and constraint solvers can all utilize existing data platforms or calculation tools within existing digital design systems for building engineering. The improvement in this application lies not in the method of establishing the aforementioned platforms, but in the fact that after the feasible domain reconstruction device reads the target steel structure design object, the target design scene space, and the conflict rule group, it generates a rule condition coverage relationship table based on the applicable condition field, divides sub-design scenes based on the rule condition coverage relationship table, generates a unified variable space based on the formula variable field, and constructs a feasible domain or generates a rollback sequence under common applicable conditions.

[0080] It should be noted that the standard provisions, rule records, design object data, design scenario data, and design variable data involved in this application are all data read from the engineering standard knowledge base, steel structure design model, automatic review system, parameter generation module, or authorized engineering design data; the standard provisions are used to provide the original constraint content in the engineering standard; the rule records are used to carry the applicable condition fields, formula variable fields, constraint parameter fields, and upstream design variable mapping fields converted from the standard provisions; the design object data is used to determine the object type, component attributes, and design stage of the target steel structure design object; the design scenario data is used to determine the target design scenario space; the design variable data is used to determine the range of variable values ​​participating in the feasible domain construction and rollback sequence generation; the feasible domain reconstruction device performs reading, field parsing, relation generation, variable normalization, feasible domain construction, and result output processing on the above data, and the data processing process is used for automatic review of steel structure design and generation of steel structure parameters.

[0081] See Figure 1The implementation environment includes a rule acquisition device, an engineering specification knowledge base, a steel structure design model, a feasible domain reconstruction device, and a downstream steel structure parameter generation module. The rule acquisition device is connected to the engineering specification knowledge base and is used to read multiple rule records that hit the same target steel structure design object from the knowledge base, and to summarize these rule records into a conflict rule group. The steel structure design model is connected to the feasible domain reconstruction device and is used to provide the feasible domain reconstruction device with the target steel structure design object, the target design scene space, and upstream design variables. The engineering specification knowledge base is also connected to the feasible domain reconstruction device and is used to provide the feasible domain reconstruction device with the applicable condition fields, formula variable fields, constraint parameter fields, and upstream design variable mapping fields corresponding to each rule record in the conflict rule group. The feasible domain reconstruction device is connected to the downstream steel structure parameter generation module and is used to generate a set of consistent constraints or a rollback order, and to output the set of consistent constraints or the rollback order to the downstream steel structure parameter generation module.

[0082] Optionally, the feasible domain reconstruction device can be a server, an engineering design terminal, a cloud review platform, or a local computing device; the server is used to perform conflict rule group processing and feasible domain construction in a multi-user steel structure design automatic review scenario; the engineering design terminal is used to read the steel structure design model in a single steel structure design project and generate a set of consistency constraints; the cloud review platform is used to receive target steel structure design objects and target design scene spaces uploaded by multiple steel structure design projects and return the corresponding set of consistency constraints or rollback order; the local computing device is used to perform rule condition coverage relationship table generation, sub-design scene division, variable normalization, and feasible domain construction in an offline design review scenario; the engineering specification knowledge base can store rule records corresponding to multiple engineering specifications and save applicable condition fields, formula variable fields, constraint parameter fields, and upstream design variable mapping fields for each rule record; the steel structure design model can provide target steel structure design objects, target design scene spaces, and upstream design variables; the embodiments of this application can be applied to scenarios of automatic steel structure design review, steel structure parameter generation, specification conflict handling, scheme comparison, and construction drawing design verification.

[0083] In this embodiment, the feasible domain reconstruction device acquires the target steel structure design object, the target design scene space, and the conflict rule group; reads the applicable condition field of each rule record in the conflict rule group, and generates a rule condition coverage relationship table based on the target design scene space and the applicable condition field; the feasible domain reconstruction device determines the inclusion, intersection, and mutual exclusion relationships of multiple rule records in the target design scene space based on the rule condition coverage relationship table, and divides the sub-design scenes according to the condition range covered by the rule records; determines the sub-scene rule set and common applicable conditions corresponding to each sub-design scene; the feasible domain reconstruction device reads the formula-type rules in the sub-scene rule set, and performs variable normalization based on the variable name, variable source, value unit, cross-sectional position, force combination, and calculation stage in the formula variable field to generate a unified variable space; under the unified variable space and common applicable conditions, the feasible domain is constructed based on the constraint parameter field and the formula variable field; the feasible domain reconstruction device determines whether the feasible domain is empty, and outputs a consistency constraint set when the feasible domain is not empty, and outputs a rollback order when the feasible domain is empty.

[0084] Those skilled in the art will understand that the number of engineering specification knowledge bases, the types of engineering specifications, the types of steel structure design objects, and the deployment form of computing devices can be configured according to the automatic review scenario of steel structure design; the number of engineering specification knowledge bases can be one or more; the types of engineering specifications can cover component design specifications, seismic structural specifications, fire protection design specifications, and connection design specifications; the types of steel structure design objects can include steel beams, steel columns, steel supports, steel node connections, and steel structure composite components; the deployment form of computing devices can be local deployment, server deployment, or cloud deployment; the embodiments of this application do not limit the number of engineering specification knowledge bases, the types of engineering specifications, the types of steel structure design objects, and the deployment form of computing devices.

[0085] It should be noted that the aforementioned implementation environment is merely an example. This application embodiment can also employ an implementation environment formed by merging some of the following devices: rule acquisition device, engineering specification knowledge base, steel structure design model, feasible domain reconstruction device, and downstream steel structure parameter generation module. For example, the rule acquisition device and feasible domain reconstruction device can be deployed in the same engineering design terminal, the engineering specification knowledge base and steel structure design model can be deployed on the same server, and the downstream steel structure parameter generation module can operate as a functional module within the feasible domain reconstruction device. This application embodiment does not limit the implementation environment.

[0086] Example 1:

[0087] This application embodiment is executed by a feasible domain reconfiguration device; see also Figure 2 The methods include:

[0088] Step S101: The feasible domain reconstruction device acquires the target steel structure design object, the target design scene space, and the conflict rule group.

[0089] The target steel structure design object is the steel structure component or connection part that requires multi-specification constraint treatment; the target steel structure design object can be a steel beam, steel column, steel brace, node connection, or combined component; the target design scenario space is the scenario range that the target steel structure design object needs to satisfy under the current design task; the target design scenario space is formed by one or more scenario dimensions such as seismic resistance level, fire resistance level, component category, stress state, design stage, and load combination conditions; the conflict rule group is multiple rule records that hit the same target steel structure design object; the multiple rule records come from different engineering specifications, different specification provisions, or different applicable branches of the same specification provision in the engineering specification knowledge base.

[0090] When multiple rule records correspond to the same target steel structure design object, and the constraint parameter fields of multiple rule records point to the same design parameter, or there is a reference relationship between the formula variable field and the constraint parameter field, and multiple rule records have overlapping applicable ranges in the target design scenario space, the multiple rule records are summarized into a conflict rule group.

[0091] Each rule record includes an applicable conditions field, a formula variable field, a constraint parameter field, and an upstream design variable mapping field. The applicable conditions field records the seismic grade, fire resistance grade, component type, stress state, design stage, and load combination conditions to which the rule record applies. The formula variable field records the variable name, variable source, unit of value, section location, stress combination, and calculation stage involved in the formula calculation in the rule record. The constraint parameter field records the final design parameters and their value ranges that are restricted by the rule record. The upstream design variable mapping field records the upstream design variables that can affect the value range of the constraint parameter field or the formula variable field. The rule record may also include a rule source field, a rule number field, a standard version field, and a clause location field. The rule source field records the name of the engineering standard corresponding to the rule record. The rule number field records the number of the rule record in the engineering standard knowledge base. The standard version field records the version of the engineering standard. The clause location field records the location of the standard clause corresponding to the rule record.

[0092] The upstream design variable mapping field is formed as follows: The feasible domain reconstruction device first reads the constraint parameter field and formula variable field from the rule record, and determines the design parameter corresponding to the constraint parameter field and the variable name corresponding to the formula variable field; the feasible domain reconstruction device then reads the generation relationship between the design variable and the design parameter from the steel structure design model and the parameter generation module; when a change in the value of a certain design variable will change the value range of the design parameter corresponding to the constraint parameter field, the feasible domain reconstruction device records the certain design variable as the upstream design variable corresponding to the constraint parameter field; when a change in the value of a certain design variable will change the value range of the variable name corresponding to the formula variable field, the feasible domain reconstruction device records the certain design variable as the upstream design variable corresponding to the formula variable field; the feasible domain reconstruction device writes the upstream design variable, the affected constraint parameter field or formula variable field, the value range of the upstream design variable before the change, the allowed value range of the upstream design variable, and the data source of the upstream design variable into the upstream design variable mapping field; the data source of the upstream design variable is the steel structure design model, the parameter generation module, or the engineering specification knowledge base.

[0093] When the constraint parameter field or formula variable field in the rule record cannot be read from the steel structure design model and parameter generation module, the feasible domain reconstructing device reads the corresponding specification clause location and rule source field from the engineering specification knowledge base, and determines the upstream design variable based on the reference relationship of the formula variable field in the rule record. When the formula variable field directly references the cross-sectional dimensions, material strength grade, connection type, component category, seismic grade, fire resistance grade, stress state, design stage, or load combination conditions of the target steel structure design object, the feasible domain reconstructing device writes the directly referenced design variable into the upstream design variable mapping field. When the formula variable field references intermediate parameters generated by the parameter generation module, the feasible domain reconstructing device continues to read the generation relationship corresponding to the intermediate parameter and writes the design variable that generated the intermediate parameter into the upstream design variable mapping field. When the constraint parameter field or formula variable field cannot be mapped to any design variable, the feasible domain reconstructing device records in the upstream design variable mapping field that there is no adjustable upstream design variable.

[0094] In one specific implementation, when a steel beam is used as the target steel structure design object, a rule record for the matched steel beam is retrieved from the engineering code knowledge base. The applicable conditions field of the rule record specifies the component type as steel beam, the stress state as bending, the design stage as construction drawing design stage, and the load combination condition as ultimate limit state. The formula variable field of the rule record specifies the variable names as flange width and flange thickness, the variable source as cross-sectional dimension data in the steel structure design model, the unit of measurement as millimeters, the cross-sectional location as the mid-span section of the steel beam, the stress combination as ultimate limit state combination, and the calculation stage as... During the construction drawing design phase, the constraint parameter field of the rule record records the width-to-thickness ratio as the restricted object, and the design parameter value range is no more than the width-to-thickness ratio limit under the corresponding steel strength grade in the engineering specification knowledge base; the upstream design variable mapping field of the rule record records the section type and steel strength grade, and records that the section type affects the flange width and flange thickness, and the steel strength grade affects the width-to-thickness ratio limit; the rule source field, rule number field, specification version field, and clause location field of the rule record respectively record the engineering specification name, the rule number in the engineering specification knowledge base, the engineering specification version, and the specification clause location.

[0095] In step S102, the feasible domain reconstruction device generates a rule condition coverage relationship table based on the target design scene space and applicable condition fields.

[0096] Specifically, the feasible domain reconstruction device reads the seismic resistance level, fire resistance level, component type, stress state, design stage, and load combination conditions from the target design scenario space, and uses the read scenario dimensions as the condition dimensions of the rule condition coverage relationship table; the feasible domain reconstruction device reads the applicable condition field of each rule record and compares the scenario dimension values ​​recorded in the applicable condition field with the target design scenario space; when the value range limited by the applicable condition field of the rule record intersects with the target design scenario space, the feasible domain reconstruction device marks the rule record as covering the corresponding range in the target design scenario space; when the ranges covered by different rule records are completely consistent, the feasible domain reconstruction device records the same coverage relationship in the rule condition coverage relationship table; when the range covered by the first rule record is... When the scope of the first rule record includes the area covered by the second rule record, and the scope covered by the first rule record contains areas not covered by the second rule record, the feasible domain reconstruction device records the inclusion relationship in the rule condition coverage relationship table, and records the rule record identifier of the first rule record as the including rule record identifier, and records the rule record identifier of the second rule record as the included rule record identifier; when the scope covered by the first rule record and the scope covered by the second rule record have a common part, and the first rule record and the second rule record each have a range not covered by the other rule record, the feasible domain reconstruction device records the intersection relationship in the rule condition coverage relationship table; when the scopes covered by different rule records do not have a common part, the feasible domain reconstruction device records the mutual exclusion relationship in the rule condition coverage relationship table.

[0097] In step S103, the feasible domain reconstruction device divides the conflict rule group into sub-design scenarios based on the rule condition coverage relationship table to obtain at least one sub-design scenario.

[0098] Sub-design scenarios are used to represent scene segments in the target design scenario space that can be jointly applied by a set of rule records. When multiple rule records are mutually exclusive in the rule condition coverage relationship table, and the combined coverage of the multiple rule records equals the target design scenario space, the feasible domain reconstruction device generates multiple sub-design scenarios according to the boundaries of the applicable condition fields of the multiple rule records. When multiple rule records are intersecting in the rule condition coverage relationship table, the intersecting range is retained as a separate sub-design scenario, and the non-intersecting range is generated as a sub-design scenario according to the boundaries of the applicable condition fields of the corresponding rule records. When the coverage of one rule record includes the coverage of another rule record, the included range is generated as a separate sub-design scenario, and the part of the included range not covered by the included range is generated as another sub-design scenario.

[0099] In step S104, the feasible domain reconstruction device determines the set of sub-scenario rules and common applicable conditions corresponding to each sub-design scenario.

[0100] The sub-scene rule set is a set of rule records covering the same sub-design scene. The feasible domain reconstruction device reads each sub-design scene one by one and reads all the condition units corresponding to the sub-design scene. The feasible domain reconstruction device then reads the condition units covered by each rule record from the rule condition coverage relationship table. When the condition units covered by a rule record contain all the condition units corresponding to the sub-design scene, the feasible domain reconstruction device writes a rule record into the sub-scene rule set corresponding to the sub-design scene. When a rule record only covers some of the condition units in the sub-design scene, the feasible domain reconstruction device does not directly write a rule record into the sub-scene rule set corresponding to the sub-design scene, but re-divides the sub-design scene according to the boundary of the condition units covered by a rule record, and then redetermines the sub-scene rule set for the re-divided sub-design scene.

[0101] In one alternative implementation, the feasible domain reconstruction device can determine whether a rule record should be written into the sub-scene rule set according to the following formula:

[0102] ;

[0103] in, This represents the i-th rule record; This represents the set of sub-scene rules corresponding to the s-th sub-design scene; This represents the set of conditional units corresponding to the s-th sub-design scenario; This represents the set of condition units covered by the i-th rule record; This indicates that the i-th rule record covers all condition units in the s-th sub-design scenario; Read from the rule condition coverage table; The results are determined by the sub-design scenario division.

[0104] The common applicable condition is the range of conditions that can be met by all rule records within the same sub-design scenario. When there is only one rule record in the sub-scenario rule set, the feasible domain reconstruction device determines the range of values ​​in the applicable condition field of the rule record that fall within the sub-design scenario as the common applicable condition. When there are at least two rule records in the sub-scenario rule set, the feasible domain reconstruction device performs intersection processing on the applicable condition fields of the at least two rule records and determines the intersection processing result as the common applicable condition. When the intersection processing result is empty, the feasible domain reconstruction device does not write the corresponding sub-design scenario into the feasible domain construction object and generates a common applicable condition empty prompt. The common applicable condition empty prompt includes the sub-design scenario, the corresponding sub-scenario rule set, and the applicable condition field that caused the intersection processing result to be empty.

[0105] In step S105, the feasible domain reconstruction device normalizes the variables of the formula-type rules in the sub-scene rule set to generate a unified variable space.

[0106] Specifically, the feasible domain reconstruction device reads the rule records in the sub-scene rule set one by one, and reads the formula variable field and constraint parameter field in each rule record. When there is at least one variable name in the formula variable field and there is a reference relationship between the constraint parameter field and the variable name in the formula variable field, the feasible domain reconstruction device determines the corresponding rule record as a formula-type rule. When the formula variable field is empty, the formula variable field only records fixed boundary values, or the constraint parameter field does not reference the variable name in the formula variable field, the feasible domain reconstruction device does not determine the corresponding rule record as a formula-type rule, and retains the corresponding rule record as a rule record in which only the constraint parameter field participates in the construction of the feasible domain.

[0107] The feasible domain reconstruction device reads variable name, variable source, unit of value, cross-sectional location, force combination, calculation stage, physical meaning of variable, variable category, and standard parameter code from the formula variable field of the formula-type rules, and generates a variable caliber mapping table based on the reading results. When the formula variable field does not record the physical meaning of variable, variable category, or standard parameter code, the feasible domain reconstruction device reads the physical meaning of variable, variable category, or standard parameter code corresponding to the variable name from the engineering specification knowledge base, steel structure design model, or parameter generation module. The variable caliber mapping table is used to record the correspondence between variable name and variable source, unit of value, cross-sectional location, force combination, calculation stage, physical meaning of variable, variable category, and standard parameter code.

[0108] The feasible domain reconstruction device determines whether variable names are mapped to a unified variable based on the variable caliber mapping table. The device first checks whether the variable source, unit of measurement, cross-sectional location, force combination, and calculation stage corresponding to two variable names are consistent. If there are inconsistencies in these aspects, the device will not map the two variable names to the same unified variable. If all aspects are consistent, and the standard parameter codes for both variable names have been read, the device will map them to the same unified variable only if the standard parameter codes are consistent. If not all standard parameter codes for two variable names have been read, the device will map them to the same unified variable only if their physical meanings and categories are consistent. If the standard parameter codes are inconsistent, or if not all standard parameter codes for two variable names have been read and there are inconsistencies in their physical meanings or categories, the device will not map them to the same unified variable.

[0109] When any variable name cannot be mapped to an existing unified variable, the feasible domain reconstruction device generates a corresponding variable caliber branch in the unified variable space. The feasible domain reconstruction device writes the formula rule, variable source, value unit, cross-sectional location, force combination, calculation stage, variable physical meaning, variable category, and standard parameter code of any variable name into the variable caliber branch. The variable caliber branch is used to separately save formula rules that cannot be processed with the same variable caliber as existing unified variables during the subsequent feasible domain construction process.

[0110] In step S106, the feasible domain reconstruction device constructs the feasible domain of each sub-design scenario based on the constraint parameter field and formula variable field under the unified variable space and common applicable conditions.

[0111] A single-parameter feasible domain corresponds to a rule record where the constraint parameter field references only one formula variable field; the feasible domain reconstruction device reads the design parameter value range recorded in the constraint parameter field and converts the design parameter value range into a value range under a unified variable space; a multi-dimensional coupled feasible domain corresponds to a rule record where the constraint parameter field references at least two formula variable fields, or a rule record where there is a cross-reference between formula variable fields and constraint parameter fields among the corresponding rule records; the feasible domain reconstruction device categorizes rule records with multiple variable references or cross-references into a variable coupling rule group, and calculates the value range that simultaneously satisfies each rule record within the variable coupling rule group; the feasible domain reconstruction device merges the single-parameter feasible domain and the multi-dimensional coupled feasible domain, and uses the merged result as the feasible domain of the sub-design scenario; when the sub-design scenario has variable caliber branches, the feasible domain reconstruction device constructs feasible domains within each variable caliber branch and retains the correspondence between each variable caliber branch and the feasible domain.

[0112] Step S107: When the feasible region is not empty, the feasible region reconstruction device writes the feasible region into the consistency constraint set.

[0113] Specifically, the feasible region reconstruction device performs a non-empty judgment on the feasible region obtained in step S106; when only a single-parameter feasible region is generated within the same sub-design scenario, the feasible region reconstruction device uses the existence of a value range that satisfies the common applicable conditions within the single-parameter feasible region as the basis for determining whether the feasible region is non-empty, and the ungenerated multi-dimensional coupled feasible region does not participate in the non-empty judgment; when only a multi-dimensional coupled feasible region is generated within the same sub-design scenario, the feasible region reconstruction device uses the existence of a value range that satisfies the common applicable conditions within the multi-dimensional coupled feasible region as the basis for determining whether the feasible region is non-empty, and the ungenerated single-parameter feasible region does not participate in the non-empty judgment; when both single-parameter feasible regions and multi-dimensional coupled feasible regions are generated within the same sub-design scenario, the feasible region reconstruction device performs a non-empty judgment on the existence of a value range that satisfies the common applicable conditions within the multi-dimensional coupled feasible region ... The feasible domain reconstruction device uses the existence of a range of values ​​that satisfy common applicable conditions after merging the single-parameter feasible domain and the multi-dimensional coupled feasible domain as the criterion for determining whether the feasible domain is non-empty. When the feasible domain is non-empty, the feasible domain reconstruction device writes the sub-design scenario, common applicable conditions, the calculated single-parameter feasible domain and the calculated multi-dimensional coupled feasible domain that participate in forming the feasible domain, and the corresponding rule records into the consistency constraint set. The consistency constraint set is used for the downstream steel structure parameter generation module to read. The downstream steel structure parameter generation module calls the consistency constraint set under the corresponding sub-design scenario and common applicable conditions, and generates the range of design parameter values ​​for the target steel structure design object based on the consistency constraint set.

[0114] Step S108: When the feasible domain is empty, the feasible domain reconfiguration device generates a rollback sequence based on the upstream design variable mapping field.

[0115] Specifically, the feasible domain reconstruction device performs spatial domain judgment on the feasible domain obtained in step S106. When only a single-parameter feasible domain is generated within the same sub-design scenario, the feasible domain reconstruction device uses the existence of a value range that satisfies the common applicable conditions within the single-parameter feasible domain as the basis for spatial domain judgment. Ungenerated multi-dimensional coupled feasible domains do not participate in the spatial domain judgment. When only a multi-dimensional coupled feasible domain is generated within the same sub-design scenario, the feasible domain reconstruction device uses the existence of a value range that satisfies the common applicable conditions within the multi-dimensional coupled feasible domain as the basis for spatial domain judgment. Ungenerated single-parameter feasible domains do not participate in the spatial domain judgment. When both single-parameter feasible domains and multi-dimensional coupled feasible domains are generated simultaneously within the same sub-design scenario, the feasible domain reconstruction device uses the existence of a value range that satisfies the common applicable conditions within the multi-dimensional coupled feasible domain as the basis for spatial domain judgment. The range of values ​​that meet the common applicable conditions is used as the basis for determining the feasible domain's empty domain. When the feasible domain is empty, the upstream design variable mapping field in the rule record that participated in forming the empty feasible domain is read, and candidate upstream design variables are generated based on the upstream design variable mapping field. The range of values ​​corresponding to each candidate upstream design variable is changed, and the feasible domain is recalculated after changing the range of values ​​corresponding to each candidate upstream design variable. When the changed range of values ​​of the candidate upstream design variable can make the feasible domain change from empty to non-empty, the difference between the changed range of values ​​of the candidate upstream design variable and the changed range of values ​​of the candidate upstream design variable is determined as the variable change amount. The feasible domain reconfiguration device arranges the candidate upstream design variables in ascending order of variable change amount, and the arrangement result is determined as the rollback order.

[0116] Step S109: The feasible domain reconstruction device outputs a set of consistency constraints or a rollback sequence.

[0117] Specifically, when step S107 generates a set of consistency constraints, the feasible domain reconfiguration device outputs the set of consistency constraints to the downstream steel structure parameter generation module; when step S108 generates a rollback sequence, the feasible domain reconfiguration device outputs the rollback sequence to the downstream steel structure parameter generation module; after receiving the set of consistency constraints, the downstream steel structure parameter generation module performs parameter generation of the target steel structure design object according to the set of consistency constraints; after receiving the rollback sequence, the downstream steel structure parameter generation module prompts the upstream design variables that need to be adjusted according to the rollback sequence.

[0118] Through the above steps, this embodiment does not directly resolve conflicting rule groups using a single rule priority or local strictest value. This embodiment first generates a rule condition coverage relationship table based on the target design scenario space and applicable condition fields, and then divides sub-design scenarios based on the rule condition coverage relationship table. Next, this embodiment normalizes the variables of formulaic rules in the sub-scenario rule set to generate a unified variable space. Subsequently, this embodiment constructs a feasible region under the unified variable space and common applicable conditions. Thus, when the feasible region is not empty, it can form a set of consistent constraints for execution by the downstream steel structure parameter generation module; when the feasible region is empty, it can output a fallback order based on the upstream design variable mapping field.

[0119] Example 2:

[0120] Figure 3 This is a logic diagram of generating a rule condition coverage relationship table and dividing sub-design scenarios provided in an embodiment of this application; based on embodiment 1, this embodiment further provides an implementation method for generating a rule condition coverage relationship table.

[0121] Specifically, the feasible domain reconfiguration device divides the target design scenario space into multiple condition units. The feasible domain reconfiguration device first reads the seismic resistance level, fire resistance level, component type, stress state, design stage, and load combination conditions contained in the target design scenario space. Then, it determines the value range of each scenario dimension in the target design scenario space. Subsequently, it combines the value ranges of different scenario dimensions and determines each combination result that corresponds to the current design task of the target steel structure design object as a condition unit. When the target design scenario space does not contain a certain scenario dimension, the feasible domain reconfiguration device does not use the missing scenario dimension as the basis for dividing the condition unit.

[0122] Among them, the condition unit is a computable scene range in the target design scene space; the condition unit is formed by one or more scene dimensions from the following: seismic resistance level, fire resistance level, component type, stress state, design stage, and load combination conditions; one condition unit corresponds to a set of scene dimension values; for example, one condition unit can correspond to a target steel structure design object under the same seismic resistance level, same fire resistance level, same component type, same stress state, same design stage, and same load combination conditions; the condition unit is used as the minimum processing object for determining whether the rule record covers the target design scene space.

[0123] Subsequently, the feasible domain reconstruction device determines the condition units covered by each rule record based on the applicable condition field of each rule record. The feasible domain reconstruction device reads the applicable condition field of the rule record and compares the seismic resistance level, fire protection level, component type, stress state, design stage, and load combination conditions recorded in the applicable condition field with the scene dimension values ​​corresponding to each condition unit. When all scene dimension values ​​corresponding to the condition unit meet the applicable condition field of the rule record, the feasible domain reconstruction device marks the rule record as covering the condition unit. When the applicable condition field of the rule record does not limit a certain scene dimension, the feasible domain reconstruction device processes the unlimited scene dimension according to the full value range of the corresponding scene dimension in the target design scene space. When any scene dimension value corresponding to the condition unit does not meet the applicable condition field of the rule record, the feasible domain reconstruction device marks the rule record as not covering the condition unit.

[0124] Furthermore, the feasible domain reconstruction device records the same coverage relationship, inclusion relationship, intersection relationship, and mutual exclusion relationship between the condition units covered by different rule records; when the condition units covered by the first rule record are completely identical to the condition units covered by the second rule record, the feasible domain reconstruction device records that there is an same coverage relationship between the first rule record and the second rule record; when all the condition units covered by the first rule record belong to the condition units covered by the second rule record, and there are condition units covered by the second rule record that are not covered by the first rule record, the feasible domain reconstruction device records that there is an inclusion relationship between the first rule record and the second rule record, and records the rule record identifier of the second rule record as the including rule record identifier, and records the rule record identifier of the first rule record as the included one. The feasible domain reconstruction device records an intersection relationship between the first rule record and the second rule record when the condition units covered by the first rule record and the condition units covered by the second rule record share a common condition unit, and both the first and second rule records have condition units that are not covered by the other rule record. When the condition units covered by the first rule record and the condition units covered by the second rule record do not share a common condition unit, the feasible domain reconstruction device records a mutual exclusion relationship between the first and second rule records. The feasible domain reconstruction device writes the rule record identifier, condition unit identifier, coverage result, same coverage relationship, inclusion relationship, including rule record identifier, included rule record identifier, intersection relationship, and mutual exclusion relationship into the rule condition coverage relationship table.

[0125] Simultaneously, the feasible domain reconstruction device performs a coverage integrity check on all condition units in the target design scene space; it reads each condition unit in the target design scene space one by one and queries the rule condition coverage relationship table to see if there is a rule record covering the corresponding condition unit; when a condition unit is not covered by any rule record in the conflict rule group, the condition unit is recorded as a condition unit in the target design scene space that is not covered by any rule record; the seismic grade, fire resistance grade, component category, stress state, design stage, and load combination conditions corresponding to the condition unit in the target design scene space that is not covered by any rule record are written into the rule condition coverage relationship table, and the corresponding condition unit is marked in the rule condition coverage relationship table as not having a rule record that can participate in the feasible domain construction; when there is a condition unit in the target design scene space that is not covered by any rule record, a missing rule prompt is generated. The missing rule prompt includes the condition unit that is not covered by any rule record, the target steel structure design object, and the corresponding scene dimension value, which is used to indicate that there is a lack of rule record covering the corresponding condition unit in the engineering specification knowledge base.

[0126] Through this embodiment, the feasible domain reconstruction device can convert the applicable condition relationship between rule records into a rule condition coverage relationship table supported by condition units. The rule condition coverage relationship table can record the coverage range of each rule record in the target design scene space, and can record the inclusion relationship, intersection relationship and mutual exclusion relationship between different rule records. As a result, the subsequent sub-design scene division can directly read the rule condition coverage relationship table and determine the sub-design scene according to the boundary of the condition unit.

[0127] Example 3:

[0128] In Example 2 and Figure 3 Based on the processing logic shown, this embodiment further provides an implementation method for obtaining sub-design scenarios and sub-scenario rule sets based on condition units.

[0129] Specifically, the feasible domain reconstruction device generates sub-design scenarios based on the rule condition coverage relationship table. When the condition units covered by multiple rule records are non-intersecting, and the merged condition units of multiple rule records equal all condition units in the target design scenario space, a sub-design scenario is generated according to the boundary of the condition units. First, the condition units corresponding to each rule record in the rule condition coverage relationship table are read. Then, it is determined whether there are common condition units between the condition units corresponding to different rule records. When there are no common condition units between the condition units corresponding to different rule records, the condition units corresponding to different rule records are determined to be non-intersecting. The feasible domain reconstruction device then merges the condition units corresponding to multiple rule records and compares the merged condition units with all condition units in the target design scenario space. When the merged condition units are consistent with all condition units in the target design scenario space, the feasible domain reconstruction device uses each set of non-intersecting condition units as the basis for generating a sub-design scenario, and generates the corresponding sub-design scenario according to the seismic resistance level, fire resistance level, component category, stress state, design stage, and load combination conditions corresponding to the condition units.

[0130] When the merged conditional units do not cover all conditional units in the target design scenario space, the feasible domain reconstruction device does not incorporate conditional units in the target design scenario space that are not covered by any rule records into the feasible domain construction object; the feasible domain reconstruction device uses conditional units that have been covered by at least one rule record as the basis for generating sub-design scenarios, and writes conditional units in the target design scenario space that are not covered by any rule records into the missing rule prompt; the missing rule prompt is output together with the sub-design scenario division result; the missing rule prompt is used to prompt the downstream steel structure parameter generation module not to execute steel structure design parameter generation under the corresponding conditional unit until the engineering specification knowledge base is filled with rule records that cover the corresponding conditional unit.

[0131] Subsequently, the feasible domain reconstruction device summarizes the rule records covering the same sub-design scenario to obtain a sub-scenario rule set. The feasible domain reconstruction device reads the condition units corresponding to the sub-design scenario one by one and queries the rule record covering the corresponding condition unit in the rule condition coverage relationship table. When a rule record covers all condition units in the sub-design scenario, the feasible domain reconstruction device writes the rule record into the sub-scenario rule set corresponding to the sub-design scenario. When at least two rule records cover different condition units in the same sub-design scenario, and the condition units corresponding to at least two rule records together constitute the sub-design scenario, the feasible domain reconstruction device writes at least two rule records together into the sub-scenario rule set corresponding to the sub-design scenario. The feasible domain reconstruction device retains the applicable condition field, formula variable field, constraint parameter field, and upstream design variable mapping field of the rule record in the sub-scenario rule set, and retains the correspondence between the sub-design scenario and the sub-scenario rule set.

[0132] In this embodiment, the feasible domain reconstruction device can identify mutually exclusive rule records that jointly cover the target design scenario space as coexisting relationships. Instead of deleting mutually exclusive rule records according to a single rule priority, the device generates sub-design scenarios according to the boundaries of the condition units and retains the corresponding rule records in different sub-design scenarios. When there are condition units in the target design scenario space that are not covered by any rule records, the device writes the condition units not covered by any rule records into a missing rule prompt and uses the condition units covered by rule records for sub-design scenario division. As a result, subsequent feasible domain construction is only performed on sub-design scenarios supported by rule records, avoiding the misinterpretation of rule blank areas as sub-design scenarios with feasible domain calculation basis.

[0133] Example 4:

[0134] In Example 2 and Figure 3 Based on the processing logic shown, this embodiment further provides an implementation method for determining common applicable conditions.

[0135] Specifically, when a rule record covers one or more condition units, the feasible domain reconstruction device determines the range of values ​​in the applicable condition field of a rule record that corresponds to the condition unit as the common applicable condition. The feasible domain reconstruction device first reads the seismic resistance level, fire resistance level, component category, stress state, design stage, and load combination conditions corresponding to the condition unit. The feasible domain reconstruction device then reads the applicable condition field of a rule record. When the values ​​of each scenario dimension corresponding to the condition unit all satisfy the applicable condition field of a rule record, the feasible domain reconstruction device extracts the part of the applicable condition field of a rule record that intersects with the condition unit and uses the extraction result as the common applicable condition. A correspondence is established between the common applicable condition and the condition unit. The common applicable condition is used to limit the scenario range of subsequent formula-type rule comparison, variable normalization, and feasible domain calculation.

[0136] When at least two rule records cover the same condition unit, the feasible domain reconstruction device performs intersection processing on the applicable condition fields corresponding to the same condition unit to obtain common applicable conditions. The feasible domain reconstruction device first reads the values ​​of each scenario dimension corresponding to the same condition unit. Then, it reads the applicable condition fields of at least two rule records respectively. The feasible domain reconstruction device compares the values ​​according to seismic resistance level, fire resistance level, component type, stress state, design stage, and load combination conditions, and retains the value range that is satisfied by at least two rule records. When a certain scenario dimension falls within the applicable conditions of at least two rule records... When all fields in the condition have limitations, the feasible domain reconstruction device takes the common value range of at least two rule records in the corresponding scene dimension; when a scene dimension has limitations only in the applicable condition fields of some rule records, the feasible domain reconstruction device takes the applicable condition fields with limitations as the common value range of the corresponding scene dimension; when a scene dimension has no limitations in the applicable condition fields of at least two rule records, the feasible domain reconstruction device takes the value of the corresponding scene dimension in the condition unit as the common value range; the feasible domain reconstruction device combines the common value ranges of each scene dimension to obtain the common applicable conditions.

[0137] Through this embodiment, the feasible domain reconstruction device can determine the common conditions under which rule records are valid within a sub-design scenario; the common applicable conditions can serve as unified input conditions for subsequent formula-based rule comparison, variable normalization, and feasible domain calculation; thus, when performing formula-based rule comparison, variable normalization, and feasible domain calculation, the feasible domain reconstruction device can first limit the applicable prerequisites of the rule records, and then process the formula variable fields and constraint parameter fields, avoiding treating rule records under different applicable conditions as the same calculation object.

[0138] Example 5:

[0139] Based on Example 2, this example further provides an implementation method for updating the rule condition coverage relationship table based on the condition expression tree.

[0140] Specifically, the feasible domain reconstruction device converts the applicable condition fields into a condition expression tree; the feasible domain reconstruction device first reads the applicable condition fields of the rule record, and then splits the applicable condition fields according to seismic resistance level, fire protection level, component category, stress state, design stage, and load combination conditions; the feasible domain reconstruction device generates condition nodes for each scenario dimension and its corresponding value range obtained from the splitting; when there are multiple scenario dimensions in the applicable condition fields that need to be satisfied simultaneously, the feasible domain reconstruction device establishes a simultaneous satisfaction relationship between the corresponding condition nodes; when there are multiple scenario dimension values ​​in the applicable condition fields that are applicable if any one of them is satisfied, the feasible domain reconstruction device establishes an arbitrary satisfaction relationship between the corresponding condition nodes; when there are exclusionary or inapplicable contents in the applicable condition fields, the feasible domain reconstruction device writes the corresponding contents into exclusion conditions and attaches the exclusion conditions to the condition nodes of the corresponding scenario dimensions.

[0141] The condition expression tree includes condition nodes, value boundaries, logical connections, exclusion conditions, and applicable scope conditions. Condition nodes record the scene dimensions appearing in the applicable condition fields. Value boundaries record the range of values ​​allowed for the corresponding scene dimension to enter the rule record coverage. Logical connections record the simultaneous satisfaction relationship and any satisfaction relationship between multiple condition nodes. Exclusion conditions record the scene dimension values ​​that need to be removed from the rule record coverage. Applicable scope conditions record the range of condition units that the rule record can cover within the target design scene space. The feasible domain reconfiguration device determines the condition units covered by the rule record in the target design scene space based on the condition nodes, value boundaries, logical connections, and exclusion conditions, and writes the covered condition units into the applicable scope conditions.

[0142] Subsequently, the feasible domain reconstruction device updates the rule condition coverage table based on the same coverage, containment, intersection, and mutual exclusion relationships between different condition expression trees. The feasible domain reconstruction device first reads the condition expression tree corresponding to each rule record and determines the condition units covered by the rule record based on the applicable scope conditions in the condition expression tree. When the condition units covered by the first condition expression tree are completely identical to those covered by the second condition expression tree, the feasible domain reconstruction device records in the rule condition coverage table that there is a same coverage relationship between the rule record corresponding to the first condition expression tree and the rule record corresponding to the second condition expression tree. When all condition units covered by the first condition expression tree belong to the condition units covered by the second condition expression tree, and there are condition units covered by the second condition expression tree that are not covered by the first condition expression tree, the feasible domain reconstruction device updates the rule condition coverage table. The relationship table records that there is an inclusion relationship between the rule record corresponding to the first conditional expression tree and the rule record corresponding to the second conditional expression tree. The rule record identifier corresponding to the second conditional expression tree is recorded as the including rule record identifier, and the rule record identifier corresponding to the first conditional expression tree is recorded as the included rule record identifier. When the conditional units covered by the first conditional expression tree and the conditional units covered by the second conditional expression tree have common conditional units, and both the first and second conditional expression trees have conditional units that are not covered by the other conditional expression tree, the feasible domain reconstruction device records that there is an intersection relationship between the corresponding rule records in the rule condition coverage relationship table. When the conditional units covered by the first conditional expression tree and the conditional units covered by the second conditional expression tree do not have common conditional units, the feasible domain reconstruction device records that there is a mutual exclusion relationship between the corresponding rule records in the rule condition coverage relationship table.

[0143] Through this embodiment, the feasible domain reconstruction device can convert applicable condition fields with conditional constraints, exclusion constraints, and applicable scope constraints into conditional expression trees; the conditional expression trees can convert the scene dimensions, value boundaries, logical connection relationships, and exclusion conditions in the applicable condition fields into conditional units covered by rule records; thus, the feasible domain reconstruction device can update the rule condition coverage relationship table based on the conditional expression tree, so that the inclusion, intersection, and mutual exclusion relationships recorded in the rule condition coverage relationship table can correspond to the actual coverage of the rule records in the target design scene space.

[0144] Example 6:

[0145] Figure 4 This application provides a logic diagram for formula-type rule variable normalization and variable scope branch generation. Based on embodiment 1, this embodiment further provides an implementation method for variable normalization of formula-type rules in a sub-scene rule set.

[0146] Specifically, the feasible domain reconstruction device reads the variable name, variable source, unit of value, cross-sectional location, force combination, and calculation stage from the formula variable field to generate a variable scope mapping table. The feasible domain reconstruction device first reads each rule record in the sub-scene rule set and determines whether each rule record contains a formula variable field. When a rule record contains a formula variable field, the feasible domain reconstruction device identifies the rule record as a formula-type rule. The feasible domain reconstruction device then extracts the variable name from the formula variable field of the formula-type rule and reads the variable source, unit of value, cross-sectional location, force combination, and calculation stage corresponding to the variable name. The variable source is used to record the variable name. The corresponding data comes from the geometric data, material data, internal force data, connection data, or data given in the specifications of the target steel structure design object; the unit of measurement is used to record the unit of measurement of the value corresponding to the variable name; the section position is used to record the position of the value corresponding to the variable name in the target steel structure design object; the force combination is used to record the load combination conditions used for the value corresponding to the variable name; the calculation stage is used to record whether the value corresponding to the variable name is in the scheme design stage, preliminary design stage, or construction drawing design stage; the feasible domain reconfiguration device writes the variable name, variable source, unit of measurement, section position, force combination, and calculation stage into the variable caliber mapping table as a single record.

[0147] Subsequently, the feasible domain reconstruction device determines whether a variable name is mapped to a unified variable based on the variable source, unit of value, cross-sectional location, force combination, calculation stage, physical meaning of the variable, variable category, and standard parameter code in the variable caliber mapping table, thus forming a unified variable space. The physical meaning of the variable is used to record the engineering meaning corresponding to the variable name. The physical meaning of the variable is read from the variable explanation corresponding to the formula variable field, the standard clause location corresponding to the rule record, or the variable description in the engineering standard knowledge base. The variable category is used to record the parameter type to which the variable name belongs. The variable category includes geometric dimension parameters, cross-sectional characteristic parameters, material performance parameters, internal force parameters, stability calculation parameters, and connection bearing parameters. The variable category is read from the variable classification record in the engineering standard knowledge base or parameter generation module. The standard parameter code is used to record the unique parameter code of the variable name in the engineering standard knowledge base, steel structure design model, or parameter generation module. The standard parameter code is read from the engineering standard knowledge base, steel structure design model, or parameter generation module.

[0148] The feasible region reconstruction device first determines whether the variable source, unit of value, cross-sectional location, force combination, and calculation stage corresponding to two variable names are consistent. If there are inconsistencies in these aspects, the device will not map the two variable names to the same unified variable. If all aspects are consistent, and the standard parameter codes corresponding to both variable names have been read, the device will only map the two variable names to the same unified variable if the standard parameter codes are consistent. If not all codes are read, the feasible domain reconstruction device will map two variable names to the same unified variable only if the physical meanings and categories of the variables corresponding to the two variable names are consistent. If the codes of the two standard parameters are inconsistent, or if not all standard parameter codes corresponding to the two variable names are read and there are inconsistencies in the physical meanings or categories of the variables, the feasible domain reconstruction device will not map the two variable names to the same unified variable. The feasible domain reconstruction device will write the mapped unified variable, the variable name corresponding to the unified variable, the variable source, the unit of value, the cross-sectional location, the force combination, the calculation stage, the physical meaning of the variable, the variable category, and the standard parameter code into the unified variable space.

[0149] Through this embodiment, the feasible domain reconstruction device can normalize the formula-type rules in the sub-scene rule set based on the variable source, value unit, cross-sectional location, force combination, calculation stage, variable physical meaning, variable category, and standard parameter code. When the variable names are different in different engineering specifications, but the variable source, value unit, cross-sectional location, force combination, and calculation stage are consistent, and the standard parameter code is consistent, the feasible domain reconstruction device maps the variable names to the same unified variable. When not all standard parameter codes are read, the feasible domain reconstruction device maps the variable names to the same unified variable only when the variable physical meaning and variable category are consistent. Thus, cross-sectional height, flange width, web thickness, slenderness ratio, and width-to-thickness ratio can be processed according to different variable physical meanings or different variable categories. The subsequent feasible domain construction can read formula variable fields and constraint parameter fields with clear engineering meanings within the unified variable space.

[0150] Example 7:

[0151] In Example 6 and Figure 4 Based on the processing logic shown, this embodiment further provides an implementation method for generating variable caliber branches.

[0152] Specifically, when any variable name in a formulaic rule is not mapped to a unified variable, the feasible domain reconstruction device generates a variable scope branch corresponding to any variable name within the unified variable space. The feasible domain reconstruction device first reads the variable scope mapping table and determines whether the variable source, value unit, cross-sectional location, force combination, and calculation stage corresponding to any variable name are consistent with the variable source, value unit, cross-sectional location, force combination, and calculation stage corresponding to existing unified variables in the unified variable space. When any variable name cannot achieve consistency matching with existing unified variables in the unified variable space, the feasible domain reconstruction device does not merge any variable name into existing unified variables. The feasible domain reconstruction device generates a variable scope branch within the unified variable space based on the variable source, value unit, cross-sectional location, force combination, and calculation stage corresponding to any variable name. The variable scope branch is used to store formulaic rules that cannot be processed using the same variable scope as existing unified variables.

[0153] Subsequently, the feasible domain reconstruction device writes the formula-type rules, variable sources, value units, cross-sectional locations, force combinations, and calculation stages into the variable scope branch. The feasible domain reconstruction device first writes the formula-type rule containing any variable name into the variable scope branch. Then, it writes the variable source, value unit, cross-sectional location, force combination, and calculation stage corresponding to any variable name into the variable scope branch. When there are at least two formula-type rules in the same variable scope branch, the feasible domain reconstruction device continues to determine whether the variable names in the at least two formula-type rules have consistent variable sources, value units, cross-sectional locations, force combinations, and calculation stages. When the variable names in the at least two formula-type rules have consistent variable sources, value units, cross-sectional locations, force combinations, and calculation stages, the feasible domain reconstruction device retains the at least two formula-type rules in the same variable scope branch. When the variable names in the at least two formula-type rules do not have consistent variable sources, value units, cross-sectional locations, force combinations, or calculation stages, the feasible domain reconstruction device generates a separate variable scope branch for the inconsistent variable names.

[0154] Furthermore, the feasible region reconstruction device constructs a feasible region based on variable caliber branches. The device reads formulaic rules from the variable caliber branches and, within the variable caliber branch's defined variable source, value unit, cross-sectional location, force combination, and calculation stage, reads formula variable fields and constraint parameter fields. Based on the formula variable fields and constraint parameter fields within the variable caliber branches, the device calculates the value range corresponding to each variable caliber branch. When a rule record within a variable caliber branch references only one formula variable field, the device calculates a single-parameter feasible region within the variable caliber branch. When a rule record within a variable caliber branch references at least two formula variable fields, or when there is a cross-reference between formula variable fields and constraint parameter fields within the variable caliber branch, the device calculates a multi-dimensional coupled feasible region within the variable caliber branch. The device writes the variable caliber branches, their corresponding single-parameter feasible regions, or multi-dimensional coupled feasible regions into the correspondence relationship and retains the variable caliber branch correspondence relationship in subsequent consistency constraint sets or rollback sequences.

[0155] In this embodiment, for formula-type rules that cannot be normalized to the same unified variable space, the feasible region reconstruction device does not perform formula replacement; the feasible region reconstruction device retains the formula-type rules that cannot be normalized to the same unified variable space in the variable caliber branches respectively, and constructs the feasible region under the variable source, value unit, cross-sectional position, force combination and calculation stage defined by the variable caliber branches; thus, the subsequent feasible region construction can distinguish the rule records corresponding to different variable calibers, and avoid treating incomparable formula-type rules as the same formula-type rule.

[0156] Example 8:

[0157] Figure 5 This is a logic diagram for constructing a single-parameter feasible domain and a multi-dimensional coupled feasible domain, provided in an embodiment of this application. Based on embodiment 1, this embodiment further provides an implementation method for constructing feasible domains for each sub-design scenario.

[0158] Specifically, the feasible domain reconstruction device calculates the single-parameter feasible domain based on rule records where the constraint parameter field references only one formula variable field. The device first reads the sub-scenario rule set, common applicable conditions, and unified variable space corresponding to the sub-design scenario. Then, it reads the constraint parameter field and formula variable field of each rule record in the sub-scenario rule set. When a rule record's constraint parameter field references only one formula variable field, the device identifies that rule record as a single-parameter rule record. The device reads the unified variable corresponding to the single-parameter rule record from the unified variable space and determines the design parameter value range corresponding to the unified variable based on the upper limit constraint, lower limit constraint, equivalent constraint, or interval constraint recorded in the constraint parameter field. When at least two single-parameter rule records restrict the same unified variable, the device performs intersection processing on the design parameter value ranges corresponding to the at least two single-parameter rule records and determines the intersection result as the single-parameter feasible domain.

[0159] Subsequently, the feasible domain reconstruction device categorizes rule records whose constraint parameter fields reference at least two formula variable fields into variable coupling rule groups. The feasible domain reconstruction device reads the constraint parameter fields of each rule record and counts the number of formula variable fields referenced by the constraint parameter fields. When a rule record's constraint parameter fields reference at least two formula variable fields, the feasible domain reconstruction device determines that the rule record involves common constraints between at least two unified variables. The feasible domain reconstruction device writes a rule record into the variable coupling rule group and retains the correspondence between the constraint parameter fields, formula variable fields, and unified variables corresponding to a rule record in the variable coupling rule group.

[0160] Furthermore, the feasible domain reconstruction device categorizes rule records where at least one rule record's formula variable field references another rule record's constraint parameter field into a variable coupling rule group; the feasible domain reconstruction device reads the field reference relationships between rule records in the sub-scene rule set; when the formula variable field of the first rule record references the constraint parameter field of the second rule record, the feasible domain reconstruction device determines that there is a cross-reference relationship between the first and second rule records; the feasible domain reconstruction device writes the first and second rule records together into the variable coupling rule group; when multiple rule records form a cross-reference relationship through formula variable fields and constraint parameter fields, the feasible domain reconstruction device writes multiple rule records into the same variable coupling rule group and retains the field reference relationships between multiple rule records.

[0161] Subsequently, the feasible domain reconstruction device calculates the multidimensional coupled feasible domain; the feasible domain reconstruction device reads all rule records in the variable coupling rule group, and reads the constraint parameter fields, formula variable fields, and uniform variables corresponding to all rule records; the feasible domain reconstruction device converts each rule record into a constraint expression record; the constraint expression record includes the rule record identifier, common applicable conditions, uniform variables participating in the constraint calculation, comparison direction corresponding to the constraint parameter field, boundary values ​​corresponding to the constraint parameter field, source of boundary values, and unit of boundary values; the comparison direction is used to record whether the constraint parameter field forms an upper limit constraint, lower limit constraint, equivalent constraint, or interval constraint on the uniform variable; the source of boundary values ​​is used to record whether the boundary values ​​come from the engineering specification knowledge base, steel structure design model, parameter generation module, or constraint parameter field of another rule record; when there are uniform variables with inconsistent units in the constraint expression record, the feasible domain reconstruction device first performs unit conversion according to the units in the variable caliber mapping table, and then writes it into the constraint expression record.

[0162] After converting the rule records in the variable coupling rule group into constraint expression records, the feasible region reconstruction device can represent the multidimensional coupled feasible region corresponding to the p-th variable coupling rule group according to the following formula:

[0163] ;

[0164] in, This represents the multidimensional coupling feasible region corresponding to the p-th variable coupling rule group; This represents the combination of uniform variable values ​​in the p-th variable coupling rule group; This represents the r-th unified variable in the p-th variable coupling rule group; This represents the number of uniform variables in the p-th variable coupling rule group; This represents the combination of allowed value ranges for each unified variable in the p-th variable coupling rule group; This indicates the computational relationship corresponding to the h-th constraint expression record; This indicates the comparison direction corresponding to the h-th constraint expression record. The comparison direction includes ≤, ≥, =, or interval inclusion relationship. This indicates the boundary value corresponding to the h-th constraint expression record; This represents the total number of constraint expression records in the p-th variable coupling rule group.

[0165] When a unified variable corresponds to a numerical range and the calculation relationship type is an undetermined monotonicity calculation relationship, the feasible region reconstruction device can subdivide the numerical range according to a preset minimum segmentation step size:

[0166] ;

[0167] in, This represents the q-th subinterval to be verified; represents the lower bound of the numerical interval before subdivision; u represents the upper bound of the numerical interval before subdivision; This indicates the preset minimum segmentation step size; This represents the index of the sub-interval to be verified.

[0168] The preset minimum segment step size is read from the engineering specification knowledge base, steel structure design model, or parameter generation module. The preset minimum segment step size is set based on the accuracy of the design parameters corresponding to the target steel structure design object, the minimum interval of the corresponding parameters in the engineering specification knowledge base, or the minimum adjustment unit allowed by the parameter generation module.

[0169] The feasible domain reconfiguration device can determine whether the combination of uniform variable values ​​satisfies all constraint expression records using the following formula:

[0170] ;

[0171] in, Represents a combination of values ​​for a uniform variable. The corresponding constraint satisfaction results; =1 indicates a unified combination of variable values. Records of all constraint expressions that satisfy the p-th variable coupling rule group; =0 indicates a uniform combination of variable values. Records that do not satisfy at least one constraint expression.

[0172] The feasible region reconfiguration device can determine whether the multidimensional coupled feasible region corresponding to the p-th variable coupling rule group is empty using the following formula:

[0173] ;

[0174] in, This represents the number of uniform variable value combinations that satisfy all constraint expression records. When the number of uniform variable value combinations that satisfy all constraint expression records is zero, the feasible region reconstruction device determines the multidimensional coupled feasible region as empty. When the number of uniform variable value combinations that satisfy all constraint expression records is not zero, the feasible region reconstruction device determines the corresponding uniform variable value combination as the multidimensional coupled feasible region.

[0175] The feasible domain reconstruction device generates value combinations based on the allowed value ranges of each unified variable in the variable coupling rule group. The allowed value ranges of the unified variables are read from the steel structure design model, parameter generation module, or engineering specification knowledge base. When a unified variable corresponds to a discrete value, the feasible domain reconstruction device writes the discrete value into the value combination item by item. When a unified variable corresponds to a numerical interval, the feasible domain reconstruction device reads the boundary values ​​appearing in the constraint parameter field and formula variable field, and segments the numerical interval with the boundary values ​​to obtain the segmented numerical interval. The feasible domain reconstruction device reads the calculation relationship corresponding to the formula variable field and reads the calculation relationship type from the engineering specification knowledge base, parameter generation module, or rule record. The calculation relationship type includes linear calculation relationship, monotonic calculation relationship, and calculation relationship with undetermined monotonicity.

[0176] When the calculation relationship type is linear, the feasible region reconstruction device substitutes the lower and upper bound values ​​of the segmented numerical intervals into the calculation relationship corresponding to the formula variable fields to obtain the lower and upper bound calculation results. Based on these results, the device determines the range of calculation results corresponding to the segmented numerical intervals. When the range of calculation results satisfies the comparison direction and boundary values ​​in the constraint expression record, the device retains the segmented numerical intervals. When the range of calculation results does not satisfy the comparison direction and boundary values ​​in the constraint expression record, the device deletes the segmented numerical intervals. When only a portion of the range of calculation results satisfies the comparison direction and boundary values ​​in the constraint expression record, the device uses the boundary values ​​in the constraint expression record to reverse-determine the boundaries of the segmented numerical intervals that can be retained, and retains the portion of the intervals that satisfy the constraint expression record.

[0177] When the calculation relationship type is a monotonic calculation relationship, the feasible region reconstruction device reads the monotonic direction; the monotonic direction is read from the calculation relationship description in the engineering specification knowledge base, parameter generation module, or rule record; when the monotonic direction is that the calculation result increases with the increase of the unified variable value, the feasible region reconstruction device determines the calculation result corresponding to the lower bound value of the segmented numerical interval as the lower bound of the interval calculation, and determines the calculation result corresponding to the upper bound value of the segmented numerical interval as the upper bound of the interval calculation; when the monotonic direction is that the calculation result decreases with the increase of the unified variable value, the feasible region reconstruction device will... The calculation result corresponding to the upper bound of the segmented numerical interval is determined as the lower bound of the interval calculation, and the calculation result corresponding to the lower bound of the segmented numerical interval is determined as the upper bound of the interval calculation. The feasible region reconstruction device determines whether the segmented numerical interval satisfies the comparison direction and boundary value in the constraint expression record based on the lower bound and upper bound of the interval calculation. When the segmented numerical interval satisfies the constraint expression record, the feasible region reconstruction device retains the segmented numerical interval. When the segmented numerical interval does not satisfy the constraint expression record, the feasible region reconstruction device deletes the segmented numerical interval.

[0178] When the computational relationship type is a computational relationship with undetermined monotonicity, the feasible domain reconstruction device subdivides the segmented numerical intervals according to a preset minimum segmentation step size, resulting in multiple sub-intervals to be verified. The preset minimum segmentation step size is read from the engineering specification knowledge base, the steel structure design model, or the parameter generation module. The preset minimum segmentation step size is set based on the accuracy of the design parameters corresponding to the target steel structure design object, the minimum interval of the corresponding parameters in the engineering specification knowledge base, or the minimum adjustment unit allowed by the parameter generation module. The feasible domain reconstruction device substitutes the lower and upper bound values ​​of each sub-interval to be verified into the computational relationship corresponding to the formula variable field, and determines whether each sub-interval to be verified satisfies the constraint expression record. When the sub-interval to be verified satisfies the constraint expression record, the feasible domain reconstruction device retains the sub-interval to be verified. When the sub-interval to be verified does not satisfy the constraint expression record, the feasible domain reconstruction device deletes the sub-interval to be verified.

[0179] When the computational relation type is a computational relation with undetermined monotonicity, and it is still impossible to determine whether the sub-interval to be verified satisfies the constraint expression record after subdividing according to the preset minimum segmentation step size, the feasible domain reconstruction device determines whether a constraint solver is configured in the engineering specification knowledge base or parameter generation module; the constraint solver adopts interval branch verification logic; the interval branch verification logic is to combine the allowed value ranges corresponding to each unified variable into candidate value range combinations, and take the constraint expression record, the allowed value range of the unified variable, the common applicable conditions, and the variable scope branch as input; the constraint solver performs constraint expression record verification for each candidate value range combination.

[0180] When the constraint solver performs constraint expression record verification on candidate value range combinations, it first reads the lower and upper bound values ​​of each unified variable in the candidate value range combination, and substitutes the lower and upper bound values ​​into the calculation relationship corresponding to the formula variable field to obtain the calculation result range. When the calculation result range as a whole satisfies the comparison direction and boundary values ​​in the constraint expression record, the constraint solver retains the candidate value range combination. When the calculation result range as a whole does not satisfy the comparison direction and boundary values ​​in the constraint expression record, the constraint solver deletes the candidate value range combination. When a part of the calculation result range satisfies the constraint expression record and another part does not satisfy the constraint expression record, the constraint solver continues to split the candidate value range combination according to the preset minimum segmentation step size.

[0181] When the candidate value range combination is split, if the width of the value corresponding to each unified variable is not greater than the preset minimum segmentation step size, the constraint solver reads the midpoint value of each unified variable in the candidate value range combination and substitutes the midpoint value into all constraint expression records. When the midpoint value satisfies all constraint expression records, the constraint solver retains the candidate value range combination as the minimum usable value range combination. When the midpoint value does not satisfy any constraint expression record, the constraint solver deletes the candidate value range combination. The preset minimum segmentation step size is read from the engineering specification knowledge base, the steel structure design model, or the parameter generation module. The preset minimum segmentation step size is set based on the value accuracy of the design parameters corresponding to the target steel structure design object, the minimum interval of the corresponding parameters in the engineering specification knowledge base, or the minimum adjustment unit allowed by the parameter generation module.

[0182] After the constraint solver completes the verification of all candidate value range combinations, if the number of retained candidate value range combinations is not zero, the feasible region reconstruction device will determine the value range of the unified variable corresponding to the retained candidate value range combinations as the multidimensional coupled feasible region; if the number of retained candidate value range combinations is zero, the feasible region reconstruction device will determine the multidimensional coupled feasible region as empty; when no constraint solver is configured, or the constraint solver cannot complete the verification of candidate value range combinations, the feasible region reconstruction device will generate a solution failure prompt and write the solution failure prompt, the corresponding rule record, the corresponding constraint expression record, and the corresponding unified variable into the input data of the rollback order.

[0183] To facilitate understanding of the formation process of the multidimensional coupled feasible region, the flange width and flange thickness of a steel beam are used as an example for illustration. The unified variable value combination includes flange width and flange thickness. The allowable values ​​for flange width are 180mm, 200mm, and 220mm. The allowable values ​​for flange thickness are 10mm, 12mm, and 14mm. The constraint expression records include a width-to-thickness ratio not greater than 18 and a flange thickness not less than 12mm. The feasible region reconstruction device first forms the value combination of flange width and flange thickness, and then verifies one by one whether each value combination simultaneously satisfies a width-to-thickness ratio not greater than 18 and a flange thickness not less than 12mm.

[0184] For example, when the flange width is 180mm and the flange thickness is 10mm, the width-to-thickness ratio is 18, but the flange thickness is less than 12mm, so the value combination is deleted; when the flange width is 220mm and the flange thickness is 12mm, the width-to-thickness ratio is 18.33, which is greater than 18, so the value combination is deleted; when the flange width is 200mm and the flange thickness is 12mm, the width-to-thickness ratio is 16.67, and the flange thickness is not less than 12mm, so the value combination is retained; when the flange width is 220mm and the flange thickness is 14mm, the width-to-thickness ratio is 15.71, and the flange thickness is not less than 12mm, so the value combination is retained; the feasible region reconfiguration device will summarize the retained value combinations to obtain the multidimensional coupled feasible region.

[0185] Finally, the feasible region reconstruction device merges the single-parameter feasible region and the multi-dimensional coupled feasible region to obtain the feasible region. The feasible region reconstruction device first reads the single-parameter feasible region and the multi-dimensional coupled feasible region calculated within the same sub-design scenario. When there is a single-parameter rule record within the same sub-design scenario but no variable coupling rule group, the feasible region reconstruction device only performs the feasible region non-empty judgment based on the single-parameter feasible region, and the ungenerated multi-dimensional coupled feasible region does not participate in the feasible region non-empty judgment. When there is no single-parameter rule record within the same sub-design scenario but there is a variable coupling rule group, the feasible region reconstruction device only performs the feasible region non-empty judgment based on the multi-dimensional coupled feasible region, and the ungenerated single-parameter feasible region does not participate in the feasible region non-empty judgment. When there are both single-parameter rule records and variable coupling rule groups within the same sub-design scenario, the feasible region reconstruction device reads both the single-parameter feasible region and the multi-dimensional coupled feasible region simultaneously.

[0186] When a single-parameter feasible region and a multi-dimensional coupled feasible region restrict the same unified variable, the feasible region reconstruction device performs intersection processing on the value ranges corresponding to the same unified variable. When a single-parameter feasible region and a multi-dimensional coupled feasible region restrict different unified variables, the feasible region reconstruction device writes the value ranges corresponding to different unified variables into the feasible region of the same sub-design scenario. When there are value ranges that satisfy common applicable conditions among the value ranges participating in the feasible region non-empty judgment, the feasible region reconstruction device determines the merged result as a non-empty feasible region. When there are no value ranges that satisfy common applicable conditions among the value ranges participating in the feasible region empty domain judgment, the feasible region reconstruction device determines the merged result as an empty feasible region. Ungenerated single-parameter feasible regions or ungenerated multi-dimensional coupled feasible regions do not participate in the feasible region non-empty judgment and feasible region empty domain judgment.

[0187] The feasible domain reconfiguration device can determine the feasible domain corresponding to the s-th sub-design scenario according to the following formula:

[0188] ;

[0189] in, This represents the feasible region corresponding to the s-th sub-design scenario; This represents the single-parameter feasible region corresponding to the s-th sub-design scenario; ∩ represents the multidimensional coupled feasible region corresponding to the s-th sub-design scenario; ∩ represents the intersection processing of the value range of the same unified variable; × represents the joint writing of the value range of different unified variables into the feasible region of the same sub-design scenario; ungenerated single-parameter feasible regions or ungenerated multidimensional coupled feasible regions do not participate in the feasible region spatial domain judgment.

[0190] The feasible domain reconfiguration device can determine whether the feasible domain corresponding to the s-th sub-design scenario is empty using the following formula: This indicates that the feasible domain corresponding to the s-th sub-design scenario is empty; This indicates that the feasible region corresponding to the s-th sub-design scenario is non-empty.

[0191] In this embodiment, the feasible domain reconstruction device can convert rule records in the variable coupling rule group into constraint expression records, and determine whether the multidimensional coupling feasible domain is empty by means of value combination verification. The single-parameter feasible domain is used to express the value range of a single component parameter under the common constraints of multiple rule records. The multidimensional coupling feasible domain is used to express the value combination that can still be retained by multiple component parameters under the common constraints of constraint expression records. Thus, the feasible domain reconstruction device can incorporate single component parameter constraints and cross-reference constraints between multiple component parameters into the feasible domain construction process, avoiding the situation where the feasible domain corresponding to the target steel structure design object is compressed into an empty state due to processing only the local strictest value.

[0192] Example 9:

[0193] In Example 8 and Figure 5 Based on the processing logic shown, this embodiment further provides an implementation method for calculating the multidimensional coupling feasible region based on the variable coupling relationship graph.

[0194] Specifically, the feasible domain reconstruction device uses the constraint parameter fields and formula variable fields in the variable coupling rule group as nodes. The device first reads each rule record in the variable coupling rule group; then it reads the constraint parameter fields and formula variable fields in each rule record. When a constraint parameter field is used to limit the range of design parameters for the target steel structure design object, the device generates a node from the constraint parameter field. When a formula variable field is used to participate in the calculation of the constraint parameter field's value, the device generates a node from the formula variable field. When the same unified variable exists in different rule records, the device merges the formula variable fields corresponding to the same unified variable into the same node. When the same constraint parameter field exists in different rule records, the device merges the same constraint parameter fields into the same node.

[0195] Subsequently, the feasible domain reconstruction device generates a variable coupling graph using the reference relationships between constraint parameter fields and formula variable fields in the rule records as edges. The device reads the reference relationships between constraint parameter fields and formula variable fields in each rule record. When a constraint parameter field references a formula variable field, the device generates an edge between the node corresponding to the constraint parameter field and the node corresponding to the formula variable field. When a constraint parameter field references at least two formula variable fields, the device generates edges between the node corresponding to the constraint parameter field and the node corresponding to each formula variable field. When a formula variable field in the first rule record references a constraint parameter field in the second rule record, the device generates an edge between the node corresponding to the formula variable field in the first rule record and the node corresponding to the constraint parameter field in the second rule record. The device then writes all nodes and all edges into the variable coupling graph.

[0196] Furthermore, the feasible domain reconstruction device groups interconnected nodes in the variable coupling graph into the same coupled variable group; the feasible domain reconstruction device randomly selects an ungrouped node in the variable coupling graph as the starting node; the feasible domain reconstruction device searches for other nodes reachable from the starting node based on the edges; the feasible domain reconstruction device groups the starting node and other nodes reachable from the starting node into the same coupled variable group; the feasible domain reconstruction device repeats the aforementioned process on the ungrouped nodes in the variable coupling graph until all nodes in the variable coupling graph are grouped into the corresponding coupled variable group; each coupled variable group retains the correspondence between the constraint parameter fields, formula variable fields, unified variables, and rule records corresponding to the nodes within the coupled variable group.

[0197] Finally, the feasible region reconstruction device calculates the multidimensional coupled feasible region within the coupled variable group; the feasible region reconstruction device reads all constraint parameter fields, all formula variable fields, and all rule records within the coupled variable group; the feasible region reconstruction device determines the unified variables corresponding to each formula variable field within the coupled variable group in the unified variable space, and converts each rule record within the coupled variable group into a constraint expression record; the constraint expression record includes the rule record identifier, common applicable conditions, unified variables participating in the constraint calculation, comparison direction corresponding to the constraint parameter field, boundary values ​​corresponding to the constraint parameter field, source of boundary values, and unit of boundary values; when the source of boundary values ​​is the constraint parameter field of another rule record, the feasible region reconstruction device first reads the value range corresponding to the constraint parameter field of the other rule record, and then uses the read value range as the source of boundary values ​​for the current constraint expression record.

[0198] The feasible domain reconstruction device reads the allowed value ranges of each unified variable within the coupled variable group and generates value combinations corresponding to the coupled variable group. The device verifies each value combination according to the constraint expression records. When a value combination satisfies all constraint expression records within the coupled variable group, the device retains the value combination. When a value combination does not satisfy any constraint expression record, the device deletes the value combination. After verifying all value combinations, the device determines whether the number of remaining value combinations is zero. When the number of remaining value combinations is not zero, the device defines the unified variable value range corresponding to the remaining value combinations as the multidimensional coupled feasible domain. When the number of remaining value combinations is zero, the device defines the multidimensional coupled feasible domain corresponding to the coupled variable group as empty.

[0199] Through this embodiment, the feasible domain reconstruction device can convert the constraint parameter fields, formula variable fields, and reference relationships in the variable coupling rule group into a variable coupling relationship diagram; the variable coupling relationship diagram can represent the field reference relationships formed by rule records between the slenderness ratio, width-to-thickness ratio, cross-sectional dimensions, connection bearing capacity, and stability parameters; the feasible domain reconstruction device then calculates the multidimensional coupled feasible domain in units of coupled variable groups, so that multiple component parameters jointly satisfy the rule records in the variable coupling rule group.

[0200] Example 10:

[0201] Based on Example 8, this example further provides an implementation method for calculating multidimensional coupling feasible regions based on a set of cross-reference rules.

[0202] Specifically, when at least two rule records have cross-references in at least two formula variable fields, the feasible domain reconstruction device summarizes the corresponding rule records into a coupled rule set. The feasible domain reconstruction device first reads the formula variable fields and constraint parameter fields of each rule record in the sub-scene rule set. When the formula variable field of the first rule record references the constraint parameter field of the second rule record, and the formula variable field of the second rule record references the constraint parameter field of the first rule record, the feasible domain reconstruction device determines that the first rule record and the second rule record have cross-references. When the formula variable field of the first rule record references the constraint parameter field of the second rule record, and the formula variable field of the second rule record references the constraint parameter field of the third rule record, and the aforementioned reference relationship involves at least two formula variable fields, the feasible domain reconstruction device determines that the first rule record, the second rule record, and the third rule record have cross-references. The feasible domain reconstruction device summarizes the rule records with cross-references into a coupled rule set, and retains the formula variable field, constraint parameter field, unified variable, and common applicable conditions of each rule record in the coupled rule set.

[0203] Subsequently, the feasible region reconstruction device calculates the multidimensional coupled feasible region that simultaneously satisfies the rule records in the coupled rule set. The feasible region reconstruction device first reads all formula variable fields and all constraint parameter fields in the coupled rule set. The feasible region reconstruction device then determines the unified variables corresponding to all formula variable fields in the unified variable space. The feasible region reconstruction device converts each rule record in the coupled rule set into a constraint expression record. The constraint expression record includes the rule record identifier, common applicable conditions, unified variables participating in the constraint calculation, comparison direction corresponding to the constraint parameter field, boundary values ​​corresponding to the constraint parameter field, source of boundary values, and unit of boundary values. When a formula variable field references a constraint parameter field of another rule record, the feasible region reconstruction device writes the value range corresponding to the referenced constraint parameter field into the source of boundary values ​​of the current constraint expression record.

[0204] The feasible region reconstruction device generates value combinations based on the allowed value ranges of each unified variable in the coupling rule set, and verifies each value combination according to the constraint expression record. When a constraint parameter field is affected by at least two formula variable fields, the feasible region reconstruction device uses the unified variables corresponding to the at least two formula variable fields as joint verification objects in the same value combination, and substitutes the value combination into the calculation relationship of the formula variable field recorded in the corresponding rule. The feasible region reconstruction device determines whether the value combination satisfies the comparison direction and boundary values ​​corresponding to the constraint parameter field based on the calculation results. When the value group... When a value combination satisfies all constraint expressions in the coupling rule set, the feasible region reconstruction device retains the value combination. When a value combination does not satisfy any constraint expression in the coupling rule set, the feasible region reconstruction device deletes the value combination. After completing the verification of all value combinations, the feasible region reconstruction device determines whether the number of remaining value combinations is zero. When the number of remaining value combinations is not zero, the feasible region reconstruction device determines the range of values ​​of the unified variable corresponding to the remaining value combinations as the multidimensional coupled feasible region. When the number of remaining value combinations is zero, the feasible region reconstruction device determines the multidimensional coupled feasible region as empty.

[0205] Through this embodiment, the feasible domain reconstruction device can perform set processing on rule records with cross-references without generating a variable coupling relationship graph; the set of coupled rules can retain the reference relationship between formula variable fields, constraint parameter fields and unified variables; the feasible domain reconstruction device obtains multi-dimensional coupled feasible domains on the basis of the set of coupled rules, so that multiple component parameters with cross-references can participate in the construction of feasible domains under the same common applicable conditions.

[0206] Example 11:

[0207] Figure 6 This is a logic diagram of a consistency constraint set and a rollback order output provided in an embodiment of this application; based on embodiment 8, this embodiment further provides an implementation method for writing feasible domains into the consistency constraint set.

[0208] Specifically, when the feasible region is not empty, the feasible region reconstruction device writes the sub-design scenario, common applicable conditions, the calculated single-parameter feasible region that participates in forming the feasible region, the calculated multi-dimensional coupled feasible region that participates in forming the feasible region, and the corresponding rule records into the consistency constraint set; the feasible region reconstruction device first reads the feasible region judgment result corresponding to the sub-design scenario; when only single-parameter feasible regions are generated within the same sub-design scenario, the feasible region reconstruction device uses whether the single-parameter feasible region has a value range that satisfies the common applicable conditions as the basis for judging whether the feasible region is not empty, and the ungenerated multi-dimensional coupled feasible regions do not participate in the feasible region not empty judgment and feasible region empty region judgment; when only multi-dimensional coupled feasible regions are generated within the same sub-design scenario, the feasible region reconstruction device uses whether the multi-dimensional coupled feasible region has a value range that satisfies the common applicable conditions as the basis for judging whether the feasible region is not empty, and the ungenerated single-parameter feasible regions do not participate in the feasible region not empty judgment and feasible region empty region judgment; when simultaneously within the same sub-design scenario... When generating single-parameter feasible regions and multi-dimensional coupled feasible regions, the feasible region reconstruction device uses the existence of a range of values ​​that satisfy common applicable conditions after merging the single-parameter feasible region and the multi-dimensional coupled feasible region as the criterion for determining whether the feasible region is non-empty. When the feasible region determination result indicates that the feasible region is non-empty, the feasible region reconstruction device writes the seismic resistance level, fire protection level, component category, stress state, design stage, and load combination conditions corresponding to the sub-design scenario into the consistency constraint set, writes the common applicable conditions into the consistency constraint set, writes the unified variables, design parameter value ranges, and rule records corresponding to the single-parameter feasible regions that have been generated and participated in forming the feasible region into the consistency constraint set, and writes the unified variables, design parameter value ranges, field reference relationships, and rule records corresponding to the multi-dimensional coupled feasible regions that have been generated and participated in forming the feasible region into the consistency constraint set. The feasible region reconstruction device does not write ungenerated single-parameter feasible regions or ungenerated multi-dimensional coupled feasible regions into the consistency constraint set.

[0209] Subsequently, the downstream steel structure parameter generation module reads the consistency constraint set and generates steel structure design parameters under the corresponding sub-design scenarios and common applicable conditions. The downstream steel structure parameter generation module first reads the target design scenario space corresponding to the target steel structure design object and converts the target design scenario space into a target condition element set. The target condition element set is formed by combining seismic resistance level, fire resistance level, component type, stress state, design stage, and load combination conditions in the target design scenario space. The downstream steel structure parameter generation module then reads the sub-design scenarios in the consistency constraint set line by line and reads the condition element set corresponding to each sub-design scenario. When the target... When each condition unit in the component unit set belongs to the condition unit set corresponding to the same sub-design scenario, and the seismic resistance level, fire resistance level, component type, stress state, design stage, and load combination conditions in the target design scenario space all meet the common applicable conditions corresponding to the same sub-design scenario, the downstream steel structure parameter generation module determines that the target design scenario space matches the same sub-design scenario; when the target condition unit set spans at least two sub-design scenarios, the downstream steel structure parameter generation module splits the target design scenario space according to the condition unit boundary corresponding to the sub-design scenario, and reads the consistency constraint set corresponding to each split target design scenario space fragment.

[0210] When the target design scenario space matches a sub-design scenario in the consistency constraint set, the downstream steel structure parameter generation module reads the common applicable conditions corresponding to a sub-design scenario, the single-parameter feasible domain that has been generated and participates in forming the feasible domain, and the multi-dimensional coupled feasible domain that has been generated and participates in forming the feasible domain. When a sub-design scenario generates only a single-parameter feasible domain, the downstream steel structure parameter generation module uses the single-parameter feasible domain as the constraint input for generating steel structure design parameters. When a sub-design scenario generates only a multi-dimensional coupled feasible domain, the downstream steel structure parameter generation module uses the multi-dimensional coupled feasible domain as the constraint input for generating steel structure design parameters. When a sub-design scenario generates both single-parameter feasible domains and multi-dimensional coupled feasible domains, the downstream steel structure parameter generation module uses the merged result of the single-parameter feasible domain and the multi-dimensional coupled feasible domain as the constraint input for generating steel structure design parameters. The downstream steel structure parameter generation module generates the steel structure design parameters corresponding to the target steel structure design object within the value range limited by the constraint input.

[0211] In this embodiment, the consistency constraint set not only retains the feasible region results, but also the sub-design scenarios, common applicable conditions, and rule records corresponding to the feasible region results. The sub-design scenarios are used to describe the target design scenario space range to which the feasible region results are applicable. The common applicable conditions are used to describe the condition range under which the rule records corresponding to the feasible region results are jointly valid. The rule records are used to describe the standard source and constraint source corresponding to the feasible region results. As a result, the downstream steel structure parameter generation module can generate steel structure design parameters based on the consistency constraint set, and the automatic review system can also read the rule record source corresponding to the feasible region results based on the consistency constraint set.

[0212] Through the above processing, when the sub-design scenario contains only single-parameter rule records, the consistency constraint set uses the single-parameter feasible region as the feasible region result; when the sub-design scenario contains only variable coupling rule groups, the consistency constraint set uses the multi-dimensional coupling feasible region as the feasible region result; when the sub-design scenario contains both single-parameter rule records and variable coupling rule groups, the consistency constraint set uses the merged result of the single-parameter feasible region and the multi-dimensional coupling feasible region as the feasible region result; therefore, the failure to generate a single-parameter feasible region or a multi-dimensional coupling feasible region will not cause the non-empty judgment of the feasible region to fail.

[0213] Example 12:

[0214] In Examples 8 and 11, and Figure 6 Based on the processing logic shown, this embodiment further provides an implementation method for generating a fallback order based on a single candidate upstream design variable.

[0215] Specifically, when the feasible domain is empty, the feasible domain reconstruction device reads the upstream design variable mapping field from the rule record that participated in forming the empty feasible domain. The upstream design variable mapping field comes from the mapping processing results between the constraint parameter field, formula variable field, steel structure design model, parameter generation module, and engineering specification knowledge base in the rule record. The feasible domain reconstruction device first reads the feasible domain judgment result corresponding to the sub-design scenario. When only a single-parameter feasible domain is generated in the same sub-design scenario, the feasible domain reconstruction device checks whether the single-parameter feasible domain is empty. As a basis for determining the spatial domain of the feasible domain, ungenerated multidimensional coupled feasible domains do not participate in the spatial domain determination. When only multidimensional coupled feasible domains are generated within the same sub-design scenario, the feasible domain reconstruction device uses whether the multidimensional coupled feasible domain is empty as the basis for determining the spatial domain of the feasible domain, and ungenerated single-parameter feasible domains do not participate in the spatial domain determination. When both single-parameter feasible domains and multidimensional coupled feasible domains are generated within the same sub-design scenario, the feasible domain reconstruction device uses whether the merged single-parameter feasible domain and multidimensional coupled feasible domain are empty as the basis for determining the spatial domain of the feasible domain.

[0216] When the feasible domain is empty, the feasible domain reconstruction device determines the rule records that participate in forming the empty feasible domain and reads the upstream design variable mapping field in the corresponding rule record. The feasible domain reconstruction device reads the upstream design variable, the affected constraint parameter field or formula variable field, the value range of the upstream design variable before the change, the allowed value range of the upstream design variable, and the data source of the upstream design variable recorded in the upstream design variable mapping field. When there is no adjustable upstream design variable recorded in the upstream design variable mapping field, the feasible domain reconstruction device does not generate a fallback order based on a single candidate upstream design variable and writes the corresponding rule record with a prompt message indicating that the upstream design variable mapping result is missing.

[0217] Subsequently, the feasible domain reconstruction device generates candidate upstream design variables; the feasible domain reconstruction device reads the design variables whose value range can be adjusted from the upstream design variable mapping field, and determines the design variables whose value range can be adjusted as candidate upstream design variables; when one upstream design variable mapping field corresponds to one design variable, the feasible domain reconstruction device determines one design variable as one candidate upstream design variable; when one upstream design variable mapping field corresponds to at least two design variables, the feasible domain reconstruction device reads at least two design variables respectively, and determines at least two design variables as candidate upstream design variables respectively; when generating candidate upstream design variables, the feasible domain reconstruction device retains the correspondence between the candidate upstream design variables and the rule records participating in the formation of the empty feasible domain.

[0218] Furthermore, the feasible region reconstruction device changes the value range corresponding to each candidate upstream design variable and recalculates the single-parameter feasible region or multi-dimensional coupled feasible region. The feasible region reconstruction device first reads the value range of each candidate upstream design variable before the change, and reads the allowed value range corresponding to the candidate upstream design variable from the steel structure design model, parameter generation module, or engineering specification knowledge base. The allowed value range is used to limit the value boundary or value set to which the candidate upstream design variable can be adjusted. The feasible region reconstruction device records the verification results and determines the conflict type according to the constraint expression corresponding to the empty feasible region. The conflict types include upper limit less than lower limit, equal constraint conflict, no intersection of intervals, and no satisfyable value combination of coupled constraints.

[0219] When the conflict type is that the upper limit is less than the lower limit, the feasible region reconstruction device reads the upper limit boundary and the lower limit boundary that form an empty feasible region. When the candidate upstream design variable affects the upper limit boundary, the feasible region reconstruction device determines the candidate boundary that can increase the upper limit boundary and is within the allowed value range as the candidate change range. When the candidate upstream design variable affects the lower limit boundary, the feasible region reconstruction device determines the candidate boundary that can decrease the lower limit boundary and is within the allowed value range as the candidate change range. When the candidate upstream design variable affects both the upper limit boundary and the lower limit boundary, the feasible region reconstruction device calculates the upper limit boundary and the lower limit boundary corresponding to the change of the candidate upstream design variable, and determines the candidate boundary that can make the upper limit boundary not less than the lower limit boundary as the candidate change range.

[0220] When the conflict type is an equivalent constraint conflict, the feasible region reconstruction device reads the boundary values ​​corresponding to the conflicting equivalent constraints. When the boundary values ​​corresponding to at least two equivalent constraints are inconsistent, the feasible region reconstruction device determines the candidate boundary that can make the boundary values ​​corresponding to at least two equivalent constraints equal as the candidate change range. When the boundary value corresponding to the equivalent constraint does not belong to the allowed value range of a single-parameter feasible region or a multi-dimensional coupled feasible region, the feasible region reconstruction device determines the candidate boundary that can make the boundary value corresponding to the equivalent constraint enter the allowed value range as the candidate change range.

[0221] When the conflict type is no intersection of intervals, the feasible region reconstruction device reads each value interval involved in the intersection processing and determines the highest lower limit boundary and the lowest upper limit boundary in each value interval. When the candidate upstream design variable affects the highest lower limit boundary, the feasible region reconstruction device determines the candidate boundary that can lower the highest lower limit boundary and is within the allowable value range as the candidate change range. When the candidate upstream design variable affects the lowest upper limit boundary, the feasible region reconstruction device determines the candidate boundary that can raise the lowest upper limit boundary and is within the allowable value range as the candidate change range. When the candidate upstream design variable affects both the highest lower limit boundary and the lowest upper limit boundary, the feasible region reconstruction device calculates the highest lower limit boundary and the lowest upper limit boundary corresponding to the change of the candidate upstream design variable, and determines the candidate boundary that can make the highest lower limit boundary no greater than the lowest upper limit boundary as the candidate change range.

[0222] When the conflict type is a coupling constraint with no satisfyable value combination, the feasible region reconstruction device reads the deleted value combination and the constraint expression record that caused the value combination to be deleted; when the value combination is deleted because the calculation result exceeds the upper limit constraint, the feasible region reconstruction device can either increase the boundary value corresponding to the upper limit constraint or decrease the candidate boundary of the calculation result corresponding to the formula variable field to determine the candidate change range; when the value combination is deleted because the calculation result is lower than the lower limit constraint, the feasible region reconstruction device can either decrease the boundary value corresponding to the lower limit constraint or increase the candidate boundary of the calculation result corresponding to the formula variable field to determine the candidate change range; when the value combination is deleted because it does not satisfy the equivalent constraint or the interval constraint, the feasible region reconstruction device determines the candidate change range according to the processing method corresponding to the equivalent constraint conflict or the interval non-intersection.

[0223] When the candidate upstream design variable is a numerical variable, the feasible domain reconstruction device takes the value range of the candidate upstream design variable before the change as the starting point, and uses the boundary values ​​appearing in the constraint parameter field or formula variable field as candidate boundaries. The feasible domain reconstruction device determines the candidate change range from the candidate boundaries according to the processing method corresponding to the above conflict type. When the candidate boundary cannot form a candidate change range, the feasible domain reconstruction device forms the candidate change range according to the upper or lower boundary of the allowed value range. When the candidate upstream design variable is a hierarchical variable, the feasible domain reconstruction device reads the hierarchical order corresponding to the candidate upstream design variable from the engineering specification knowledge base or parameter generation module, and determines the candidate change range from the hierarchical levels within the allowed value range according to the processing method corresponding to the above conflict type. When the candidate upstream design variable is a categorical variable, the feasible domain reconstruction device reads the replaceable category order corresponding to the candidate upstream design variable from the steel structure design model or parameter generation module, and determines the candidate change range from the categories within the allowed value range according to the processing method corresponding to the above conflict type.

[0224] Subsequently, the feasible domain reconfiguration device converts the difference between the candidate change range and the value range of the candidate upstream design variable before the change into the variable change amount. When the candidate upstream design variable is a numerical variable, the feasible domain reconfiguration device first calculates the absolute value of the change amount between the boundary value of the candidate change range and the corresponding boundary value of the value range before the change, then calculates the allowable value range width between the upper and lower boundaries of the allowable value range, and determines the variable change amount by the ratio of the absolute value of the change amount to the allowable value range width. When the allowable value range width is zero, the feasible domain reconfiguration device does not write the corresponding candidate upstream design variable into the rollback order.

[0225] When the candidate upstream design variable is a hierarchical variable, the feasible domain reconfiguration device determines the level difference between the corresponding level of the candidate change range and the level before the change according to the level order, and reads the number of allowed levels within the allowed value range; the feasible domain reconfiguration device determines the variable change amount by the ratio of the level difference to the number of allowed levels; when the number of allowed levels is less than or equal to 1, the feasible domain reconfiguration device does not write the corresponding candidate upstream design variable into the rollback order.

[0226] When the candidate upstream design variable is a categorical variable, the feasible domain reconfiguration device determines the order difference between the category corresponding to the candidate change range and the category before the change based on the order of replaceable categories, and reads the number of replaceable categories within the allowed value range; the feasible domain reconfiguration device determines the variable change amount by the ratio of the order difference to the number of replaceable categories; when the number of replaceable categories is less than or equal to 1, the feasible domain reconfiguration device does not write the corresponding candidate upstream design variable into the rollback order.

[0227] The feasible domain reconfiguration device calculates the variable change based on the variable type of the candidate upstream design variable.

[0228] For numerical candidate upstream design variables, the feasible region reconfiguration device can calculate the variable change using the following formula:

[0229] ;

[0230] in, This represents the change in the variable corresponding to the z-th candidate upstream design variable; This represents the lower bound of the value range of the z-th candidate upstream design variable before it is changed; This represents the upper bound of the value range of the z-th candidate upstream design variable before it is changed; This represents the lower bound of the candidate change range corresponding to the z-th candidate upstream design variable; This represents the upper bound of the candidate change range corresponding to the z-th candidate upstream design variable; This represents the upper bound of the allowed value range for the z-th candidate upstream design variable; This represents the lower bound of the allowed value range for the z-th candidate upstream design variable; the allowed value range is read from the steel structure design model, parameter generation module, or engineering specification knowledge base; when = When the feasible domain reconfiguration device does not write the z-th candidate upstream design variable into the fallback order.

[0231] For hierarchical candidate upstream design variables, the feasible domain reconfiguration device calculates the variable change using the following formula:

[0232] ;

[0233] in, This indicates the sequence number of the z-th candidate upstream design variable in the rank order before the change. This indicates the index of the candidate change range level of the z-th candidate upstream design variable in the level order; This represents the number of allowable levels for the z-th candidate upstream design variable within its permissible value range; the level order and the number of allowable levels are read from the engineering specification knowledge base or the parameter generation module; when When the value is ≤1, the feasible domain reconfiguration device does not write the z-th candidate upstream design variable into the fallback order; when the number of allowed levels is N, N-1 ordinal intervals are formed between adjacent levels, so N-1 is used as the normalization denominator.

[0234] For categorical candidate upstream design variables, the change in the feasible domain reconfiguration device can be calculated using the following formula:

[0235] ;

[0236] in, This represents the index of the z-th candidate upstream design variable's category in the order of replaceable categories before the change; This indicates the index of the category corresponding to the candidate change range of the z-th candidate upstream design variable in the order of replaceable categories; This represents the number of replaceable categories for the z-th candidate upstream design variable within its allowed value range; the order and number of replaceable categories are read from the steel structure design model or parameter generation module; when When the number of alternative categories is ≤1, the feasible domain reconfiguration device does not write the z-th candidate upstream design variable into the backoff order; when the number of alternative categories is N, N-1 order intervals are formed between adjacent alternative categories, so N-1 is used as the normalization denominator.

[0237] The feasible domain reconfiguration device can generate a rollback order according to the following sorting rules:

[0238] ;

[0239] in, Indicates the first The candidate upstream design variables are ranked in the fallback order as follows: Before the candidate upstream design variables; when = At that time, the feasible domain reconfiguration devices are arranged according to the order of candidate upstream design variables in the design phase; the order in the design phase is read from the steel structure design model or parameter generation module.

[0240] Finally, the feasible domain reconstruction device sorts the variables from smallest to largest according to the amount of change when the feasible domain changes from empty to non-empty, and generates a rollback order. The feasible domain reconstruction device first filters candidate upstream design variables that can change a single-parameter feasible domain or a multi-dimensional coupled feasible domain from empty to non-empty. The feasible domain reconstruction device then reads the variable change amount of the corresponding candidate upstream design variables. The feasible domain reconstruction device arranges the candidate upstream design variables in ascending order of variable change amount. When at least two candidate upstream design variables have the same variable change amount, the feasible domain reconstruction device arranges the candidate upstream design variables according to their order in the design stage. The order in the design stage is read from the steel structure design model or parameter generation module. The feasible domain reconstruction device writes the sorted candidate upstream design variables, the value range of the candidate upstream design variables before the change, the candidate change range, the variable change amount, and the corresponding rule records into the rollback order.

[0241] In this embodiment, when the single-parameter feasible region or the multi-dimensional coupled feasible region is empty, the feasible region reconstruction device can determine candidate upstream design variables based on the upstream design variable mapping field, and recalculate the single-parameter feasible region or the multi-dimensional coupled feasible region by changing the value range corresponding to a single candidate upstream design variable; when the candidate upstream design variable can make the feasible region change from empty to non-empty, the feasible region reconstruction device generates a rollback order according to the variable change amount; thus, the feasible region reconstruction device can output the upstream design variables that need to be adjusted first, avoiding only outputting infeasible solution results to the downstream steel structure parameter generation module.

[0242] Through the formation and reading process of the upstream design variable mapping field, the candidate upstream design variables in the backtracking order are derived from the correspondence between the constraint parameter field, the formula variable field, the steel structure design model, the parameter generation module, and the engineering specification knowledge base. Therefore, the backtracking order is not generated solely based on the result of an empty feasible domain, but rather based on the upstream design variables that can affect the value range of the constraint parameter field or the formula variable field.

[0243] Example 13:

[0244] In Example 12 and Figure 6 Based on the processing logic shown, this embodiment further provides an implementation method for generating a rollback order based on the combination of candidate variables.

[0245] Specifically, the feasible domain reconstruction device combines at least two candidate upstream design variables into a candidate variable combination. The feasible domain reconstruction device first reads the candidate upstream design variables generated in Example 12, and reads the value range, variable change amount, and corresponding rule record corresponding to each candidate upstream design variable. When the value range of a single candidate upstream design variable after change cannot make the single-parameter feasible domain or multi-dimensional coupled feasible domain change from empty to non-empty, the feasible domain reconstruction device selects at least two candidate upstream design variables from the candidate upstream design variables and combines the at least two candidate upstream design variables into a candidate variable combination. The candidate upstream design variables in the candidate variable combination all have a corresponding relationship with the rule record participating in the formation of the empty feasible domain. When generating the candidate variable combination, the feasible domain reconstruction device retains the value range before change, the allowed value range, and the corresponding rule record of each candidate upstream design variable in the candidate variable combination.

[0246] Subsequently, the feasible region reconstruction device changes the value range of the candidate upstream design variables in the candidate variable combination and recalculates the single-parameter feasible region or multi-dimensional coupled feasible region. The feasible region reconstruction device first reads the value range of each candidate upstream design variable in the candidate variable combination before the change. Then, based on the allowed value ranges stored in the steel structure design model, parameter generation module, or engineering specification knowledge base, the feasible region reconstruction device determines the value range of each candidate upstream design variable in the candidate variable combination after the change. The feasible region reconstruction device then modifies each candidate upstream design variable in the candidate variable combination. The range of values ​​is then substituted into the corresponding constraint parameter field or formula variable field; the feasible region reconstruction device recalculates the single-parameter feasible region or multi-dimensional coupled feasible region under the common applicable conditions; when the recalculated single-parameter feasible region or multi-dimensional coupled feasible region has a range of values ​​that meet the common applicable conditions, the feasible region reconstruction device records that the candidate variable combination can make the feasible region change from empty to non-empty; when the recalculated single-parameter feasible region or multi-dimensional coupled feasible region still does not have a range of values ​​that meet the common applicable conditions, the feasible region reconstruction device does not write the candidate variable combination into the rollback order.

[0247] Furthermore, the feasible region reconstruction device will transform the feasible region from empty to non-empty candidate variable combinations, sorting them from fewest to most candidate upstream design variables. The feasible region reconstruction device first counts the number of candidate upstream design variables contained in each candidate variable combination; then, it arranges the candidate variable combinations from fewest to most candidate upstream design variables. When at least two candidate variable combinations contain the same number of candidate upstream design variables, the feasible region reconstruction device adds up the variable changes of each candidate upstream design variable in the at least two candidate variable combinations and arranges the at least two candidate variable combinations from smallest to largest according to the sum. When the sum of the at least two candidate variable combinations is the same, the feasible region reconstruction device arranges the at least two candidate variable combinations according to the order of the design stages corresponding to the candidate upstream design variables in the candidate variable combinations. The order of the design stages is read from the steel structure design model or parameter generation module.

[0248] Finally, the feasible domain reconstruction device writes the sorting results into the rollback order; the feasible domain reconstruction device writes the candidate variable combination, the value range of each candidate upstream design variable in the candidate variable combination before the change, the value range of each candidate upstream design variable in the candidate variable combination after the change, the variable change amount of each candidate upstream design variable in the candidate variable combination, the recalculated single-parameter feasible domain or multi-dimensional coupled feasible domain, and the corresponding rule record into the rollback order; the rollback order is used to output a joint adjustment scheme that can change the feasible domain from empty to non-empty to the downstream steel structure parameter generation module; after reading the rollback order, the downstream steel structure parameter generation module prompts the candidate upstream design variables and their corresponding value ranges that need to be adjusted simultaneously according to the rollback order.

[0249] In this embodiment, when the changed value range of a single candidate upstream design variable cannot change the feasible region from empty to non-empty, the feasible region reconstruction device can combine at least two candidate upstream design variables into a candidate variable combination, and recalculate the single-parameter feasible region or multi-dimensional coupled feasible region by simultaneously changing the value range of the candidate upstream design variables in the candidate variable combination; thus, the feasible region reconstruction device can output the joint backoff direction corresponding to the candidate variable combination when the feasible region cannot be restored by a single candidate upstream design variable.

[0250] Example 14:

[0251] Figure 7 This is an example diagram of the overall processing in a steel beam application scenario provided by the embodiments of this application; based on any of the above embodiments, this embodiment further provides an example of overall processing.

[0252] Specifically, the feasible domain reconstruction device uses the steel beam as the target steel structure design object and reads the target design scenario space and conflict rule group corresponding to the steel beam. The target design scenario space includes the seismic resistance level, fire resistance level, component type, stress state, design stage, and load combination conditions corresponding to the steel beam. The feasible domain reconstruction device reads the component type, cross-sectional shape, material strength level, stress state, and load combination conditions corresponding to the steel beam from the steel structure design model, and reads multiple rule records that hit the steel beam from the engineering code knowledge base. The multiple rule records include applicable condition fields, formula variable fields, constraint parameter fields, and upstream design variable mapping fields, respectively. The feasible domain reconstruction device summarizes the multiple rule records that hit the steel beam into a conflict rule group.

[0253] Subsequently, the feasible domain reconstruction device generates a rule condition coverage relationship table based on the applicable condition field and divides it into multiple sub-design scenarios. The feasible domain reconstruction device first divides the target design scenario space into multiple condition units, then reads the applicable condition field of each rule record and determines the condition units covered by each rule record. When two rule records are applicable to different seismic resistance levels or different stress states, the feasible domain reconstruction device records a mutual exclusion relationship between the two rule records in the rule condition coverage relationship table. When two rule records cover the same seismic resistance level, the same fire resistance level, the same component category, the same stress state, the same design stage, and the same... When two rule records cover identical condition units under a single load combination, the feasible domain reconstruction device records in the rule condition coverage relationship table that the two rule records have the same coverage relationship or a common coverage relationship. When two rule records cover condition units with common condition units, and each rule record has condition units that are not covered by the other rule record, the feasible domain reconstruction device records in the rule condition coverage relationship table that the two rule records have an intersection relationship. The feasible domain reconstruction device generates sub-design scenarios according to the boundaries of the condition units and summarizes the rule records covering the same sub-design scenario into a sub-scenario rule set.

[0254] Furthermore, the feasible domain reconstruction device normalizes the formula-type rules in each sub-design scenario to generate a unified variable space or variable scope branch. The feasible domain reconstruction device reads the formula variable field in the rule set of the sub-scenario and extracts the variable name, variable source, value unit, cross-sectional location, force combination, and calculation stage from the formula variable field. When the variable names in different rule records correspond to the same variable source, the same value unit, the same cross-sectional location, the same force combination, and the same calculation stage, the feasible domain reconstruction device maps the variable names in different rule records to the same unified variable. When the variable names in different rule records correspond to different variable sources, different value units, different cross-sectional locations, different force combinations, or different calculation stages, the feasible domain reconstruction device does not map the variable names in different rule records to the same unified variable and generates the corresponding variable scope branch.

[0255] Subsequently, the feasible domain reconstruction device calculates the single-parameter feasible domain and the multi-dimensional coupled feasible domain under the unified variable space and common applicable conditions. When the constraint parameter field of a rule record references only one formula variable field, the feasible domain reconstruction device identifies the rule record as a single-parameter rule record and determines the single-parameter feasible domain based on the constraint parameter field. When the constraint parameter field of a rule record references at least two formula variable fields, the feasible domain reconstruction device categorizes the rule record into a variable coupled rule group and calculates the multi-dimensional coupled feasible domain. When the formula variable field of one rule record references the constraint parameter field of another rule record, the feasible domain reconstruction device categorizes the corresponding rule records into a variable coupled rule group and calculates the value range that simultaneously satisfies each rule record within the variable coupled rule group. The feasible domain reconstruction device merges the single-parameter feasible domain and the multi-dimensional coupled feasible domain to obtain the feasible domain of the steel beam under the corresponding sub-design scenario.

[0256] When the feasible domain is not empty, the feasible domain reconstruction device outputs a set of consistency constraints. The feasible domain reconstruction device first writes the sub-design scenarios, common applicable conditions, single-parameter feasible domains, multi-dimensional coupled feasible domains, and corresponding rule records into the set of consistency constraints. The feasible domain reconstruction device then outputs the set of consistency constraints to the downstream steel structure parameter generation module. The downstream steel structure parameter generation module reads the set of consistency constraints and generates the steel structure design parameters corresponding to the steel beams within the value range defined by the set of consistency constraints. The automatic review system reads the rule records in the set of consistency constraints and traces the standard provisions based on the rule source field, rule number field, standard version field, and provision location field.

[0257] When the feasible domain is empty, the feasible domain reconstruction device reads the upstream design variable mapping field and generates a fallback order. The device first determines the rule records involved in forming the empty feasible domain, then reads the upstream design variable mapping field from these records. Based on the upstream design variable mapping field, the device generates candidate upstream design variables and changes their corresponding value ranges. After each change in the value range of a candidate upstream design variable, the device recalculates the single-parameter feasible domain or the multi-dimensional coupled feasible domain. When the changed value range of a candidate upstream design variable enables the feasible domain to change from empty to non-empty, the device determines the variable change amount corresponding to the candidate upstream design variable. The device arranges the candidate upstream design variables in ascending order of variable change amount and writes the arrangement result into the fallback order. The downstream steel structure parameter generation module reads the fallback order and prompts the candidate upstream design variables that need adjustment and their corresponding value ranges.

[0258] Through this embodiment, the feasible domain reconstruction device can sequentially execute the following steps: generating a rule condition coverage relationship table, dividing sub-design scenarios, determining sub-scenario rule sets, determining common applicable conditions, normalizing variables, generating variable caliber branches, calculating single-parameter feasible domains, calculating multi-dimensional coupled feasible domains, outputting consistency constraint sets, and outputting rollback sequences, starting from the target steel structure design object, the target design scenario space, and the conflict rule group. As a result, those skilled in the art can execute the steel structure specification conflict feasible domain reconstruction method based on the target steel structure design object and the engineering specification knowledge base, and use the execution results for automatic review of steel structure design and generation of steel structure parameters.

[0259] The above description is merely a preferred embodiment of this application, and the scope of protection of this application shall be determined by the scope defined in the claims. Any improvements and modifications made by those skilled in the art without departing from the essence of the technical solution of this application shall fall within the scope of protection of this application. It should be noted that for those skilled in the art, any improvements and modifications made without departing from the principles of this application shall also be considered within the scope of protection of this application.

Claims

1. A method for reconstructing the feasible domain of steel structure code conflicts, characterized in that, include: Obtain the target steel structure design object, the target design scene space, and the conflict rule group. The conflict rule group includes multiple rule records that hit the same target steel structure design object. The rule record includes the applicable condition field, the formula variable field, the constraint parameter field, and the upstream design variable mapping field. Based on the target design scenario space and applicable condition fields, generate a rule condition coverage relationship table; Based on the rule condition coverage relationship table, the conflict rule group is divided into sub-design scenarios to obtain at least one sub-design scenario. Determine the set of rules for each sub-design scenario and the common applicable conditions; Formula-type rules in the sub-scene rule set are normalized to generate a unified variable space. Specifically, variable name, source, unit of measurement, cross-sectional location, force combination, calculation stage, physical meaning, and category or standard parameter code are read from the formula variable field to generate a variable caliber mapping table. When two variable names in the variable caliber mapping table have the same source, unit of measurement, cross-sectional location, force combination, and calculation stage, and the same standard parameter code, the two variable names are mapped to the same unified variable. When the standard parameter code is not read, two variable names with the same source, unit of measurement, cross-sectional location, force combination, calculation stage, physical meaning, and category are mapped to the same unified variable, forming a unified variable space. Under the conditions of a unified variable space and common applicability, the feasible domain of each sub-design scenario is constructed based on the constraint parameter field and the formula variable field; wherein, rule records in which the constraint parameter field references at least two formula variable fields, or at least one rule record's formula variable field references another rule record's constraint parameter field, are grouped into the variable coupling rule group, and the multidimensional coupling feasible domain is calculated; When the feasible region is not empty, write the feasible region into the set of consistency constraints; When the feasible domain is empty, the fallback order is generated based on the upstream design variable mapping field. Output a set of consistency constraints or a rollback order.

2. The steel structure specification conflict feasible domain reconstruction method according to claim 1, characterized in that, Methods for generating rule condition coverage relationship tables include: Divide the target design scenario space into at least one conditional unit; The condition units covered by each rule record are determined based on the applicable condition fields of each rule record; Record the same coverage relationship, containment relationship, intersection relationship and mutual exclusion relationship between the condition units covered by different rules, and generate a rule condition coverage relationship table.

3. The steel structure specification conflict feasible domain reconstruction method according to claim 2, characterized in that, Methods for obtaining a set of rules for a sub-scene include: When multiple rule records cover non-intersecting condition units and their combined value equals the target design scenario space, a sub-design scenario is generated according to the boundary of the condition units. By summarizing the rule records that cover the same sub-design scenario, we obtain the sub-scenario rule set.

4. The steel structure specification conflict feasible domain reconstruction method according to claim 2, characterized in that, Methods for determining common applicable conditions include: When a rule record covers one or more condition units, the range of values ​​in the applicable condition field of that rule record that intersect with the corresponding condition unit or the corresponding sub-design scenario are determined as common applicable conditions. When at least two rule records cover the same condition unit, the applicable condition fields corresponding to the same condition unit are intersected to obtain the common applicable conditions.

5. The steel structure specification conflict feasible domain reconstruction method according to claim 2, characterized in that, Methods for generating rule condition coverage relationship tables also include: Convert the applicable condition fields into a condition expression tree; Update the rule condition coverage table based on the inclusion, intersection, and mutual exclusion relationships between different condition expression trees.

6. The method for reconstructing the feasible domain of steel structure code conflicts according to claim 1, characterized in that, Methods for normalizing variables in formulaic rules within a sub-scene rule set also include: When any variable name in a formulaic rule is not mapped to a unified variable, a variable scope branch corresponding to any variable name is generated in the unified variable space; Write the formula-type rules, variable sources, value units, cross-sectional locations, force combinations, and calculation stages into the variable scope branch, and construct the feasible region based on the variable scope branch.

7. The steel structure specification conflict feasible domain reconstruction method according to claim 1, characterized in that, Methods for constructing the feasible domain of each sub-design scenario include: Calculate the single-parameter feasible region based on rule records where the constraint parameter field references only one formula variable field; The generated single-parameter feasible region and the generated multidimensional coupled feasible region are merged to obtain the feasible region. The ungenerated single-parameter feasible region or the ungenerated multidimensional coupled feasible region does not participate in the spatial domain determination of the feasible region. The generated single-parameter feasible domain and the generated multi-dimensional coupled feasible domain are merged, including: intersecting the range of values ​​of the same unified variable, and writing the range of values ​​of different unified variables into the feasible domain of the same sub-design scenario.

8. The method for reconstructing the feasible domain of steel structure code conflict according to claim 7, characterized in that, Methods for calculating the multidimensional coupling feasible region include: A variable coupling relationship graph is generated by using the constraint parameter fields and formula variable fields in the variable coupling rule group as nodes and the reference relationships between the constraint parameter fields and formula variable fields in the rule record as edges. Group interconnected nodes in the variable coupling graph into the same coupled variable group; Within the set of coupled variables, the range of values ​​that simultaneously satisfy the rule records in the set of coupled variables is determined, thus obtaining the multidimensional coupled feasible region.

9. The steel structure specification conflict feasible domain reconstruction method according to claim 7, characterized in that, Methods for calculating the multidimensional coupling feasible region include: When at least two rule records have cross-references on at least two formula variable fields, the corresponding rule records are aggregated into a set of coupled rules; Find the range of values ​​for the rule records in the set of coupling rules that simultaneously satisfy the condition, and obtain the multidimensional coupling feasible region.

10. The steel structure specification conflict feasible domain reconstruction method according to claim 7, characterized in that, Methods for writing feasible regions into the set of consistency constraints include: When the feasible region is not empty, the sub-design scenario, common applicable conditions, single-parameter feasible regions calculated and participating in the formation of the feasible region, multi-dimensional coupled feasible regions calculated and participating in the formation of the feasible region, and corresponding rule records are written into the consistency constraint set.

11. The method for reconstructing the feasible domain of steel structure code conflict according to claim 7, characterized in that, Methods for generating rollback order include: When the feasible domain is empty, read the upstream design variable mapping field from the rule record that participated in forming the empty feasible domain, and generate candidate upstream design variables; Change the value range of each candidate upstream design variable and recalculate the feasible region; The difference between the range of values ​​of the candidate upstream design variable after the change and the range of values ​​before the change is defined as the variable change amount; Sort the variables by the amount of change when the feasible region changes from empty to non-empty, from smallest to largest, and generate a rollback order.

12. The method for reconstructing the feasible domain of steel structure code conflicts according to claim 11, characterized in that, Methods for generating rollback order also include: Combine at least two candidate upstream design variables into candidate variable combinations; Change the value range of the candidate upstream design variable in the candidate variable combination and recalculate the single-parameter feasible region or the multi-dimensional coupled feasible region respectively; The candidate variable combinations that can transform the feasible region from empty to non-empty are sorted in ascending order of the number of candidate upstream design variables, and the sorting results are written into the fallback order.

Images