Modeling element processing method and device, electronic equipment, medium and product

Abstract

The embodiment of the invention provides a modeling element processing method and device, electronic equipment, a medium and a product. The method comprises the following steps: in response to a deletion instruction for a target element, determining at least one first type of element according to a preset dependency graph; wherein the dependency relationship graph comprises a plurality of dependency relationships, and the dependency relationships represent relationships between the dependency modeling elements and the depended modeling elements; the first class of elements are modeling elements associated with the target element; processing the modeling elements in the to-be-deleted element set according to a preset deletion strategy; wherein the to-be-deleted element set comprises a target element and at least one first-class element. The method is used for comprehensively identifying the modeling elements associated with the modeling elements needing to be deleted and automatically processing the modeling elements, and the effect of improving the processing efficiency of the modeling elements is achieved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of dynamics simulation, and in particular, to a modeling element processing method and device, an electronic device, a medium and a product. BACKGROUND

[0002] Dynamics simulation technology is used to construct a simulation model of a complex system in a simulation process. In the process of constructing the simulation model, the simulation model is formed by modeling elements and dependency relationships between the modeling elements. When a user needs to delete a certain modeling element in the simulation model, a cascade deletion requirement of multiple layers of dependency relationships can be involved.

[0003] In some technologies, a simulation modeling software can process elements having a direct connection with a modeling element that needs to be deleted. In the above technology, the simulation modeling software cannot automatically process deep cascade dependency relationships, resulting in the user needing to manually clean up indirectly dependent modeling elements.

[0004] Therefore, there is an urgent need for a solution that can comprehensively identify modeling elements associated with a modeling element that needs to be deleted and automatically process the modeling elements. SUMMARY

[0005] The modeling element processing method and device, the electronic device, the medium and the product provided by the embodiments of the present application comprehensively identify modeling elements associated with a modeling element that needs to be deleted and automatically process the modeling elements, thereby improving the processing efficiency of the modeling elements.

[0006] In a first aspect, the embodiments of the present application provide a modeling element processing method, including:

[0007] In response to a deletion instruction for a target element, at least one first-type element is determined according to a preset dependency relationship graph; the dependency relationship graph includes a plurality of dependency relationships, and the dependency relationships represent relationships between dependent modeling elements and depended modeling elements; the first-type element is a modeling element associated with the target element;

[0008] The modeling elements in a to-be-deleted element set are processed according to a preset deletion strategy; the to-be-deleted element set includes the target element and at least one first-type element.

[0009] In a possible implementation, the at least one first-type element is determined according to the preset dependency relationship graph, including:

[0010] In the dependency relationship graph, a traversal operation is performed along a first direction of the dependency relationship starting from the target element, and at least one directly dependent element is determined; the first direction is that the depended modeling element points to the dependent modeling element; the directly dependent element is a corresponding dependent modeling element when the target element is the depended modeling element;

[0011] In the dependency graph, starting from the direct dependency element, traversing in the first direction of the dependency relationship, at least one indirect dependency element is determined; wherein, the indirect dependency element includes a modeling element having at least one level of dependency relationship with the direct dependency element;

[0012] The direct dependency element and the indirect dependency element are determined as at least one first type element.

[0013] In a possible implementation, according to the preset deletion strategy, the modeling elements in the set of modeling elements to be deleted are processed, including:

[0014] According to the preset deletion strategy, the deletion action corresponding to each modeling element in the set of modeling elements to be deleted is determined;

[0015] Based on the deletion action, each modeling element in the set of modeling elements to be deleted is processed; wherein, the deletion action includes at least one of the following: deleting the modeling element, restoring the attribute value of the modeling element to the preset default value, and no action.

[0016] In a possible implementation, the deletion strategy includes: a first strategy and a second strategy; wherein, the first strategy is the deletion action defined by the system by default for each modeling element, and the second strategy is the deletion action customized by the user for each modeling element;

[0017] According to the preset deletion strategy, the deletion action corresponding to each modeling element in the set of modeling elements to be deleted is determined, including:

[0018] If the priority of the first strategy is greater than or equal to the priority of the second strategy, the deletion action corresponding to each modeling element in the set of modeling elements to be deleted is determined according to the deletion action in the first strategy;

[0019] Otherwise, the deletion action corresponding to each modeling element in the set of modeling elements to be deleted is determined according to the deletion action in the second strategy.

[0020] In a possible implementation, in response to the deletion instruction for the target element, the method further includes:

[0021] According to the preset dependency graph, at least one second type element is determined; wherein, the second type element is the dependent modeling element corresponding to the target element as the dependency modeling element, and the second type element does not exist as the dependency relationship of the dependency modeling element;

[0022] According to the at least one second type element, a display list is generated, and the display list is displayed on the visualization interface; wherein, the display list includes prompt information and each second type element.

[0023] In a possible implementation, the at least one second type of element is determined according to a preset dependency graph, including:

[0024] In the dependency graph, a traversal operation is performed in a second direction of the dependency relationship starting from the target element, to determine at least one candidate element; the second direction is that a dependent modeling element points to a depended modeling element

[0025] In the dependency graph, starting from the candidate element, if it is determined that the traversal is performed in the second direction, the candidate element cannot be found as the dependent modeling element corresponding to the depended modeling element, the candidate element is determined as the second type of element.

[0026] In a possible implementation, the modeling element is a modeling object or an attribute expression; the modeling object is used to construct a simulation model, and the attribute expression is used to represent an attribute relationship between the modeling objects.

[0027] In a second aspect, an embodiment of the present application provides a modeling element processing apparatus, including:

[0028] The first processing module is configured to determine at least one first type of element according to a preset dependency graph in response to a deletion instruction for a target element; the dependency graph includes a plurality of dependency relationships, the dependency relationship represents a relationship between a dependent modeling element and a depended modeling element, and the first type of element is a modeling element associated with the target element.

[0029] The second processing module is configured to process the modeling elements in a to-be-deleted element set according to a preset deletion strategy; the to-be-deleted element set includes the target element and the at least one first type of element.

[0030] In a possible implementation, the at least one first type of element is determined according to a preset dependency graph, and the first processing module is configured to:

