Processing method of simulation model and electronic device

Abstract

The application provides a simulation model processing method and an electronic device, which can be applied to the technical field of simulation engineering. The method comprises the following steps: matching component constraint information of a plurality of component models with model constraint information of a device model to obtain a matching result; in the case where the matching result indicates that there is a repeated constraint identifier, updating the model constraint information to obtain first constraint information; generating an action object corresponding to an update constraint type in the device model based on the update constraint type and update object information, wherein the action object represents a geometric data object associated with a simulation constraint condition defined by the update constraint type; constructing a constraint definition in the device model by using object information of the action object, the update constraint identifier and the update constraint type, to obtain a mapping from the component constraint information of the component model to the constraint information of the device model, so as to execute simulation processing by using the device model containing the constraint definition after the mapping is completed.

Description

Technical Field

[0001] This application relates to the field of simulation engineering technology, specifically to a method for processing simulation models and an electronic device. Background Technology

[0002] In the simulation process of design and manufacturing, pre-built sub-models need to be repeatedly assembled into different overall models for use, or the overall model needs to be split into multiple sub-models for use. Regarding the transfer mapping between sub-model constraints and overall model constraints, the relevant techniques mainly involve resetting the constraints of the sub-models in the overall model or deleting redundant constraints in the sub-models. However, this approach struggles to simultaneously set the pre-defined assembly conditions for the parts, resulting in repetitive work, wasted effort and time, and low simulation modeling efficiency. Summary of the Invention

[0003] In view of the above problems, this application provides a method for processing simulation models and an electronic device.

[0004] According to a first aspect of this application, a method for processing a simulation model is provided, comprising: matching component constraint information of multiple component models with model constraint information of a device model to obtain a matching result; updating the model constraint information to obtain first constraint information when the matching result indicates the presence of duplicate constraint identifiers; wherein the first constraint information includes an updated constraint identifier, an updated constraint type, and updated object information determined by the updated constraint type; the updated constraint type includes at least one of binding constraint, coupling constraint, and rigid body constraint; and the component models and the device model have an assembly relationship; generating an action object corresponding to the updated constraint type in the device model based on the updated constraint type and the updated object information; wherein the action object represents a geometric data object associated with the simulation constraint conditions defined by the updated constraint type; and constructing constraint definitions in the device model using the object information of the action object, the updated constraint identifier, and the updated constraint type to obtain a mapping from the component constraint information of the component models to the constraint information of the device model, so as to perform simulation processing using the device model containing the constraint definitions after the mapping is completed.

[0005] A second aspect of this application provides a simulation model processing apparatus, comprising: an update module, configured to match component constraint information of multiple component models with model constraint information of a device model to obtain a matching result; and, if the matching result indicates the presence of duplicate constraint identifiers, to update the model constraint information to obtain first constraint information, wherein the first constraint information includes an update constraint identifier, an update constraint type, and update object information determined by the update constraint type, the update constraint type including at least one of binding constraint, coupling constraint, and rigid body constraint, and the component models and the device model having an assembly relationship; a first construction module, configured to generate an action object corresponding to the update constraint type in the device model based on the update constraint type and the update object information, wherein the action object represents a geometric data object associated with the simulation constraint conditions defined by the update constraint type; and a second construction module, configured to construct constraint definitions in the device model using the object information of the action object, the update constraint identifier, and the update constraint type, to obtain a mapping from the component constraint information of the component models to the constraint information of the device model, so as to perform simulation processing using the device model containing the constraint definitions after the mapping.

[0006] A third aspect of this application provides an electronic device comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0007] A fourth aspect of this application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0008] The fifth aspect of this application also provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method.

[0009] According to the embodiments of this application, by automatically matching with the first constraint information, a unique constraint identifier and action object information usable in the device model are generated. Based on the updated constraint type and updated object information, the action object is intelligently constructed, and the constraint information of the component model is automatically converted into specific geometric data objects in the device model. The constraint definition is constructed and the mapping is completed, realizing a complete and one-click migration from component model constraints to device model constraints. This avoids the repetitive work caused by model reconstruction or model deletion and modification of constraints, realizes efficient collaboration and reuse of simulation models, and further improves the automation level of the entire simulation process. Attached Figure Description

[0010] The above-mentioned contents, other objects, features and advantages of this application will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0011] Figure 1 The diagram illustrates an application scenario of the processing method for the simulation model according to an embodiment of this application.

[0012] Figure 2 A flowchart illustrating a method for processing a simulation model according to an embodiment of this application is shown schematically.

[0013] Figure 3A This illustration schematically shows an example of a process for mapping parts of a component model to a device model according to an embodiment of this application;

[0014] Figure 3B This illustration schematically shows an example of a process for establishing binding constraints by coupling multiple slave nodes to an element surface according to an embodiment of this application;

[0015] Figure 3C This illustration shows an example diagram of a reverse query operation from a node to an element face according to an embodiment of this application;

[0016] Figure 4 This illustration schematically shows an example of a process for mapping constraints of parts from a component model to a device model according to an embodiment of this application;

[0017] Figure 5A This schematically illustrates an example diagram of the process for determining the coupling surface in coupling constraints according to an embodiment of this application;

[0018] Figure 5B This illustration schematically shows an example diagram of the process of reconstructing coupling constraints in a device model according to an embodiment of this application;

[0019] Figure 6A This illustration schematically shows an example diagram of the process for determining the master face and slave face in a binding constraint according to an embodiment of this application;

[0020] Figure 6B This illustration schematically shows an example diagram of the process of reconstructing binding constraints in a device model according to an embodiment of this application;

[0021] Figure 7 This schematic diagram illustrates a structural block diagram of a processing apparatus for a simulation model according to an embodiment of the present application;

[0022] Figure 8 A block diagram schematically illustrates an electronic device suitable for implementing a processing method for a simulation model according to an embodiment of this application. Detailed Implementation

[0023] The embodiments of this application will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of this application. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of this application for ease of explanation. However, it will be apparent that one or more embodiments may be implemented without these specific details. Furthermore, descriptions of well-known structures and technologies are omitted in the following description to avoid unnecessarily obscuring the concepts of this application.

[0024] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of this application. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0025] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0026] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0027] In simulation engineering for design and manufacturing, established sub-models (i.e., component models) need to be repeatedly assembled and used, or the overall model (i.e., equipment model) needs to be re-split into sub-models for use. Traditional simulation engineering software can only copy parts to other models, making it difficult to set the pre-defined assembly conditions (constraints) of the parts. It is necessary to repeatedly reset the constraints of the sub-models in the assembled overall model, or delete redundant constraints in the sub-models. This not only involves repetitive work in constraint setting, but also makes it difficult to achieve collaborative work between simulation projects of different products.

[0028] In one example, after the overall model is set up, when a specific sub-model within the overall model needs to be used, it is mainly done by deleting parts and constraints unrelated to the specific sub-model. Alternatively, a sequential modeling approach can be used: first, the constraints of the easily created first sub-model are set up in the overall model; then, the overall model with the first sub-model's constraints are used subsequently. During this process, if a second sub-model needs to be imported into the overall model with the first sub-model's constraints, the first sub-model's constraints need to be deleted before the second sub-model's constraints are set up. Taking a laptop product as an example, first, the constraints of the first component model (e.g., the screen model) are set up; then, the second component model (e.g., the processor model) is assembled into the overall model (device model) and its relevant constraints are set up; finally, the parts and constraints of the first component model are deleted, leaving only the parts and constraints of the second component model.