[0031] In the dependency graph, a traversal operation is performed in a first direction of the dependency relationship starting from the target element, to determine at least one directly dependent element; the first direction is that a depended modeling element points to a dependent modeling element, and the directly dependent element is a dependent modeling element corresponding to the target element as a depended modeling element.

[0032] In the dependency graph, a traversal operation is performed in the first direction of the dependency relationship starting from the directly dependent element, to determine at least one indirectly dependent element; the indirectly dependent element includes a modeling element having at least one level of dependency relationship with the directly dependent element.

[0033] The directly dependent element and the indirectly dependent element are determined as the at least one first type of element.

[0034] In a possible implementation, the modeling elements in the set of modeling elements to be deleted are processed according to the preset deletion policy, and the second processing module is configured to:

[0035] According to the preset deletion policy, the deletion action corresponding to each modeling element in the set of modeling elements to be deleted is determined.

[0036] Each modeling element in the set of modeling elements to be deleted is processed based on the deletion action, wherein the deletion action includes at least one of the following: deleting the modeling element, restoring the attribute value of the modeling element to a preset default value, and no action.

[0037] In a possible implementation, the deletion policy includes a first policy and a second policy, wherein the first policy is a deletion action defined by default for each modeling element in the system, and the second policy is a deletion action customized by a user for each modeling element.

[0038] According to the preset deletion policy, the deletion action corresponding to each modeling element in the set of modeling elements to be deleted is determined.

[0039] If the priority of the first policy is greater than or equal to the priority of the second policy, the deletion action corresponding to each modeling element in the set of modeling elements to be deleted is determined according to the deletion action in the first policy.

[0040] Otherwise, the deletion action corresponding to each modeling element in the set of modeling elements to be deleted is determined according to the deletion action in the second policy.

[0041] In a possible implementation, in response to the deletion instruction for the target element, the first processing module is further configured to:

[0042] According to the preset dependency graph, at least one second type element is determined, wherein the second type element is a dependent modeling element corresponding to the target element as a dependent modeling element, and the second type element does not exist as a dependent modeling element.

[0043] According to the at least one second type element, a display list is generated, and the display list is displayed on the visual interface, wherein the display list includes prompt information and each second type element.

[0044] In a possible implementation, according to the preset dependency graph, at least one second type element is determined, and the first processing module is configured to:

[0045] In the dependency graph, the target element is taken as a starting point, and a traversal operation is performed in a second direction of the dependency relationship to determine at least one candidate element, wherein the second direction is a direction in which a dependent modeling element points to a dependent modeling element.

[0046] In the dependency graph, starting from the alternative element, if it is determined to traverse in the second direction, the corresponding depended modeling element cannot be found as the dependency modeling element, the alternative element is determined as the second type of element.

[0047] In a possible implementation, the modeling element is a modeling object or an attribute expression; the modeling object is used to construct a simulation model, and the attribute expression is used to represent an attribute relationship between the modeling objects.

[0048] In a third aspect, an embodiment of the present application provides an electronic device, including a memory and a processor.

[0049] The memory stores computer execution instructions.

[0050] The processor executes the computer execution instructions stored in the memory, so that the processor executes the first aspect and / or various possible implementation manners of the first aspect.

[0051] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, the computer readable storage medium stores computer execution instructions, and the computer execution instructions are executed by the processor to implement the first aspect and / or various possible implementation manners of the first aspect.

[0052] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, and the computer program is executed by the processor to implement the first aspect and / or various possible implementation manners of the first aspect.

[0053] The modeling element processing method, device, electronic device, medium and product provided by the embodiment of the present application can first identify the dependency relationship of all levels of modeling elements according to the dependency graph. In response to the deletion instruction of the user, all first type elements associated with the target element intended to be deleted by the user can be determined based on the dependency graph. At this time, the modeling elements that need to be deleted include the target element and all associated first type elements. The elements that need to be deleted are automatically processed respectively according to the preset deletion strategy. The modeling elements associated with the modeling elements that need to be deleted can be comprehensively identified and automatically processed. The processing efficiency of the modeling elements is improved. BRIEF DESCRIPTION OF DRAWINGS

[0054] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present application and, together with the specification, serve to explain the principles of the application.

[0055] Figure 1 The flowchart of the modeling element processing method provided by the embodiment of the present application Figure One ;

[0056] Figure 2An exemplary dependency graph;

[0057] Figure 3 A flowchart of a processing method of a modeling element provided by the present application Figure Two ;

[0058] Figure 4 An exemplary relationship diagram of a first type of element and a target element;

[0059] Figure 5 A flowchart of a processing method of a modeling element provided by the present application Figure Three ;

[0060] Figure 6 A flowchart of a processing method of a modeling element provided by the present application Figure Four ;

[0061] Figure 7 An exemplary relationship diagram of a second type of element and a target element;

[0062] Figure 8 An exemplary data structure diagram;

[0063] Figure 9 A structural diagram of a processing device of a modeling element provided by the present application;

[0064] Figure 10 A structural diagram of an electronic device provided by the present application.

[0065] The specific embodiments of the present application have been shown through the above-described drawings, and will be described in more detail hereinafter. These drawings and written descriptions are not intended to limit the scope of the concept of the present application by any means, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0066] The exemplary embodiments will be described in detail herein below, with examples shown in the drawings. When the following description refers to the drawings, identical numbers on different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of apparatuses and methods consistent with some aspects of the present application as detailed in the appended claims.

[0067] First, the terms involved in the present application are explained:

[0068] Modeling element: refers to the basic components in constructing a simulation model of a complex system. Exemplarily, the modeling elements can include parts, joints, forces, motions, measures, etc.

[0069] Deletion policy: refers to the action that the modeling element can perform in response to the user's deletion operation or deletion instruction.

[0070] Dynamic simulation technology is widely used in different engineering design fields, such as mechanical engineering, vehicle dynamics, robot system, etc. Dynamic simulation technology is used to build simulation models of complex systems in the simulation process.

[0071] In the process of building a simulation model, a simulation model is formed by modeling elements and the dependency relationship between modeling elements. The simulation model containing multiple entities is gradually built by the dependency relationship between modeling elements. These modeling elements form a mesh topology through the dependency relationship. For example, a constraint node may depend on two component nodes, and a measurement node may depend on the combination of constraint nodes and component nodes.

[0072] In a possible application scenario, when the user needs to delete a certain modeling element in the simulation model, the cascade deletion requirement of multiple levels of dependency relationship may be involved.

[0073] In some embodiments, the simulation modeling software can process elements that have a dependency relationship with the modeling element that needs to be deleted. However, in the above embodiment, other modeling elements with deep cascade dependency relationship with the deleted target element cannot be automatically processed, resulting in the need for the user to manually clean up these indirect dependent elements. This leads to low processing efficiency of modeling elements, and there may be problems of accidental deletion or omission.

[0074] The modeling element processing method provided by the embodiments of the present application can first identify the dependency relationship of all levels of modeling elements according to the dependency graph. In response to the user's deletion instruction, all first type elements associated with the target element intended to be deleted by the user can be determined based on the dependency graph. At this time, the modeling elements that need to be deleted include the target element and all associated first type elements. For the preset deletion policy, the elements that need to be deleted are automatically processed respectively. The modeling elements associated with the modeling elements that need to be deleted can be comprehensively identified and automatically processed. The processing efficiency of the modeling elements is improved.

[0075] The technical solutions of the present application and how the technical solutions of the present application solve the above technical problems will be described in detail in the specific embodiments below. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0076] Figure 1 Flowchart of the modeling element processing method provided by the present application Figure OneAs shown in Figure 1 The method comprises the following steps:

[0077] Step 101. In response to a deletion instruction for a target element, determining at least one first type of element according to a preset dependency graph.

[0078] The dependency graph comprises a plurality of dependency relationships, and the dependency relationships represent relationships between a dependent modeling element and a depended modeling element; and the first type of element is a modeling element associated with the target element.

[0079] For example, a user needs to delete a target element in a simulation model, and generates a deletion instruction for the target element. In response to the deletion instruction, a first type of element associated with the target element is determined from a preset dependency graph.

[0080] The dependency graph can be preset or pre-constructed. The dependency graph comprises a plurality of dependency relationships. The dependency relationships represent the reference relationship between different modeling elements in the simulation model. Specifically, the dependency relationships represent the relationship between a dependent modeling element and a depended modeling element.

[0081] Optionally, the dependency relationship has a direction. In the dependency graph, the positive direction of the dependency relationship is from the dependent modeling element to the depended modeling element.

[0082] Figure 2 An example of a dependency graph is shown in Figure 2 An example of a dependency graph of modeling elements of a simulation model is shown in

[0083] In the example, modeling element C depends on modeling element B. Modeling element B depends on modeling element A, modeling element 22, and modeling element 23. Modeling element A depends on modeling element 31, modeling element 32, and modeling element 33. Modeling element 33 depends on modeling element 41.

[0084] As shown by the arrow direction in Figure 2 , the positive direction of the dependency relationship is that the dependent modeling element points to the depended modeling element. For example, modeling element 33 depends on modeling element 41. It can be understood that the dependent modeling element is modeling element 33, and the depended modeling element is modeling element 41.

[0085] Optionally, the dependency graph can be pre-built. The dependency graph is built by constructing a dependency table map of modeling elements - [(dependent element 1, attribute 1), (dependent element 2, attribute 2)... (dependent element n, attribute n)] in memory. In the dependency table map, the key represents the modeling element, and the value represents all the dependency tables of the attribute of a certain modeling element.

[0086] In combination Figure 2 To explain, in response to a deletion instruction for a target element, the target element is first found in the dependency graph, and then the first type of element is determined according to the modeling elements having a dependency relationship with the target element in the dependency graph. Further, the first type of element includes modeling elements having a direct dependency relationship with the target element, and also includes modeling elements having a dependency relationship with the modeling elements having a direct dependency relationship.

[0087] These first type of elements are associated with the target element, and in the process of deleting the target element, these associated modeling elements need to be considered.

[0088] Step 102. According to the preset deletion strategy, the modeling elements in the to-be-deleted element set are processed.

[0089] Among them, the to-be-deleted element set includes the target element and at least one first type of element.

[0090] For example, the first type of element determined above and the target element are taken as the to-be-deleted element set. For each modeling element in the to-be-deleted element set, the modeling element is processed according to the preset deletion strategy.

[0091] Among them, the deletion strategy refers to the processing action that needs to be performed in response to the deletion instruction for the modeling element in the to-be-deleted element set. For example, deleting the modeling element, or restoring the attribute value of the modeling element to the default value, etc. The form of these deletion strategies can be a deletion strategy class Class, which contains multiple matching rules in the form of a map in the deletion strategy class Class. The matching rule is used to determine the corresponding processing action and default value according to the type and attribute of the modeling element.

[0092] For example, when the element type of the modeling element is Assembly and the value of the attribute name Interface is Output, the execution mode is None, and the deletion operation is not performed, that is, the cascading deletion does not continue to spread down from the modeling element node.

[0093] It can be understood that the processing actions to be performed by each deleting element are determined according to the deletion strategy for the modeling elements in the set of modeling elements to be deleted. Each modeling element in the set of modeling elements to be deleted is automatically processed based on the corresponding processing action.

[0094] The modeling element processing method provided by the embodiments of the present application can first identify the dependency relationship of modeling elements of all levels according to the dependency graph. In response to a user deletion instruction, all first-type elements associated with a target element intended to be deleted by the user can be determined based on the dependency graph. At this time, the modeling elements to be deleted include the target element and all associated first-type elements. The elements to be deleted are automatically processed respectively according to the preset deletion strategy. The modeling elements associated with the modeling elements to be deleted can be comprehensively identified and automatically processed, without the need for the user to manually find the modeling elements having an indirect dependency relationship with the elements to be deleted, thereby realizing automatic processing of the modeling elements of the simulation model and achieving the effect of improving the processing efficiency of the modeling elements.

[0095] Figure 3 Flowchart of the modeling element processing method provided by the present application Figure Two As shown in Figure 3 , the embodiments on the basis of Figure 1 the embodiments, the process of how to determine the first-type elements in step 101 is described in detail. The method includes:

[0096] Step 301. In the dependency graph, starting from the target element, traversing operation is performed along the first direction of the dependency relationship to determine at least one direct dependency element.