[0029] However, the traditional approach involves setting up the equipment model and then splitting it according to the actual model's mapping requirements. When there are shared or mixed assembly of component models, it is necessary to reset the constraints between the component models and the equipment models, resulting in repetitive work, low efficiency of collaborative operations, and low information sharing rate between component models.

[0030] To address this technical problem, embodiments of this application provide a method for processing simulation models and an electronic device. The method includes: matching component constraint information of multiple component models with model constraint information of a device model to obtain a matching result; updating the model constraint information to obtain first constraint information when the matching result indicates the presence of duplicate constraint identifiers; wherein the first constraint information includes an updated constraint identifier, an updated constraint type, and updated object information determined by the updated constraint type; the updated constraint type includes at least one of binding constraints, coupling constraints, and rigid body constraints; and the component models and device models have an assembly relationship. Based on the updated constraint type and updated object information, generating an action object corresponding to the updated constraint type in the device model; wherein the action object represents a geometric data object associated with the simulation constraint conditions defined by the updated constraint type; and constructing constraint definitions in the device model using the object information of the action object, the updated constraint identifier, and the updated constraint type to obtain a mapping from the component constraint information of the component models to the constraint information of the device model, so as to perform simulation processing using the mapped device model containing constraint definitions.

[0031] According to the embodiments of this application, by automatically matching with the first constraint information, a unique constraint identifier and action object information usable in the device model are generated. Based on the updated constraint type and updated object information, the action object is intelligently constructed, and the constraint information of the component model is automatically converted into geometric data objects in the device model. The constraint definition is constructed and the mapping is completed, realizing a complete and one-click migration from component model constraints to device model constraints. This avoids the repetitive work caused by model reconstruction or model deletion and modification of constraints, realizes efficient collaboration and reuse of simulation models, and further improves the automation level of the entire simulation process. Figure 1 The diagram illustrates an application scenario of the processing method for the simulation model according to an embodiment of this application.

[0032] like Figure 1 As shown, application scenario 100 according to this embodiment may include terminal device 101, network 102, and server 103. Network 102 is used as a medium to provide a communication link between terminal device 101 and server 103. Network 102 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0033] Users can use terminal device 101 to interact with server 103 via network 102 to receive or send messages, etc. Terminal device 101 can be various electronic devices with a display screen and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers, etc.

[0034] Terminal device 101 can be used to view component models and initiate model integration requests to the system. Terminal device 101 can also store component model files. For example, the collaborative platform client on terminal device 101 packages and uploads the component model file and its contained component constraint information (initial constraint identifier, constraint category, and description of the target object) via network 102, and sends a "constraint mapping and model integration" request to server 103.

[0035] Server 103 can be a processor installed in an electronic device that provides various services, such as a high-performance computing server or cloud server that deploys the core logic of the "simulation model constraint information processing method" and provides collaborative simulation platform services, stores the device model, and executes automatic mapping algorithms.

[0036] For example, after receiving a "constraint mapping and model integration" request, server 103 loads the model constraint information of the device model stored locally (i.e., a list of names of all existing constraints). Server 103 runs the algorithm and performs the relevant information processing.

[0037] It should be noted that the simulation model processing method provided in this application embodiment can generally be executed by server 103. Correspondingly, the simulation model processing device provided in this application embodiment can generally be located in server 103. The simulation model processing method provided in this application embodiment can also be executed by a server or server cluster that is different from server 103 and capable of communicating with terminal device 101 and / or server 103. Correspondingly, the simulation model processing device provided in this application embodiment can also be located in a server or server cluster that is different from server 103 and capable of communicating with terminal device 101 and / or server 103.

[0038] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0039] Figure 2 A flowchart illustrating a method for processing a simulation model according to an embodiment of this application is shown.

[0040] like Figure 2 As shown, the simulation model processing method of this embodiment includes operations S210 to S230.

[0041] In operation S210, the component constraint information of multiple component models is matched with the model constraint information of the device model to obtain a matching result. If the matching result indicates the existence of duplicate constraint identifiers, the model constraint information is updated to obtain the first constraint information. The first constraint information includes an updated constraint identifier, an updated constraint type, and updated object information determined by the updated constraint type. The updated constraint type includes at least one of binding constraints, coupling constraints, and rigid body constraints. The component models and the device model have an assembly relationship.

[0042] In the embodiments of this application, the device model can be a complete digital model of a smart device, also referred to as a device model. Smart devices include, but are not limited to, laptops, tablets, mobile phones, and vehicle terminals. The component model can refer to the component models that constitute the device model, which are pre-established independently and have constraint information set. In the finite element simulation model, constraints can be part assembly conditions, a set of simulation parameters used to define the connection relationships, fixing relationships, or load transfer relationships between different parts (components). Component constraint information can be a set of constraint data stored in the component model, used to describe the connection and interaction relationships between its internal components or with other components. Model constraint information can be a set of information on all existing constraints in the device model, used as a matching reference library to avoid introducing duplicate constraint information. Constraint types include, but are not limited to, binding constraints, coupling constraints, and rigid body constraints.

[0043] To avoid duplication between constraint identifiers in the component model and existing constraint identifiers in the device model, the component constraint information and model constraint information are matched. This ensures the uniqueness of constraint identifiers during the automated migration from the component model to the device model, preventing conflicts or overwriting caused by identifier conflicts.

[0044] The matching result can be obtained by comparing the constraint identifiers in the component constraint information with the existing constraint identifiers in the model constraint information one by one. This includes whether the constraint identifiers in the component constraint information are duplicates / matched with the existing constraint identifiers in the model constraint information, and whether the constraint identifiers in the component constraint information are not duplicates / matched with the existing constraint identifiers in the model constraint information. The first constraint information can be the constraint information after expanding or modifying the model constraint information. The updated constraint identifier can be a unique constraint identifier in the device model determined after matching processing. The updated constraint type can refer to the physical category of the constraint. The updated object information can be specific data associated with the updated constraint type, describing the target of the constraint action.

[0045] For example, the device model is the complete model of an A-series laptop, and the component model can be the screen model or processor model of the A-series laptop. For example, binding constraints can be constraints that include a set of master face nodes and a set of slave face nodes; coupling constraints can be constraints that include the coordinates of the reference point and a set of coupled face nodes; rigid body constraints can be constraints that include the coordinates of the reference point and a set of element identifiers defining the rigid body.

[0046] For example, tie constraints and coupling constraints have different settings and functions in simulation models. The main purpose of tie constraints is to join two or more parts, and they can be used for things like gluing, hot-melting, or welding between parts; the purpose of coupling constraints is to simplify screw settings. Rigid body constraints can be used as substitutes for tools in product or equipment simulations.

[0047] In operation S220, based on the update constraint type and update object information, an action object corresponding to the update constraint type is generated in the device model. The action object represents the geometric data object associated with the simulation constraint conditions defined by the update constraint type.