[0097] The first direction is that the dependent modeling element points to the dependency modeling element; and the direct dependency element is the corresponding dependency modeling element when the target element is the dependent modeling element.

[0098] For example, as can be known from the foregoing embodiments, each dependency relationship in the dependency graph has a direction, which is that, among the two connected modeling elements, the dependency modeling element points to the dependent modeling element.

[0099] For the target element, if the target element is deleted, the modeling elements having a dependency relationship with the target element will be affected. Specifically, the affected modeling elements should be the corresponding dependency modeling elements when the target element is the dependent modeling element.

[0100] Combined with Figure 2 , it is explained that if the modeling element A is taken as the target element, the corresponding dependency modeling element of the target element A as the dependent modeling element is the modeling element B; that is, the direct dependency element is the modeling element B.

[0101] It can be understood that, along the first direction, starting from the target element, all corresponding dependent modeling elements having a dependency relationship with the target element are determined. These corresponding dependent modeling elements having a dependency relationship with the target element are direct dependent elements.

[0102] That is, the direct dependent elements are corresponding dependent modeling elements having one level of dependency relationship with the target element.

[0103] Step 302. In the dependency relationship graph, starting from the direct dependent element, along the first direction of the dependency relationship, at least one indirect dependent element is determined.

[0104] The indirect dependent element includes a modeling element having at least one level of dependency relationship with the direct dependent element.

[0105] For example, for the target element, if the target element is deleted, the direct dependent element will be affected. Further, the modeling element having a dependency relationship with the direct dependent element will also be affected.

[0106] In combination Figure 2 It is explained that, if the modeling element A is taken as the target element, the corresponding dependent modeling element of the target element A as the dependent modeling element is the modeling element B; that is, the direct dependent element is the modeling element B.

[0107] Further, the modeling element B as the dependent modeling element still has one dependency relationship, and the corresponding dependent modeling element is the modeling element C; that is, the indirect dependent element is the modeling element C.

[0108] It can be understood that, along the first direction, starting from the direct dependent element, all corresponding dependent modeling elements having a dependency relationship with the direct dependent element are determined. These corresponding dependent modeling elements having a dependency relationship with the direct dependent element are modeling elements having one level of dependency relationship with the direct dependent element, that is, indirect dependent elements.

[0109] Optionally, if the modeling element having one level of dependency relationship with the direct dependent element still has a next level of dependency relationship, the corresponding dependent modeling element in the next level of dependency relationship is also an indirect dependent element.

[0110] Figure 4 The relationship diagram between the exemplary first type of element and the target element is shown. As shown in FIG. 1, the target element is the modeling element A, and the direct dependent element is the modeling element B. Figure 4As shown, the modeling element A is taken as the target element. Traversing along the reverse direction of the illustrated arrow (the first direction), the direct dependent element, i.e., the modeling element B, is obtained. Traversing along the reverse direction of the illustrated arrow (the first direction) from the direct dependent element, the indirect dependent element, i.e., the modeling element C, is obtained.

[0111] It can be understood that if there is a modeling element D above the modeling element C and the modeling element D depends on the modeling element C, the modeling element D is also an indirect dependent element. Therefore, the termination condition of the traversal of the indirect dependent element is that no other modeling element having a dependency relationship can be found in the dependency graph in the first direction from the modeling element as the starting point.

[0112] For example, all constraint nodes referencing the component node are found from the component node, and all force or measurement nodes referencing the constraints are found from the constraint nodes.

[0113] Step 303. The direct dependent elements and the indirect dependent elements are determined as the at least one first type element.

[0114] For example, all the direct dependent elements and the indirect dependent elements obtained by the traversal are taken as the first type elements. These first type elements are all modeling elements associated with the target element, which are affected and need to be processed according to the preset deletion strategy when the target element is processed in response to the deletion instruction.

[0115] In the above embodiment, by taking the target element as the starting point in the dependency graph in the first direction, the modeling elements having a direct dependency relationship with the target element are first traversed as the direct dependent elements. Then, by taking the direct dependent element as the starting point in the dependency graph in the first direction, the traversal is performed until no dependent element of the next level can be found, and all the traversed modeling elements are taken as the indirect dependent elements. All the direct dependent elements and the indirect dependent elements are determined as the first type elements. Thus, all the first type elements associated with the target element in the dependency graph can be found, and all levels of dependency relationships can be identified. The problem of processing only the modeling elements having a direct dependency relationship with the target element is solved, and all the cascading dependent elements are ensured to be covered by the deletion operation.

[0116] In some possible application scenarios, in the process of performing the deletion operation on the modeling elements in the simulation model, other modeling elements associated with the target element can be excessively deleted.

[0117] For example, a simulation model contains modeling element groups. These groups are used to uniformly activate or disable all modeling elements belonging to a group. When deleting a modeling element from a group, sometimes it's necessary to delete all modeling elements within the group, and sometimes it's just to delete the element itself, leaving the modeling elements within the group unchanged. If this distinction isn't made, it can lead to excessive deletion.

[0118] For another example, a simulation model may contain multiple subsystems, which form a larger system through assembly relationships. Subsystem A and subsystem B are completely isolated, connected only by assembler-type modeling elements. When a modeling element in subsystem A is deleted, due to the connection relationships of the assembler-type modeling elements, the deletion operation will propagate along the cascading relationship to subsystem B, deleting the modeling elements in subsystem B as well.

[0119] In this scenario, it is necessary to formulate deletion strategies for each of the first-category elements associated with the target element. Based on the deletion strategy corresponding to each first-category element, the deletion action corresponding to that strategy is then executed.

[0120] Figure 5 Flowchart of the method for processing modeling elements provided in this application Figure Three ,like Figure 5 As shown, in this embodiment... Figure 1 Based on the embodiments, the process of how to process modeling elements according to the deletion strategy in step 102 is described in detail. The method includes:

[0121] Step 501. Based on the preset deletion strategy, determine the deletion action corresponding to each modeling element in the set of modeling elements to be deleted.

[0122] For example, as can be seen from the foregoing examples, for each modeling element in the set of modeling elements to be deleted, the corresponding processing action is determined according to the deletion strategy.

[0123] Specifically, the deletion strategy can include matching rules for the corresponding modeling elements. Based on each modeling element in the set of modeling elements to be deleted, a matching process is performed according to these rules to obtain the matching results. The deletion action corresponding to each modeling element is then determined based on the matching results.

[0124] For example, for modeling elements of type A, perform automatic deletion; for modeling elements of type B with non-zero attribute values, restore their attribute values ​​to their default values ​​(e.g., the default value is 0); for modeling elements of type B with an attribute value of 0, perform automatic deletion.

[0125] The matching rules and corresponding deletion actions described above are for illustrative purposes only. In practical applications, specific deletion strategies can be specified based on actual processing needs.

[0126] Step 502. Processing each modeling element in the set of modeling elements to be deleted based on the deletion action.

[0127] The deletion action includes at least one of the following: deleting the modeling element, restoring the attribute value of the modeling element to a preset default value, and no action.

[0128] For example, based on the corresponding deletion action determined for each modeling element, the deletion action is performed on the modeling element, thereby realizing automatic processing of the modeling elements in the set of modeling elements to be deleted.

[0129] As can be seen from the foregoing examples, the deletion action can include various types of actions. For example, the modeling element is automatically deleted, or the attribute value of the modeling element is restored to a preset default value. For example, for some special types of modeling elements, direct deletion is not allowed, and the modeling element is not processed, i.e., no action.

[0130] In the foregoing embodiments, for each modeling element in the set of modeling elements to be deleted, a corresponding deletion action is determined according to a deletion strategy, and then the modeling element in the set of modeling elements to be deleted is processed based on the deletion action. This realizes flexible control of the deletion action for different modeling elements, dynamically controls the actual action behavior of the modeling elements by the deletion instruction, avoids excessive deletion or omission of key elements, and improves the flexibility and security of the deletion operation.

[0131] Optionally, on the basis of the foregoing embodiments, the deletion strategy includes a first strategy and a second strategy. The first strategy is a deletion action defined by the system by default for each modeling element, and the second strategy is a deletion action defined by a user for each modeling element.

[0132] For example, the first strategy is a deletion strategy preset by the system by default in a default condition, which is a default system deletion strategy according to business rules and cannot be changed. For example, an exemplary first strategy is: group element deletion, which does not affect the modeling elements in the group element. The first strategy includes a deletion action defined by the system by default for each modeling element.

[0133] For example, the second strategy is a deletion strategy defined by a user. The second strategy includes a deletion action defined by a user for each modeling element.

[0134] Optionally, the second strategy can be automatically attached based on the user when triggering the deletion instruction for the target element.

[0135] Optionally, in combination with the foregoing examples, the form of the deletion strategy can be a deletion strategy class Class. The deletion strategy class Class can further include a system strategy subclass and a user-defined subclass. The subclass contains all the attributes and methods of the parent class, and can also have its own attributes and methods.

[0136] On this basis, the first strategy and the second strategy have priorities. The priority of the first strategy is a priority value set by the system by default, and the priority of the second strategy is a priority value set by the user by default. The priority value represents the priority of the execution of the deletion strategy.

[0137] In determining the deletion action corresponding to the to-be-deleted modeling element, the priorities of the first strategy and the second strategy can be used to select different deletion strategies to determine the deletion action.

[0138] In one example, if the priority of the first strategy is greater than or equal to the priority of the second strategy, the deletion action corresponding to each modeling element in the to-be-deleted modeling element set is determined according to the deletion action in the first strategy.

[0139] For example, the priority value of the first strategy is greater than or equal to the priority value of the second strategy, which means that the priority of the first strategy is greater than or equal to the priority of the second strategy. That is, the first strategy needs to be executed first.

[0140] Further, the deletion action corresponding to each modeling element in the to-be-deleted modeling element set is determined according to the deletion action in the first strategy. It can be understood that in the case of equal priority, the system deletion strategy is preferred to the user-defined deletion strategy.

[0141] In another example, otherwise, the deletion action corresponding to each modeling element in the to-be-deleted modeling element set is determined according to the deletion action in the second strategy.

[0142] For example, the priority value of the first strategy is less than the priority value of the second strategy, which means that the priority of the first strategy is less than the priority of the second strategy. That is, the second strategy needs to be executed first.

[0143] Further, the deletion action corresponding to each modeling element in the to-be-deleted modeling element set is determined according to the deletion action in the second strategy. It can be understood that in this example, the user-defined deletion strategy is used to determine the deletion action corresponding to the modeling element.

[0144] Optionally, one example of the priority value can be 1, 2, or 3. The greater the priority value, the higher the execution priority of the deletion strategy.

[0145] In the above examples, by the deletion strategy preset by the system and the deletion strategy customized by the user, and based on the priority, different deletion strategies are selected to determine the actual deletion action of each modeling element in the set of modeling elements to be deleted, thereby realizing the intelligentization of the deletion operation. Further, the user is supported to customize the deletion action of the modeling element, the flexible deletion strategy is supported, and the individuality degree of the modeling element processing process is improved

[0146] In a possible application scenario, after the user deletes the target element, some modeling elements may not have any dependency relationship with other modeling elements in the simulation model. These modeling elements without any dependency relationship can be referred to as orphan elements. It is usually difficult to detect these orphan elements. However, the existence of these orphan elements may cause redundancy and potential calculation errors of the simulation model.

[0147] Figure 6 Flowchart of the modeling element processing method provided in the present application Figure Four As shown in the foregoing any embodiment, in response to the deletion instruction for the target element, the method further includes: Figure 6

[0148] Step 601. Determine at least one second type element according to the preset dependency relationship graph.

[0149] The second type element is a dependent modeling element corresponding to the target element as a dependency modeling element, and the second type element does not have a dependency relationship as a dependency modeling element.

[0150] For example, in response to the deletion instruction, the target element is first found from the preset dependency relationship graph, and then the second type element is determined from the modeling elements having a dependency relationship with the target element in the dependency relationship graph.

[0151] Further, these second type elements have a dependency relationship with the target element, and the target element is a dependency modeling element and the second type element is a dependent modeling element. Further, these second type elements do not have a dependency relationship as a dependency modeling element. Wherein, not having a dependency relationship as a dependency modeling element means that starting from the second type element, along the second direction in the dependency relationship graph, no other modeling element having a dependency relationship can be found.