[0048] In the embodiments of this application, "construction" can refer to the active process of creating new geometric data objects that can be recognized and calculated by simulation engineering software in the database and geometric topology of the device model. The object of action can be a specific geometric data object newly created in the device model according to the updated constraint type and updated object information. The geometric data object can be a basic graphical unit that can be recognized in the simulation engineering software and participate in simulation calculations, such as nodes, element edges, element faces, reference points, etc.

[0049] For example, the target is an element surface constructed from a set of nodes, a newly created reference point after coordinate transformation, or a set of rigid body elements that has been identified.

[0050] For example, after identifying the update constraint type as a binding constraint, the process of converting nodes into element surfaces is executed. In the mesh database of the device model, a reverse query operation from node to element surface is performed on each node in the node set (containing the identifiers or names of multiple nodes) to obtain the list of candidate element surfaces to which each node belongs. Then, the results of all reverse query operations are counted to obtain the target.

[0051] In operation S230, by using the object information of the target object, updating the constraint identifier and updating the constraint type, constraint definitions are constructed in the device model, and a mapping is obtained from the component constraint information of the component model to the constraint information of the device model, so as to perform simulation processing using the device model containing the constraint definitions that has completed the mapping.

[0052] In the embodiments of this application, object information can be a specific attribute identifier of the object (geometric data object) constructed from the device model. For example, a unique number of an element surface, or the coordinate value of a reference point and its identifier in the model database. Constructing constraint definitions can be a formal creation of a complete constraint object or information set that can be recognized, calculated, and have physical effects applied by the simulation engineering software solver in the device model database and simulation preprocessing environment. It is a simulation rule object containing complete attributes such as type, identifier, and object association.

[0053] Mapping can refer to the final realization and verification of the complete conversion, reconstruction, and creation process from component constraint information in the component model to constraint information in the device model. Simulation processing can refer to the standard simulation workflow of applying loads and boundary conditions based on the above complete device model and submitting it to the solver of simulation engineering software for mechanical, thermal, and other physical field calculation and analysis.

[0054] For example, after obtaining the object information of the target object, including the main face element identifier and the slave face element identifier, the update constraint identifier, and the update constraint type as a binding constraint, the creation binding constraint interface of the simulation engineering software can be called. The main face element identifier and the slave face element identifier are passed into the interface to successfully create a binding constraint rule object, i.e., a constraint definition, in the database of the device model.

[0055] In one feasible embodiment, any component model in the smart device can be used as the initial device model in the constraint information processing process, so as to process the constraint information based on the initial device model.

[0056] Figure 3AThe illustration shows an example schematic diagram of a process for mapping parts of a component model to a device model according to an embodiment of this application.

[0057] like Figure 3A As shown, taking the T-series laptop as an example, the component model of the T-series laptop can include a first screen component model 30-T1, a second screen component model 30-T2, and a processor component model 30-S1. The first screen component model 30-T1 and the second screen component model 30-T2 together correspond to the processor component model 30-S1. The processor component model 30-S1 can be used as the initial device model in the constraint information processing process. All parts in the second screen component model 30-T2 are first mapped to the initial device model to obtain the mapped device model 30A for subsequent constraint information processing.

[0058] The constraint category table of the first screen component model can contain multiple constraints. Each constraint category table records the constraint identifier and its corresponding constraint category. The component model and the device model have their own constraint category tables. Therefore, the constraint identifiers of the component model should not be duplicated in the device model. The constraint identifiers of the component model that are duplicated in the device model can be renamed in the device model. Conversely, the constraint identifiers of the original component model can be retained.

[0059] The objects affected by the constraints are recorded according to different constraint categories. Binding constraints affect the master surface and slave surface, recording all nodes on both surfaces. Coupling constraints affect the reference point and coupling surface, recording the position of the reference point and all nodes on the coupling surface. Rigid body constraints affect the reference point and all elements of the part, recording the coordinates of the reference point and elements defined as rigid bodies. It should be noted that in binding constraints, the master surface and slave surface can be distinguished based on the description information of the master surface and the slave surface.

[0060] After determining the constraint identifiers and the information of the objects affected by the constraints, the system can switch from the component model to the device model. Based on the constraint type, the constraint identifiers and the information of the objects affected by the constraints are re-established in the device model. This includes: when updating the constraint type to a bound constraint or a coupled constraint, nodes on the master and slave faces in a bound constraint, or nodes on the coupling face in a coupled constraint, are converted into element faces, and the element face cluster is reconstructed in the device model using these element faces. When updating the constraint type to a coupled constraint or a rigid body constraint, the reference point is reconstructed in the device model based on the coordinates of the reference point of the coupled constraint or the rigid body constraint. When updating the constraint type to a rigid body constraint, all elements of the part are copied to the device model, and the elements are directly set as rigid body constraint elements in the device model.

[0061] For constraints on each component model, you can first switch to the device model, rebuild the constraints in the device model, then switch back to the component model and record the constraint identifier and the object information of the constraint according to the constraint category, until the constraints of all component models are completed.

[0062] According to the embodiments of this application, by automatically matching with the first constraint information, a unique constraint identifier and action object information usable in the device model are generated. Based on the updated constraint type and updated object information, the action object is intelligently constructed, and the constraint information of the component model is automatically converted into specific geometric data objects in the device model. The constraint definition is constructed and the mapping is completed, realizing a complete and one-click migration from component model constraints to device model constraints. This avoids the repetitive work caused by model reconstruction or model deletion and modification of constraints, realizes efficient collaboration and reuse of simulation models, and further improves the automation level of the entire simulation process.

[0063] As is understood, the above text has already explained in detail how to process the constraint information of the simulation model from the overall technical solution. The following text will explain how to construct the object of action.

[0064] According to an embodiment of this application, based on the update constraint type and update object information, generating an action object corresponding to the update constraint type in the device model includes: when the update constraint type is a bound constraint or a coupled constraint, converting the node set in the update object information into an element surface in the device model as a component of the action object.

[0065] In embodiments of this application, a node set can refer to the set of identifiers (e.g., IDs) of all nodes constituting the surface (master surface, slave surface, or coupling surface) of the device model. Converting to an element surface can refer to executing an intelligent conversion algorithm to identify and map the node set into a complete, high-level geometric surface that uniquely defines the node set within the mesh topology of the device model. An element surface can be a basic geometric unit representing the model surface in simulation engineering software, and can be composed of multiple nodes connected topologically (e.g., triangles, quadrilaterals), serving as a standard carrier for applying constraints and loads in engineering software.

[0066] The components of the object of action can refer to the element surfaces obtained through transformation, which will become the direct targets of the constraints reconstructed in the device model. For binding constraints, the primary and secondary element surfaces together constitute the object of action; for coupling constraints, the coupling element surfaces are part of the object of action.

[0067] For example, after determining that the update constraint type is a coupling constraint and the node set is the six node identifiers corresponding to the coupling surface, in the device model, the node reverse query element surface operation is performed on each of the six nodes one by one. Based on all query results, the number of occurrences of each element surface is counted. It is found that element surface No. 1 appears a total of 6 times in all query results. Since the number of nodes 6 is equal to the number of occurrences of element surface No. 1 6, it is determined that the node set is converted into element surface No. 1. Then, element surface No. 1 is used as a component of the coupling constraint object to obtain the coupling surface element surface.