[0152] It can be understood that after the target element is deleted, such second type elements will exist alone in the simulation model, and no other modeling element has a dependency relationship with them. Such second type elements will cause redundancy in the simulation model.

[0153] Step 602. Generate a display list according to the at least one second type element, and display the display list on the visual interface.​

[0154] The display list includes prompt information and the second-type elements.

[0155] In an example, the second-type elements determined in step 601 are displayed in sequence. For example, the display list is used for display, and modeling element information of all second-type elements is displayed in the display list. The modeling element information includes, but is not limited to, a name of a modeling element, a type of the modeling element, and an identification (ID) of the modeling element.

[0156] Further, the display list is displayed on a preset visual interface, to prompt the user to view orphan elements in the simulation model after the deletion instruction for the target element is executed.

[0157] The process of further processing by the user can include configuring an operation control for each second-type element in the display list. The operation control is used to process the second-type element corresponding to the operation control in response to a click of the user. The process of processing the second-type element includes determining a deletion action of the second-type element according to a preset deletion strategy, and processing the second-type element based on the deletion action.

[0158] Optionally, the display list further includes prompt information in addition to the second-type elements. The prompt information is used to prompt the user that the second-type elements are orphan elements. An example of the prompt information is: “The following elements are created due to the deleted components, but currently have no direct dependency relationship, and may have no actual effect. Please confirm whether to manually process.”

[0159] In the above embodiment, the orphan elements (second-type elements) after the target element is processed based on the dependency relationship diagram are determined, and a corresponding visual display list is generated, to prompt the user to process the second-type elements. The second-type elements are processed based on the actual intention of the user, to avoid element redundancy of the simulation model due to the inability to identify the second-type elements.

[0160] In the above embodiment, how to determine the second-type elements is specifically explained.

[0161] In an example, at least one second-type element is determined by the following steps:

[0162] In the dependency relationship diagram, a traversal operation is performed along a second direction of the dependency relationship starting from the target element, to determine at least one candidate element.

[0163] In the dependency graph, starting from the alternative element, if it is determined to traverse in the second direction and no alternative element as the dependent modeling element is found, the corresponding dependent modeling element is determined as the second type of element.

[0164] The second direction is the direction in which the dependent modeling element points to the dependent modeling element.

[0165] Figure 7 An example of the relationship between the second type of element and the target element is shown in the figure. As shown in Figure 7 , the modeling element A is taken as the target element. Starting from the target element and traversing in the positive direction of the arrow (the second direction), the alternative element is obtained. It can be understood that Figure 7 the modeling element 31, the modeling element 32 and the modeling element 33 in

[0166] Taking the modeling element 31 in Figure 7 as an example, the modeling element 31 is taken as the dependent modeling element, and the modeling element 31 is taken as the starting point. No corresponding dependent modeling element can be found, so the modeling element 31 is the second type of element.

[0167] Correspondingly, Figure 7 the modeling element 32 in

[0168] Taking the modeling element 33 in Figure 7 as an example, the modeling element 33 is taken as the dependent modeling element, and the modeling element 33 is taken as the starting point. In the second direction, the corresponding dependent modeling element (the modeling element 41 shown in Figure 7 ) can be found, so the modeling element 33 is not the second type of element.

[0169] Optionally, in combination with the foregoing example, it can be known that the form of the deletion strategy can be a deletion strategy class Class. A virtual method can also be declared and defined, which is denoted as an intent verification method class. The virtual method is used for judging and processing the second type of element of the modeling element. For example, the intent verification method class derives specific implementation methods InterfaceServiceImpl1 and InterfaceServiceImpl2. The InterfaceServiceImpl1 is used to analyze whether the modeling element is an orphan element; and the InterfaceServiceImpl2 is used to analyze whether the modeling element is metadata and is not recommended to be deleted.

[0170] In the foregoing example, based on the dependency graph, the orphan element (the second type of element) that may exist in the simulation model after the target element is processed can be identified. It is ensured that there is no invalid data residual in the simulation model after the deletion operation, thereby reducing the redundancy of the simulation model and avoiding calculation errors.

[0171] In any of the foregoing embodiments, the modeling elements in the foregoing embodiments can include entity objects for constructing the simulation model, or can include attribute relationships between the entity objects.

[0172] In an example, the modeling elements are modeling objects or attribute expressions. The modeling objects are used to construct the simulation model, and the attribute expressions are used to represent attribute relationships between the modeling objects.

[0173] In an example, the modeling elements can include modeling objects for constructing the simulation model, and attribute expressions for representing attribute relationships between the modeling objects.

[0174] The modeling elements are basic units of the simulation model. The attribute expression Expression in the modeling elements is a special modeling element that is responsible for computing and managing the dependency relationships.

[0175] In a possible implementation, the successor modeling elements and the precursor modeling elements have dependency relationships. It can be understood that the successor modeling elements are dependent modeling elements, and the precursor modeling elements are dependent modeling elements.

[0176] Figure 8 An example of a data structure diagram is shown in FIG. 1. As shown in FIG. 1, the attribute expression Expression is a special modeling element that is responsible for computing and managing the dependency relationships. The “Successor Properties” is a template class entity that manages the properties of the successor objects. Figure 8 Successor Object: The other modeling element object or attribute expression Expression referenced by the modeling element object. The Successor Object can be an entity object of a modeling element of any Type. The “Precursor Properties” is a template class entity that manages the properties of the base data types.

[0177] Precursor Object: The other modeling element object or attribute expression Expression that references the modeling element object itself. The Precursor Object can be an entity object of a modeling element of any Type.

[0178] The modeling elements described above can be modeling objects of any type, or can be attribute expressions representing attribute relationships between the modeling objects. For example, an example attribute expression is to determine the dependent modeling element from a plurality of dependent modeling elements in a certain manner.

[0179]

[0180] ​In the above examples, the processing of diversified kinds of modeling elements ensures comprehensive identification of the modeling elements in the simulation model, ensuring the comprehensiveness and accuracy of the processing of the modeling elements.

[0181] The modeling element processing method provided by the embodiment of the application can first identify the dependency relationship of the modeling elements of all levels according to the dependency graph. In response to a deletion instruction of a user, all first-type elements associated with a target element intended to be deleted by the user can be determined based on the dependency graph. At this time, the modeling elements that need to be deleted include the target element and all the associated first-type elements. The elements that need to be deleted are automatically processed respectively according to a preset deletion strategy. The modeling elements associated with the modeling elements that need to be deleted can be comprehensively identified and automatically processed, without the need for the user to manually find the modeling elements that have an indirect dependency relationship with the elements that need to be deleted, thereby realizing the automatic processing of the modeling elements of the simulation model and achieving the effect of improving the processing efficiency of the modeling elements.

[0182] All the direct dependency elements and the indirect dependency elements are determined as the first-type elements. In this way, all the first-type elements associated with the target element can be found in the dependency graph, and the dependency relationship of all levels can be identified. The problem of processing only the modeling elements that have a direct dependency relationship with the target element is solved, and the deletion operation covers all the cascading dependency elements.

[0183] The system preset deletion strategy and the user-defined deletion strategy are selected to determine the actual deletion actions of the modeling elements in the set of modeling elements to be deleted according to the priority, thereby realizing the intelligentization of the deletion operation. The deletion actions are flexibly controlled, the actual action behavior of the modeling elements by the deletion instruction is dynamically controlled, over-deletion or omission of key elements is avoided, and the flexibility and safety of the deletion operation are improved.

[0184] The orphan elements (second-type elements) that may exist in the simulation model after the target element is processed can be identified based on the dependency graph, and the second-type elements can be processed according to the actual intention of the user. It is ensured that there is no invalid data left in the simulation model after the deletion operation, thereby reducing the redundancy of the simulation model and avoiding calculation errors.

[0185] Figure 9 The structure diagram of the modeling element processing device provided by the application is shown in FIG. 9. Figure 9 As shown in FIG. 9, the modeling element processing device 90 provided by the embodiment of the application includes:

[0186] The first processing module 901 is configured to, in response to a deletion instruction for a target element, determine at least one first-type element according to a preset dependency graph; the dependency graph comprises a plurality of dependency relationships, and the dependency relationships represent relationships between dependent modeling elements and depended modeling elements; and the first-type element is a modeling element associated with the target element.

[0187] The second processing module 902 is configured to process the modeling elements in the to-be-deleted element set according to a preset deletion strategy; the to-be-deleted element set comprises the target element and the at least one first-type element.

[0188] In a possible implementation, the at least one first-type element is determined according to the preset dependency graph, and the first processing module 901 is configured to:

[0189] In the dependency graph, a traversal operation is performed in a first direction of the dependency relationship starting from the target element, to determine at least one directly dependent element; the first direction is that the depended modeling element points to the dependent modeling element; and the directly dependent element is a corresponding dependent modeling element when the target element is a depended modeling element.

[0190] In the dependency graph, a traversal operation is performed in the first direction of the dependency relationship starting from the directly dependent element, to determine at least one indirectly dependent element; the indirectly dependent element comprises a modeling element having at least one level of dependency relationship with the directly dependent element.

[0191] The directly dependent element and the indirectly dependent element are determined as the at least one first-type element.

[0192] In a possible implementation, the modeling elements in the to-be-deleted element set are processed according to the preset deletion strategy, and the second processing module 902 is configured to:

[0193] According to the preset deletion strategy, a deletion action corresponding to each modeling element in the to-be-deleted element set is determined.

[0194] Each modeling element in the to-be-deleted element set is processed based on the deletion action; the deletion action comprises at least one of the following: deleting the modeling element, restoring a property value of the modeling element to a preset default value, and no action.

[0195] In a possible implementation, the deletion strategy comprises a first strategy and a second strategy; the first strategy is a deletion action defined by default for each modeling element in a system, and the second strategy is a deletion action customized by a user for each modeling element.

[0196] According to the preset deletion strategy, a deletion action corresponding to each modeling element in the to-be-deleted element set is determined, and the second processing module 902 is configured to:

[0197] If the priority of the first strategy is greater than or equal to the priority of the second strategy, the deletion action corresponding to each modeling element in the set of modeling elements to be deleted is determined according to the deletion action in the first strategy;

[0198] Otherwise, the deletion action corresponding to each modeling element in the set of modeling elements to be deleted is determined according to the deletion action in the second strategy.

[0199] In a possible implementation, in response to the deletion instruction for the target element, the first processing module 901 is further configured to:

[0200] determine at least one second type element according to the preset dependency relationship graph; the second type element is a dependent modeling element corresponding to the target element as a dependency modeling element, and the second type element does not exist as a dependency relationship of a dependency modeling element;

[0201] generate a display list according to the at least one second type element, and display the display list on the visual interface; the display list includes prompt information and each second type element.

[0202] In a possible implementation, the first processing module 901 is configured to determine at least one second type element according to the preset dependency relationship graph.

[0203] In the dependency relationship graph, the at least one candidate element is determined by starting from the target element and performing a traversal operation in a second direction of the dependency relationship; the second direction is a direction in which a dependency modeling element points to a dependent modeling element.

[0204] In the dependency relationship graph, the candidate element is determined as the second type element if it is determined that the candidate element cannot be found as a dependency modeling element corresponding to a dependent modeling element when the traversal operation in the second direction is performed.

[0205] In a possible implementation, the modeling element is a modeling object or an attribute expression; the modeling object is used to construct a simulation model, and the attribute expression is used to represent an attribute relationship between modeling objects.

[0206] The modeling element processing apparatus provided in this embodiment can execute the method provided in the method embodiment, and has similar implementation principles and technical effects, which will not be described here in detail.

[0207] Figure 10 The structural schematic diagram of the electronic device provided in this embodiment is shown in FIG. 1. Figure 10As shown, the electronic device 100 provided by the embodiment includes at least one processor 1001 and a memory 1002. Optionally, the electronic device 100 further includes a communication component 1003. The processor 1001, the memory 1002 and the communication component 1003 are connected through a bus 1004.

[0208] In the implementation process, the at least one processor 1001 executes the computer execution instructions stored in the memory 1002, so that the at least one processor 1001 executes the above-mentioned method.