[0068] In finite element software, nodes are the most basic building blocks. Converting nodes into element surfaces can minimize the computational resource requirements of simulation engineering software, thereby shortening the time it takes to upload simulation information to the server. In addition, the parts of the component model in the simulation model are mainly meshed using second-order tetrahedral elements. Second-order tetrahedral elements will generate nodes at the midpoints of the element edges of first-order tetrahedral elements. Therefore, the accuracy of stress results of second-order tetrahedral elements is higher than that of first-order tetrahedral elements.

[0069] In finite element software, adjusting the node coordinates of a second-order tetrahedral element requires reducing its order to first-order tetrahedral before adjustment to prevent element deformation and its impact on accuracy. After reduction, a single element surface changes from six nodes to three. If the coupling surfaces in a coupling constraint are composed of nodes, modifying the nodes and then upgrading the first-order tetrahedral element to a second-order tetrahedral results in the loss of some node information, affecting the simulation model's calculations. Therefore, embodiments of this application reconstruct the element surface clusters of coupling surfaces, master surfaces, or slave surfaces in the device model using element surfaces to prevent the loss or omission of some node information.

[0070] Figure 3B The illustration shows an example of a process for establishing binding constraints by coupling multiple slave nodes to an element surface according to an embodiment of this application.

[0071] like Figure 3B As shown, for the multi-node connection scenario of hot melt assembly, the element surface 31b on the hot melt cylinder of the laptop C component is used as the main surface of the binding constraint, and the multiple nodes 32b of the circular holes on the sheet metal element are used as the set of slave nodes of the binding constraint; the multiple slave nodes are coupled to the element surface (main surface), thereby constructing the action object 33b corresponding to the binding constraint in the simulation.

[0072] It is understandable that by combining the master element surface and the slave node set, and combining the geometric reconstruction algorithm, accurate physical simulation can be achieved while overcoming the data compatibility and robustness problems when the simulation model is reused at different design stages and different mesh accuracies.

[0073] In finite element software, points, lines, and surfaces are represented by nodes, element edges, and element surfaces, respectively. Nodes in an element necessarily form element surfaces, and element surfaces then form the element. There are no isolated nodes in finite element software, so no fault tolerance is required.

[0074] In related technologies, constraints are directly associated with a set of node identifiers. When the model undergoes mesh optimization, refinement, simplification, or order adjustment (e.g., from second-order to first-order), there is a risk that the node identifiers and their number may fundamentally change, causing the constraints based on the original node identifiers to completely fail and requiring a complete overhaul. The embodiments of this application convert the node set into element surfaces, associating constraints with higher-level, more stable topological entities (element surfaces). As long as the geometric features and topological relationships of the model remain unchanged, the element surfaces always exist regardless of how the surface mesh is divided. This allows the mapping results to withstand local mesh changes in the model, enhancing the reusability and lifecycle of simulation data assets, achieving long-term validity with a single mapping.

[0075] According to an embodiment of this application, the node set in the updated object information is converted into an element surface in the device model, including: performing a reverse query operation from node to element surface in the device model based on the identifier of each node to obtain at least one candidate element surface containing each node; and determining the candidate element surface that appears the most frequently during the reverse query process as the element surface.

[0076] In the embodiments of this application, the identifier of each node can refer to the unique identification code of each node in the node set, and can be used as the query key value for the reverse query operation to locate the node in the database of the device model. The reverse query operation from node to element surface can be a data retrieval operation in the model database of computer-aided software, taking the identifier of a certain node as input, searching in reverse and returning a list of identifiers of all element surfaces in the device model that contain that node. The candidate element surface can be the element surface that contains the currently queried node after performing the reverse query operation. The element surface can be composed of multiple nodes, and is a candidate element surface whose occurrence frequency is equal to the total number of nodes in the node set.

[0077] The algorithm for converting nodes to element faces can be used to transform nodes on master faces, slave faces, or coupled faces bound by constraints. Taking a hexahedron as an example, the algorithm flow for converting nodes to element faces is as follows: Figure 3C As shown.

[0078] Figure 3C This illustration shows an example diagram of a reverse query operation from a node to an element face according to an embodiment of this application.

[0079] like Figure 3CAs shown, the four nodes can include node 31, node 32, node 33, and node 34. In the process of converting four nodes into one element face, we can first look up the element faces belonging to node 31 in reverse order to obtain node 310, node 320, and node 330. Then, we look up node 32 in reverse order to obtain node 310, node 320, node 340, and node 350. Next, we look up node 33 in reverse order to obtain node 320, node 330, and node 360. Finally, we look up node 34 in reverse order to obtain node 320, node 360, node 370, and node 380. From the above query results, we can determine that node 320 appears four times, indicating that node 31, node 32, node 33, and node 34 can be converted into node 320. Therefore, a hexahedral element can be converted from four nodes into one element face.

[0080] It is understandable that the algorithm for converting elements of a second-order tetrahedron is the same as that for a hexahedron, the only difference being that it converts six nodes into one element face. The process of converting six nodes into one element face can include: each of the six nodes can be used to look up its corresponding element face; finally, it can be determined that a certain element face (e.g., the first element face) appears six times, indicating that these six nodes can be converted into the first element face. Therefore, a second-order tetrahedron element can be converted from six nodes into one element face. The specific conversion process will not be elaborated here.

[0081] In traditional techniques, simulation engineers need to manually select all the nodes that make up a certain face from among the numerous nodes and faces of the device model, relying on their memory and understanding of the original component model drawings. This is prone to omissions and errors, and it is difficult to verify whether the selected nodes can form a reasonable element face. Even if scripts are used, simply comparing the node list with the face's node list can lead to matching failures or mismatches due to inconsistent node order or duplicate nodes in the model mesh (such as on shared edges).

[0082] The embodiments of this application automatically obtain all possible element faces to which each node belongs through a reverse query operation, and then uniquely and automatically identify the correct target element face by using an algorithm that counts the occurrences and compares them with the total number of nodes, eliminating the uncertainty and error rate of manual selection; moreover, the query process does not require the order of nodes, but only uses the core criterion of "common inclusion". The condition for a face to be "determined" (occurrence count = total number of nodes) is both sufficient and necessary, which makes the judgment criteria clear and unambiguous, and ensures the mathematical and geometric rationality of the transformation result.

[0083] According to an embodiment of this application, based on the update constraint type and update object information, an action object corresponding to the update constraint type is generated in the device model, including: when the update constraint type is a coupled constraint or a rigid body constraint, determining the updated coordinates of the reference point in the device model coordinate system based on the reference point position in the update object information and the geometric transformation information when the parts of the component model are assembled into the device model; and generating a reference geometric object of the reference point defined by the updated coordinates in the device model as a component of the action object.

[0084] In the embodiments of this application, the reference point position can refer to the three-dimensional spatial coordinate values ​​of the reference point in the local coordinate system of the component model, which are included in the updated object information. Geometric transformation information can be parameters describing the spatial pose changes experienced when a part in the component model is assembled into the device model, such as rotation matrices and translation vectors. The device model coordinate system can refer to the global coordinate system used by the device model, under which all parts and constraints must be unified during simulation analysis.

[0085] Updated coordinates can refer to the new 3D spatial coordinate values ​​of the reference point in the device model coordinate system, calculated through inverse transformation. The reference geometric object can be a newly created point-like geometric data object in the device model at the spatial location defined by the updated coordinates.

[0086] For example, when establishing reference points in coupled constraints or rigid body constraints, it is necessary to confirm whether the part has undergone rotation and translation before establishing the reference points. Given the coordinates (x0, y0, z0) of the reference point before rotation and translation, at the rotation center (x... R ,y R ,z R ) along the unit vector (u x ,u y ,u z The rotation angle θ, after rotation and translation, the coordinates of the reference point are (x1, y1, z1). The rotation and translation relationship of the part coordinate system can be represented by the following transformation matrices and vectors, as shown in the following formula (1):

[0087] (1);

[0088] in, It can be used as the coordinates of the reference point after rotation and translation. , It can be used as a reference point coordinate for the part before rotation and translation. T can be the center of rotation. .

[0089] The rotation matrix R can be obtained through unit vectors. The rotation angle θ is determined as shown in the following formula (2):

[0090] (2);

[0091] In related technologies, when manually creating reference points in a device model, it is difficult to directly know the precise location in the original component model. Only measurement, estimation, or approximate alignment can be used, leading to errors that can cause load transfer path offsets in coupled constraints or errors in the moment center of rigid body constraints, directly affecting the accuracy of simulation results. The embodiments of this application, through inverse transformation calculations based on geometric transformation information, can mathematically derive the theoretically precise location (updated coordinates) of the reference point in the device model coordinate system. This ensures that the reconstructed constraint's point of action in physical space remains consistent with the original design intent, eliminating spatial errors caused by manual placement and guaranteeing the geometric fidelity of the simulation model.

[0092] According to an embodiment of this application, based on the reference point position in the updated object information and the geometric transformation information when the parts of the component model are assembled into the device model, the updated coordinates of the reference point in the device model coordinate system are determined, including: using the product of the difference between the reference point position and the translation vector in the geometric transformation information and the transformation matrix of the rotation matrix in the geometric transformation parameters as the updated coordinates.

[0093] In the embodiments of this application, the coordinates of the reference point before rotation and translation are... The calculation method allows the rotation matrix R to be transformed into an inverse matrix. As shown in the following formula (3):

[0094] (3);

[0095] Center of rotation Unit vector (u) x ,u y ,u z ), rotation angle θ, and reference point coordinates Substituting these values ​​will give you the coordinates of the reference point before rotation and translation. .

[0096] According to an embodiment of this application, based on the update constraint type and update object information, an action object corresponding to the update constraint type is generated in the device model, including: when the update constraint type is a rigid body constraint, identifying a set of rigid body elements from the parts of the component model that match the set of element identifiers in the update object information, and using them as components of the action object.

[0097] In the embodiments of this application, a part in the component model can refer to a specific part in the component model that is defined by the element identifier set and needs to be processed as a rigid body. The element identifier set can be a set of finite element identifiers stored in the update object information. The rigid body element set can be a set obtained by traversing and comparing all elements copied from the component model in the device model, identifying the elements whose identifiers are completely consistent with the element identifier set, and summarizing these elements.

[0098] It can be understood that the set of rigid body elements obtained through the identification operation is established as the direct target (geometric carrier) of the rigid body constraint definition to be created in the device model. This set, together with the reference points reconstructed through coordinate transformation, constitutes the complete rigid body constraint object. Elements in the part have been copied into the device model, where they are directly set as rigid body constraint elements.

[0099] After obtaining the set of element identifiers and the coordinates of the reference point in the updated object information, the corresponding set of rigid body elements can be directly identified on the target part of the component model based on the set of element identifiers. Then, the set of rigid body elements is combined with the reference point to serve as the object of the completed construction.

[0100] In related technologies, when redefining rigid body constraints in a device model, it is necessary to define the rigid body range by individually or by selecting hundreds or thousands of elements on a complex assembly. This process is time-consuming and prone to omissions, over-selection, or incorrect selection, leading to discrepancies between the rigid body definition and the design intent, thus affecting simulation accuracy. The embodiments of this application, through precise identification and matching based on unique element identifiers, can automatically and accurately locate and aggregate the set of elements in the device model that are identical to those defined in the component model, thereby avoiding information loss and error propagation during the mapping process.

[0101] According to an embodiment of this application, when the matching result indicates the presence of duplicate constraint identifiers, updating the model constraint information to obtain first constraint information includes: when the component constraint identifier in the component constraint information is duplicated with the model constraint identifier in the model constraint information, updating the component constraint identifier to obtain an updated constraint identifier in the first constraint information, so as to distinguish it from the model constraint identifier; when the component constraint identifier and the model constraint identifier are not duplicated, using the component constraint identifier as the updated constraint identifier in the first constraint information.

[0102] In embodiments of this application, a component constraint identifier can refer to the name defined for each constraint in the component model, such as the constraint identifier of the component model. A model constraint identifier can refer to the names of existing constraints in the device model. Updating a component constraint identifier can refer to modifying the original component constraint identifier when the component constraint identifier matches (is duplicated) the model constraint identifier, such as adding a specific prefix according to preset rules. An updated constraint identifier can be a constraint identifier that will be used in the device model, determined based on the matching results.

[0103] For example, during the matching process between component constraint information and model constraint information, it is found that one of the constraint identifiers of the screen model (LCD) is "Bond_Corner_A", which is the same as one of the constraint identifiers of the device model, "Bond_Corner_A". Then, according to the update strategy of model constraint information (such as adding a prefix), the first constraint information "LCD_Bond_Corner_A" is generated.

[0104] For example, during the matching process between component constraint identifiers and model constraint identifiers, if a constraint in the component model is named "Couple_Screen_Bracket", comparing this component constraint identifier with the list of model constraint identifiers in the device model will not find any identifier with the same name, resulting in a "mismatch". Since the name is unique, no modification is needed. Therefore, the component constraint identifier "Couple_Screen_Bracket" can be directly used as the updated constraint identifier in the first constraint information.

[0105] It is understandable that updating component constraint identifiers (such as adding the "LCD_" prefix) is a pre-defined, uniform rule, which makes the identifiers of all constraints from the same type of component model have predictable patterns and clear source identifiers in the device model, improving the management efficiency and readability of large simulation model data, and making the model easier to understand, maintain and reuse.

[0106] According to embodiments of this application, the above method further includes: when the update constraint type is a binding constraint, the update object information determined by the update constraint type includes a set of master nodes for defining the master face and a set of slave nodes for defining the slave face, wherein the master face and the slave face are model surfaces that need to establish a connection relationship with each other in the binding constraint; when the update constraint type is a coupling constraint or a rigid body constraint, the update object information includes the reference point position indicating the reference point in the local coordinate system of the component model and a set of elements for defining the coupling surface or the rigid body.

[0107] In embodiments of this application, the set of master nodes can be a set of unique identifiers for all finite element nodes constituting the master face in the binding constraint. The set of slave nodes can be a set of identifiers for all finite element nodes constituting the slave face in the binding constraint. The master face and slave face can be two model surfaces defined in the binding constraint that need to establish a connection relationship with each other.