[0209] The specific implementation process of the processor 1001 can refer to the method embodiments described above, which have similar implementation principles and technical effects, and will not be described here in detail.

[0210] In the above embodiments, it should be understood that the processor can be a central processing unit (English: Central Processing Unit, for short: CPU), and can also be other general-purpose processors, digital signal processors (English: Digital Signal Processor, for short: DSP), application specific integrated circuits (English: Application Specific Integrated Circuit, for short: ASIC) and the like. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor and the like. The steps of the method disclosed in combination with the application can be directly embodied as execution completed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

[0211] The memory can contain a random access memory (Random Access Memory, RAM), and can also include a non-volatile memory (Non-volatile Memory, NVM), for example, at least one disk memory.

[0212] The bus can be an industry standard architecture (Industry Standard Architecture, ISA) bus, a peripheral component interconnect (Peripheral Component, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, the bus in the drawings of the present application does not limit only one bus or one type of bus.

[0213] The present application also provides a computer program product, comprising a computer program which is executed by a processor to implement the above-mentioned method.

[0214] The application further provides a computer readable storage medium, and the computer readable storage medium stores computer execution instructions.

[0215] The readable storage medium can be implemented by any type of volatile or nonvolatile storage devices or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0216] An exemplary readable storage medium is coupled to the processor, so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be an integral part of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in the device.

[0217] The division of units is only a logical function division, and in actual implementation, there can be another division mode, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0218] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or they can be distributed on multiple network units. According to actual needs, some or all of the units can be selected to achieve the purpose of the embodiment.

[0219] In addition, the functional units in each embodiment of the application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit.

[0220] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the parts of the technical solutions that essentially contribute to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the embodiments of the method of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0221] It can be understood by those skilled in the art that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction related hardware. The aforementioned program can be stored in a computer readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk, and various media that can store program codes.

[0222] Finally, it should be noted that: those skilled in the art will easily think of other embodiments of the present application after considering the specification and practicing the application disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application that follow the general principles of the present application and include common knowledge or conventional technical means in the art that are not disclosed in the present application, and is not limited to the precise structure described above and shown in the drawings, and various modifications and changes can be made without departing from the scope thereof. The scope of the present application is only limited by the appended claims.

Claims

1. A method for processing modeling elements, characterized in that, include: In response to a deletion instruction for a target element, at least one first-type element is determined based on a preset dependency graph; wherein, the dependency graph includes multiple dependencies, which represent the relationship between dependent modeling elements and dependent modeling elements; the first-type element is a modeling element associated with the target element; According to a preset deletion strategy, the modeling elements in the set of elements to be deleted are processed; wherein, the set of elements to be deleted includes the target element and the at least one first-class element.

2. The method according to claim 1, characterized in that, Based on the pre-defined dependency graph, at least one element of type 1 is identified, including: In the dependency graph, starting from the target element, a traversal operation is performed along the first direction of the dependency relationship to determine at least one direct dependent element; wherein, the first direction is from the dependent modeling element to the dependent modeling element; the direct dependent element is the dependent modeling element corresponding to the target element when the target element is the dependent modeling element. In the dependency graph, starting from the direct dependent element, traversing along the first direction of the dependency relationship, at least one indirect dependent element is determined; wherein, the indirect dependent element includes modeling elements that have at least one level of dependency relationship with the direct dependent element. The directly dependent element and the indirectly dependent element are identified as at least one first-class element.

3. The method according to claim 1, characterized in that, According to the preset deletion strategy, the modeling elements in the set of modeling elements to be deleted are processed, including: Based on the preset deletion strategy, determine the deletion action corresponding to each modeling element in the set of modeling elements to be deleted; The deletion action is used to process each modeling element in the set of modeling elements to be deleted; wherein the deletion action includes at least one of the following: deleting the modeling element, restoring the attribute value of the modeling element to a preset default value, or no action.

4. The method according to claim 3, characterized in that, The deletion strategy includes: a first strategy and a second strategy; wherein, the first strategy is the deletion action defined by each modeling element under the system default, and the second strategy is the deletion action defined by the user for each modeling element. According to a preset deletion strategy, the deletion action corresponding to each modeling element in the set of modeling elements to be deleted is determined, including: If the priority of the first strategy is greater than or equal to the priority of the second strategy, then the deletion action corresponding to each modeling element in the set of modeling elements to be deleted is determined according to the deletion action in the first strategy. Otherwise, based on the deletion action in the second strategy, determine the deletion action corresponding to each modeling element in the set of modeling elements to be deleted.

5. The method according to any one of claims 1-4, characterized in that, In response to a deletion instruction targeting a element, the method further includes: Based on a preset dependency graph, at least one second type of element is determined; wherein, the second type of element is the dependent modeling element corresponding to the target element when it is used as a dependency modeling element, and the second type of element does not have any dependency relationship as a dependency modeling element; A display list is generated based on at least one second-type element, and the display list is displayed on a visual interface; wherein, the display list includes prompt information and each of the second-type elements.

6. The method according to claim 5, characterized in that, Based on the pre-defined dependency graph, at least one element of the second type is identified, including: In the dependency graph, starting from the target element, a traversal operation is performed along the second direction of the dependency relationship to determine at least one candidate element; wherein, the second direction is from the dependency modeling element to the dependent modeling element. In the dependency graph, if, starting from the candidate element, it is determined that traversing along the second direction will not find the candidate element as a dependency modeling element, then the corresponding dependent modeling element will be determined as the second type of element.

7. The method according to any one of claims 1-4, characterized in that, The modeling element is a modeling object or an attribute expression; wherein, the modeling object is used to construct a simulation model, and the attribute expression is used to characterize the attribute relationships between the modeling objects.

8. A processing device for modeling elements, characterized in that, include: The first processing module is configured to, in response to a deletion instruction for a target element, determine at least one first-type element based on a preset dependency graph; wherein the dependency graph includes multiple dependencies, and the dependency relationships characterize the relationship between dependent modeling elements and dependent modeling elements; the first-type element is a modeling element associated with the target element. The second processing module is used to process the modeling elements in the set of elements to be deleted according to a preset deletion strategy; wherein the set of elements to be deleted includes the target element and the at least one first-class element.

9. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-7.

11. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-7.

Images