[0108] After identifying whether the current constraint type is bound, coupled, or rigid body, the corresponding geometric data can be extracted from the component model according to the type. The geometric data may include a set of nodes or coordinates, and a set of element identifiers. Then, this data is packaged into a structured reconstruction instruction manual (i.e., update object information) for subsequent use.

[0109] For example, when updating a constraint of type "bound constraint", the main face of the bound constraint is queried from the component model, and the identifiers of all nodes on its surface are extracted to form a set of main nodes, such as {N101,N102,N103,N104,N105,N106}; the secondary face of the bound constraint is queried, and the IDs of all nodes on its surface are extracted to form a set of secondary nodes, such as {N201,N202,N203,N204}; then these data are encapsulated to obtain the update object information of the constraint: {Type: Bound constraint, Main node set: {N101,...N106}, Secondary node set: {N201,...N204}}.

[0110] For example, when updating a constraint of type coupling, the reference point of the coupling constraint is queried from the component model to obtain its position in the local coordinate system of the component model, such as (120.5, 30.2, 5.8); the coupling surface of the coupling constraint is queried, and the identifiers of all elements constituting the surface are extracted to form an element set, such as {Elem_45, Elem_46, Elem_47, Elem_48}; then these data are encapsulated to obtain the update object information of the constraint: {Type: Coupling constraint, Reference point position: (120.5, 30.2, 5.8), Element set: {Elem_45, ..., Elem_48}}.

[0111] In traditional techniques, the geometric information of constraints (nodes, coordinates, elements) is scattered throughout various parts of the model or exists only in graphical operations, failing to form a complete, self-describing data package, making it difficult to automatically understand and process. The embodiments of this application, by updating the constraint type, structurally encapsulate all the geometric information required for different types of constraints within the updated object information, providing accurate and unambiguous input for subsequent intelligent geometric reconstruction algorithms.

[0112] According to embodiments of this application, a constraint definition is constructed in a device model using the object information of the object being acted upon, the update constraint identifier, and the update constraint type. This includes: when the update constraint type is a bound constraint, generating a bound constraint definition in the device model based on the master node set, the slave node set, and the bound constraint identifier in the update constraint identifier; and when the update constraint type is a coupled constraint or a rigid body constraint, generating a coupled constraint definition or a rigid constraint definition in the constraint definition in the device model based on the updated coordinates of the reference point, the element set, and the coupled constraint identifier or rigid body constraint identifier in the update constraint identifier.

[0113] In the embodiments of this application, the constraint definition can be a complete constraint object formally created in the simulation preprocessing environment of the device model, which can be recognized, calculated and have physical effects applied by the simulation engineering software solver. It includes a simulation rule object with complete attributes such as type (binding, coupling and rigid body), identifier, and association with the target object.

[0114] For example, after determining that the update constraint type is a binding constraint, the object information of the affected object includes the constructed master face element identifier (Face_201) and slave face element identifier (Face_198), and the binding constraint identifier is "LCD_Bond_Corner_A", the creation binding constraint interface of the simulation engineering software can be called according to the update constraint type (binding). The binding constraint identifier "LCD_Bond_Corner_A" is passed as the constraint identifier parameter; Face_201 is designated as the master face parameter, and Face_198 is designated as the slave face parameter. These are passed to the interface, and then the interface is used to generate a binding constraint rule object in the device model, that is, a binding constraint definition, which defines the mechanical relationship of the fixed connection between Face_201 and Face_198 in the simulation.

[0115] In related technologies, even after manually selecting all geometric objects, it is still necessary to manually find the "Create Constraints" menu on the simulation engineering software interface, fill in the name, select the type, and associate the geometric objects. Each step involves manual interaction, resulting in low efficiency and a high error rate. The embodiments of this application generate constraint definitions by calling the software interface, replacing the manual graphical interface operation of creating constraints. This makes the entire extraction-processing-reconstruction-creation process an end-to-end, fully automated closed loop without human intervention. Users only need to make a request to automatically deliver a device model containing all correct constraints that can be simulated immediately, achieving one-click direct mapping.

[0116] In one feasible embodiment, taking laptop computer assembly as an example, the laptop computer is divided into two main parts: a screen assembly and a processor assembly. In the embodiments of this application, the relevant constraint settings for the screen assembly model and the processor assembly model can be completed separately first. Then, the screen assembly model and the processor assembly model can be assembled into a device model, which can be done by assembling the screen assembly model into the processor assembly model.

[0117] Figure 4 The illustration shows an example schematic diagram of the process of mapping and constraining parts of a component model to a device model according to an embodiment of this application.

[0118] like Figure 4 As shown, firstly, the processor model 41 in the component model is copied as the initial device model 42, and then the parts of the screen model 43 in the component model are copied to the initial device model 42. At this time, the initial device model 42 will contain the part information of the processor model 41 with complete constraint information set and the mapped screen model 43'.

[0119] The purpose of confirming the number of constraints in the screen model is to determine the number of mapping jobs (the number of loops after programming) and to proceed with the constraint mapping process. A query reveals that the screen model contains 25 constraint settings; the first 6 constraints are coupling constraints, and the latter 19 are bound constraints.

[0120] For the first constraint among the 25 constraints, since constraints with the same identifier cannot exist within the same device model, and component models are set up by different engineers, there may be duplicate names or identifiers. Therefore, it is necessary to confirm whether this constraint identifier is duplicated with the constraint identifier in the device model. If there is no duplicate, the constraint identifier in the component model can be directly used in the device model; if there is a duplicate, the component constraint identifier must be modified, for example, by adding "LCD_" to distinguish it. After updating the constraint identifier, the constraint category can be determined.

[0121] Figure 5A The illustration shows an example schematic diagram of the process for determining the coupling surface in the coupling constraint according to an embodiment of the present application.

[0122] like Figure 5A As shown, the first constraint is a coupling constraint. The location of coupling constraint 501 is the rivet that fixes the hinge bracket to the hinge axis. A reference point 502 is established. The coordinates of reference point 502 are obtained by querying, and the reference point is reconstructed in the device model using the coupling constraint algorithm.

[0123] By querying the coupling surface number of the coupling constraint in the component model, and then querying the coupling surface number to obtain the number of nodes contained in the coupling surface, the coupling surface can be considered as the original elements of the coupling surface. Further querying the node information can obtain the node coordinates and the part to which they belong, denoted as coordinates Coordinates={(x,y,z)|screen model coupling surface node}, finally obtaining coupling surface 503.

[0124] Figure 5B The illustration shows an example schematic diagram of the process of reconstructing coupling constraints in a device model according to an embodiment of the present application.

[0125] like Figure 5B As shown, after the reference point has been reconstructed and the relevant node information and coordinates of the coupling surface 503 in the screen model have been obtained, since the parts of the screen model in the device model are the same as the parts of the original screen model, when mapping the coupling surface to the device model, the relevant node information and coordinates of the parts can be directly imported into the device model as the coupling surface and associated with the reference point to obtain the coupling constraint result 50B. The above mapping process is repeated until the mapping of the first six coupling constraints is completed.

[0126] Figure 6A The illustration shows an example diagram of the process for determining the master face and slave face in the binding constraint according to an embodiment of this application.

[0127] When the seventh constraint is a bound constraint, the first step is to determine whether the constraint identifier of the bound constraint is duplicated. The process is the same as the identifier deduplication process for the coupled constraint described above, and will not be repeated here. Figure 6A As shown, the binding constraint position 611 is the fitting position between the corners of the laptop A component and the corner of the laptop A component.

[0128] Establish the master face 612 and slave face 613 in the binding constraint. In the binding constraint, the master face 612 and slave face 613 are set on the first part 614 and the second part 615, respectively. The construction method of the master face 612 and slave face 613 is the same as or similar to the construction method of the coupling surface, and will not be described in detail here.

[0129] By querying the number of the main face of the screen model, we can obtain the node coordinates and the parts to which the main face belongs, and denoted as Coordinates = { (x, y, z) | Main face node of screen model}; by querying the number of the secondary face of the screen model, we can obtain the node coordinates and the parts to which the secondary face belongs, and denoted as Coordinates = { (x, y, z) | Secondary face node of screen model}.

[0130] Figure 6BThe illustration shows an example schematic diagram of the process of reconstructing binding constraints in a device model according to an embodiment of the present application.

[0131] like Figure 6B As shown, the binding constraints are reconstructed in the device model. Since the parts of the screen model in the device model are exactly the same as the parts of the original screen model, when mapping the master and slave faces of the binding constraints to the device model, the node information and coordinates of the master and slave faces of the original screen model can be directly mapped to the device model as master and slave faces, respectively, based on the position 611 of the binding constraints, resulting in binding constraint result 60B. The above binding constraint mapping steps are repeated until the mapping of 19 binding constraints is completed.

[0132] Based on the above-described simulation model processing method, this application also provides a simulation model processing apparatus. The following will combine... Figure 7 The device is described in detail.

[0133] Figure 7 A schematic block diagram of a processing apparatus for a simulation model according to an embodiment of this application is shown.

[0134] like Figure 7 As shown, the simulation model processing device 700 of this embodiment includes an update module 710, a first construction module 720, and a second construction module 730.

[0135] The update module 710 is used to match the component constraint information of multiple component models with the model constraint information of the device model to obtain a matching result. If the matching result indicates the existence of duplicate constraint identifiers, the model constraint information is updated to obtain first constraint information. The first constraint information includes an updated constraint identifier, an updated constraint type, and updated object information determined by the updated constraint type. The updated constraint type includes at least one of binding constraints, coupling constraints, and rigid body constraints. The component models and the device model have an assembly relationship. In one embodiment, the update module 710 can be used to perform the operation S210 described above, which will not be repeated here.

[0136] The first construction module 720 is used to generate an action object in the device model corresponding to the updated constraint type based on the updated constraint type and updated object information. The action object represents a geometric data object associated with the simulation constraint conditions defined by the updated constraint type. In one embodiment, the first construction module 720 can be used to execute the operation S220 described above, which will not be repeated here.

[0137] The second construction module 730 is used to construct constraint definitions in the device model using the object information of the target object, update constraint identifiers, and update constraint types, thereby obtaining a mapping from component constraint information of the component model to constraint information of the device model, so as to perform simulation processing using the device model containing the constraint definitions after mapping. In one embodiment, the second construction module 730 can be used to perform the operation S230 described above, which will not be repeated here.

[0138] According to the embodiments of this application, the update module 710, the first construction module 720, and the second construction module 730 in the simulation model-based processing device 700 automatically match and generate unique constraint identifiers and action object information available in the device model by matching with the first constraint information. Thus, based on the updated constraint type and updated object information, the action object is intelligently constructed, and the constraint information of the component model is automatically converted into specific geometric data objects in the device model. The constraint definition is constructed and the mapping is completed, realizing a complete and one-click migration from component model constraints to device model constraints. This avoids the repetitive work caused by model reconstruction or model deletion and modification of constraints, realizes efficient collaboration and reuse of simulation models, and further improves the automation level of the entire simulation process.

[0139] According to an embodiment of this application, the first construction module 720 includes: a conversion submodule, used to convert the set of nodes in the updated object information into element surfaces in the device model when the update constraint type is a binding constraint or a coupling constraint, so as to serve as a component of the object to be applied.

[0140] According to an embodiment of this application, the conversion submodule includes a query unit and a determination unit. The query unit is used to perform a reverse query operation from node to element surface in the device model based on the identifier of each node, to obtain at least one candidate element surface containing each node; the determination unit is used to determine the candidate element surface that appears the most frequently during the reverse query process as the element surface.

[0141] According to an embodiment of this application, the first construction module 720 includes a coordinate determination submodule and a generation submodule. The coordinate determination submodule is used to determine the updated coordinates of the reference point in the equipment model coordinate system based on the reference point position in the updated object information and the geometric transformation information when the parts of the component model are assembled into the equipment model, when the update constraint type is a coupled constraint or a rigid body constraint. The generation submodule is used to generate a reference geometric object in the equipment model defined by the updated coordinates, as a component of the applied object.

[0142] According to an embodiment of this application, the coordinate determination submodule includes: a determination unit, used to use the product of the difference between the reference point position and the translation vector in the geometric transformation information and the transformation matrix of the rotation matrix in the geometric transformation parameters as the updated coordinates.

[0143] According to an embodiment of this application, the first construction module 720 includes: an identification submodule, used to identify, when the update constraint type is rigid body constraint, a set of rigid body elements that matches the set of element identifiers in the update object information from the parts of the component model, as a component of the object to be applied.

[0144] According to an embodiment of this application, the update module 710 includes an update submodule and a determination submodule. The update submodule is used to update the component constraint identifier to obtain an updated constraint identifier in the first constraint information when the component constraint identifier in the component constraint information is the same as the model constraint identifier in the model constraint information, so as to distinguish it from the model constraint identifier; the determination submodule is used to use the component constraint identifier as the updated constraint identifier in the first constraint information when the component constraint identifier and the model constraint identifier are not the same.

[0145] According to an embodiment of this application, the above-mentioned apparatus further includes: when the update constraint type is a binding constraint, the update object information determined by the update constraint type includes a set of master nodes for defining a master face and a set of slave nodes for defining a slave face, wherein the master face and the slave face are model surfaces that need to establish a connection relationship with each other in the binding constraint; when the update constraint type is a coupling constraint or a rigid body constraint, the update object information includes a reference point position indicating the reference point in the local coordinate system of the component model and a set of elements for defining the coupling surface or the rigid body.

[0146] According to an embodiment of this application, the second construction module 730 includes: a first entity generation submodule and a second entity generation submodule. The first entity generation submodule is used to generate a bound constraint definition in the device model based on the master node set, the slave node set, and the bound constraint identifier in the updated constraint identifier when the update constraint type is a bound constraint. The second entity generation submodule is used to generate a coupled constraint definition or a rigid constraint definition in the constraint definition in the device model based on the updated coordinates of the reference point, the element set, and the coupled constraint identifier or rigid constraint identifier in the updated constraint identifier.

[0147] According to embodiments of this application, any plurality of modules among the update module 710, the first construction module 720, and the second construction module 730 can be merged into one module, or any one of these modules can be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules can be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this application, at least one of the update module 710, the first construction module 720, and the second construction module 730 can be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any appropriate combination of any of these three implementation methods. Alternatively, at least one of the update module 710, the first construction module 720, and the second construction module 730 can be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0148] Figure 8 A block diagram schematically illustrates an electronic device suitable for implementing a processing method for a simulation model according to an embodiment of this application.

[0149] like Figure 8 As shown, an electronic device 800 according to an embodiment of this application includes a processor 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage portion 808 into a random access memory (RAM) 803. The processor 801 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor, and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 801 may also include onboard memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of this application.

[0150] RAM 803 stores various programs and data required for the operation of electronic device 800. Processor 801, ROM 802, and RAM 803 are interconnected via bus 804. Processor 801 executes various operations of the method flow according to embodiments of this application by executing programs in ROM 802 and / or RAM 803. It should be noted that the programs may also be stored in one or more memories other than ROM 802 and RAM 803. Processor 801 may also execute various operations of the method flow according to embodiments of this application by executing programs stored in said one or more memories.

[0151] According to embodiments of this application, the electronic device 800 may further include an input / output (I / O) interface 805, which is also connected to a bus 804. The electronic device 800 may also include one or more of the following components connected to the input / output (I / O) interface 805: an input section 806 including a keyboard, mouse, etc.; an output section 807 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the input / output (I / O) interface 805 as needed. A removable medium 811, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 810 as needed so that computer programs read from it can be installed into the storage section 808 as needed.

[0152] This application also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the method according to the embodiments of this application.

[0153] According to embodiments of this application, the computer-readable storage medium can be a non-volatile computer-readable storage medium, such as including but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this application, the computer-readable storage medium may include ROM 802 and / or RAM 803 and / or one or more memories other than ROM 802 and RAM 803 described above.

[0154] Embodiments of this application also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to enable the computer system to implement the processing method of the simulation model provided in the embodiments of this application.

[0155] When the computer program is executed by the processor 801, it performs the functions defined in the system / apparatus of this application embodiment. According to the embodiments of this application, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0156] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 809, and / or installed from a removable medium 811. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0157] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 809, and / or installed from the removable medium 811. When the computer program is executed by the processor 801, it performs the functions defined in the system of this application embodiment. According to the embodiments of this application, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0158] According to embodiments of this application, program code for executing the computer programs provided in the embodiments of this application can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can be executed entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

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

[0160] Those skilled in the art will understand that the features described in the various embodiments of this application can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this application. In particular, the features described in the various embodiments of this application can be combined and / or combined in various ways without departing from the spirit and teachings of this application. All such combinations and / or combinations fall within the scope of this application.

[0161] The embodiments of this application have been described above. However, these embodiments are merely illustrative and not intended to limit the scope of this application. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. Without departing from the scope of this application, those skilled in the art can make various substitutions and modifications, all of which should fall within the scope of this application.

Claims

1. A method for processing simulation models, characterized in that, The method includes: The component constraint information of multiple component models is matched with the model constraint information of the device model to obtain a matching result. If the matching result indicates that there is a duplicate constraint identifier, the model constraint information is updated to obtain first constraint information. The first constraint information includes an updated constraint identifier, an updated constraint type, and updated object information determined by the updated constraint type. The updated constraint type includes at least one of binding constraint, coupling constraint, and rigid body constraint. The component model and the device model have an assembly relationship. Based on the update constraint type and the update object information, an action object corresponding to the update constraint type is generated in the device model, wherein the action object represents a geometric data object associated with the simulation constraint conditions defined by the update constraint type; Using the object information of the target object, the update constraint identifier, and the update constraint type, a constraint definition is constructed in the device model to obtain a mapping from the component constraint information of the component model to the constraint information of the device model, so as to perform simulation processing using the device model containing the constraint definition after the mapping is completed.

2. The method according to claim 1, characterized in that, Based on the update constraint type and the update object information, an action object corresponding to the update constraint type is generated in the device model, including: When the update constraint type is a binding constraint or a coupling constraint, the set of nodes in the update object information is converted into element surfaces in the device model and used as components of the applied object.

3. The method according to claim 2, characterized in that, Converting the set of nodes in the updated object information into an element facet in the device model includes: Based on the identifier of each node, a reverse query operation from node to element surface is performed in the device model to obtain at least one candidate element surface containing each node. The candidate element facets that appear an equal number of times during the reverse lookup process to the total number of nodes in the node set are determined as the element facets.

4. The method according to claim 1, characterized in that, Based on the update constraint type and the update object information, an action object corresponding to the update constraint type is generated in the device model, including: When the update constraint type is a coupling constraint or a rigid body constraint, the updated coordinates of the reference point in the equipment model coordinate system are determined based on the reference point position in the update object information and the geometric transformation information when the parts of the component model are assembled into the equipment model. A reference geometry object is generated in the device model using the reference points defined by the updated coordinates, as a component of the object being acted upon.

5. The method according to claim 4, characterized in that, Based on the reference point position in the updated object information and the geometric transformation information when the parts of the component model are assembled into the equipment model, the updated coordinates of the reference point in the equipment model coordinate system are determined, including: The updated coordinates are the product of the difference between the reference point position and the translation vector in the geometric transformation information, and the transformation matrix of the rotation matrix in the geometric transformation parameters.

6. The method according to claim 1, characterized in that, Based on the update constraint type and the update object information, an action object corresponding to the update constraint type is generated in the device model, including: When the update constraint type is rigid body constraint, a set of rigid body elements that match the set of element identifiers in the update object information are identified from the parts of the component model and used as a component of the object being acted upon.

7. The method according to claim 1, characterized in that, If the matching result indicates the presence of a duplicate constraint identifier, the model constraint information is updated to obtain first constraint information, including: If the component constraint identifier in the component constraint information is the same as the model constraint identifier in the model constraint information, the component constraint identifier is updated to obtain the updated constraint identifier in the first constraint information, so as to distinguish it from the model constraint identifier. If the component constraint identifier and the model constraint identifier are not duplicated, the component constraint identifier is used as the update constraint identifier in the first constraint information.

8. The method according to claim 1, characterized in that, The method further includes: When the update constraint type is a binding constraint, the update object information determined by the update constraint type includes a set of master nodes for defining the master face and a set of slave nodes for defining the slave face. The master face and the slave face are model surfaces that need to establish a connection relationship with each other in the binding constraint. When the updated constraint type is a coupling constraint or a rigid body constraint, the updated object information includes the reference point position indicating the reference point in the local coordinate system of the component model and the set of elements used to define the coupling surface or rigid body.

9. The method according to claim 8, characterized in that, Using the object information of the object being acted upon, the update constraint identifier, and the update constraint type, a constraint definition is constructed in the device model, including: When the update constraint type is a binding constraint, a binding constraint definition of the constraint definition is generated in the device model based on the master node set, the slave node set, and the binding constraint identifier in the update constraint identifier; When the update constraint type is a coupled constraint or a rigid body constraint, the coupled constraint definition or rigid constraint definition in the constraint definition is generated in the device model based on the update coordinates of the reference point, the element set, and the coupled constraint identifier or rigid body constraint identifier in the update constraint identifier.

10. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 9.

Images