A method for implementing EDA data parameterized modeling

Abstract

The present invention provides a method for implementing parametric modeling of EDA data. The method includes: constructing three mapping tables when performing attribute parameterization operations on single or batch commands; performing parameterized processing on single or batch commands; and modifying parameter values ​​to affect all entities parameterized by the parameters. This method enables batch modification of model data, grouped parameter control, and supports redo / undo functions.

Description

Technical Field

[0001] The present invention relates to the technical field of EDA model layout simulation, and in particular to a method for implementing EDA data parameterized modeling. Background Art

[0002] The parametric modeling function of EDA model data uses one or more attributes of a command within the model, such as offset or height, as parameters, and the dimensions and position of the entity as driven elements. By processing and calculating the parameters and related attributes through internal program logic, the driven elements are driven to change, thereby generating a model that meets the requirements. This process of establishing the association between parameters and driven elements is called parameterization.

[0003] EDA model data is parameterized and grouped, so that when a parameter is modified once, the entire group of data is modified simultaneously. This eliminates the need for users to locate and modify each parameter individually on the 3D interface. This efficiency benefit is particularly noticeable when the model data volume is large, making model updates and modifications more flexible and convenient, accelerating product launches. Summary of the Invention

[0004] In view of the above problems, the present invention is proposed to provide a method for implementing EDA data parameterized modeling that overcomes the above problems or at least partially solves the above problems.

[0005] According to one aspect of the present invention, a method for implementing EDA data parameterized modeling is provided, the method comprising:

[0006] When performing attribute parameterization operations on single or batch commands, three mapping tables are constructed;

[0007] Parameterize single or batch commands;

[0008] When the value of a parameter is modified, it affects all entities parameterized by the parameter.

[0009] Optionally, when performing attribute parameterization operations on a single or batch command, constructing three mapping tables specifically includes:

[0010] A global mapping table of entities and related commands. For different entities in the EDA model, there is a unique entity ID, and for each command of the entity, there is a unique command ID.

[0011] Establish a global parameterized mapping table;

[0012] For a single command that supports parameterization, a mapping table between attribute types and parameter names is constructed.

[0013] Optionally, the unique ID is used to search for data quickly and reduce the amount of data in the mapping table; the mapping table includes the correspondence between all entities and commands.

[0014] Optionally, establishing a global parameterized mapping table specifically includes:

[0015] The entity ID and command ID are unique. For each attribute of the command, there is also a unique attribute type identifier, which is composed of three data types.

[0016] The mapping table GMAP2 is constructed using a linked list consisting of parameter names and tuples. The mapping table includes all parameterized data.

[0017] Optionally, for a single command that supports parameterization, constructing a mapping table between attribute types and parameter names specifically includes:

[0018] When a mapping table includes a certain attribute type, it means that the attribute has been parameterized, and the parameter name corresponding to the attribute type is the parameterized name;

[0019] When the mapping table does not include the attribute being operated, it means that the attribute has not been parameterized.

[0020] Optionally, the parameterization processing of a single or batch command specifically includes:

[0021] The parameterized name entered by the user is used as the key value of the mapping table. The linked list consisting of the tuples of the entity ID, command ID, and attribute type associated with the parameter name is used as the value of the mapping table to construct GMAP2. The single or multiple commands being operated are added to the mapping table MAP3 consisting of their own attribute types and parameter names, and the specific parameterized values ​​are updated to the attributes corresponding to the commands.

[0022] If the original data is a value rather than a parameter name, delete the mapping data between the attribute type and the parameter name in MAP3 added in the previous step, and update the command attributes at the same time;

[0023] If the original data is a parameter name, delete the mapping data between the attribute type and the parameter name in MAP3 added in the previous step, and add the mapping data consisting of the attribute type and the original data in MAP3;

[0024] Recalculate and render the associated entities.

[0025] Optionally, when modifying the value of the parameter, the modification affects all entities parameterized by the parameter, specifically including:

[0026] By traversing GMAP2, find the tuple list of all associated entity IDs, command IDs, and attributes that need to be updated in the command;

[0027] Find the corresponding command in GMAP1 using the found entity ID and command ID, and then set the new value to the corresponding attribute of the command found in the previous step and its MAP3;

[0028] When performing the Undo operation, it is also necessary to traverse GMAP2 to find the tuple list of all associated entity IDs, command IDs, and attribute types, and then use the found entity ID and command ID to find the corresponding command that needs to be Undo in GMAP1, and set the data to be restored to the corresponding attribute of the command to be Undo and MAP3.

[0029] The present invention provides a method for implementing parametric modeling of EDA data. The method includes: constructing three mapping tables when performing attribute parameterization operations on single or batch commands; performing parameterized processing on single or batch commands; and modifying parameter values ​​to affect all entities parameterized by the parameters. This method enables batch modification of model data, grouped parameter control, and supports redo / undo operations.

[0030] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are specifically listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0032] Figure 1 A data processing flow chart of parameterized operations provided by an embodiment of the present invention;

[0033] Figure 2 A schematic diagram showing the mapping relationship between GMAP1 and MAP3 constructed for the parameterized operation provided in an embodiment of the present invention;

[0034] Figure 3 A schematic diagram of the GMAP2 mapping relationship constructed for the parameterized operation provided in the embodiment of the present invention. DETAILED DESCRIPTION

[0035] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0036] The terms "comprises" and "comprising" and any variations thereof in the description, embodiments, claims and drawings of the present invention are intended to cover non-exclusive inclusions, for example, including a series of steps or units.

[0037] The technical solution of the present invention is further described in detail below with reference to the accompanying drawings and embodiments.

[0038] like Figure 1 As shown, a method for implementing EDA data parameterized modeling includes:

[0039] 1. When performing attribute parameterization operations on single or batch commands, three mapping tables are constructed:

[0040] 1.1 Global entity-to-command mapping table (referred to as GMAP1). Each entity in the EDA model has a unique entity ID, and each command in that entity has a unique command ID. Unique IDs are important for data lookup, as they enable faster lookups and reduce the amount of data in the mapping table. This mapping table contains all the corresponding relationships between entities and commands.

[0041] 1.2 Global parameterized mapping table (referred to as GMAP2). Entity IDs and command IDs are unique, and each attribute of a command also has a unique attribute type identifier. These three data types form a tuple. A linked list consisting of parameter names and tuples is used to construct the mapping table GMAP2, which contains all parameterized data.

[0042] 1.3 For individual commands that support parameterization, a mapping table (referred to as MAP3) is constructed between attribute types and parameter names. When the mapping table contains an attribute type, it indicates that the attribute has been parameterized, and the parameter name corresponding to the attribute type is the parameterized name. Conversely, when the mapping table does not contain the attribute being operated on, it indicates that the attribute has not been parameterized.

[0043] The process of parameterizing a single or batch command is as follows: The GMAP1 mapping table has been constructed when the command is created, so only GMAP2 and MAP3 need to be constructed during parameterization. The parameterized name entered by the user is used as the Key value of the mapping table, and the linked list consisting of all tuples of entity ID, command ID, and attribute type associated with the parameter name is used as the Value value of the mapping table to construct GMAP2; the single or multiple commands being operated add their own attribute types and parameter names to the mapping table MAP3, and update the specific parameterized values ​​to the attributes corresponding to the command. Finally, all associated entities are recalculated and rendered. When performing the Undo operation, the attributes of the command need to be restored with the original data, and the corresponding entity ID, command ID, and attribute type tuple are removed from GMAP2. There are two situations for command processing:

[0044] 2.1 If the original data is a value rather than a parameter name, you need to delete the mapping data between the attribute type and the parameter name in MAP3 added in the previous step, and update the command attributes at the same time.

[0045] 2.2 If the original data is a parameter name, you need to delete the mapping data between the attribute type and the parameter name in MAP3 added in the previous step, and add new mapping data consisting of the attribute type and the original data in MAP3.

[0046] Finally, the associated entities are recalculated and rendered.

[0047] When the value of a parameter is modified, it will affect all entities parameterized by this parameter. The method is as follows: by traversing GMAP2, find the tuple list of all associated entity IDs, command IDs, and attributes that need to be updated in the command. Then find the corresponding command in GMAP1 using the found entity ID and command ID, and then set the new value to the corresponding attribute of the command found in the previous step and its MAP3. When performing the Undo operation, it is also necessary to traverse GMAP2 to find the tuple list of all associated entity IDs, command IDs, and attribute types, and then find the corresponding command that needs to be Undo in GMAP1 using the found entity ID and command ID, and set the data to be restored to the corresponding attribute of the command to be Undo and its MAP3.

[0048] This invention provides a method for modifying multiple model data sets simultaneously by replacing model data with user-entered parameter names and modifying the parameter name values. By establishing a custom mapping table between parameter names and entities, commands, and attributes, this method allows for simultaneous updates of multiple model data sets with a single data modification. Redo / Undo support allows for efficient batch data modification to create models that meet requirements.

[0049] Beneficial Effects: This invention implements batch modification of model data, grouping parameter control functions, and supports Redo / Undo. This makes user operation of model data more efficient and convenient. Previously, when modifying a group of model data, it was necessary to search and select each one individually before modifying the parameters. Now, only the parameter name needs to be associated to perform batch modification operations on the model data, which greatly facilitates user data operations.

[0050] The above specific implementation methods further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation methods of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for implementing EDA data parameterized modeling, characterized in that: The implementation method includes: When performing attribute parameterization operations on single or batch commands, three mapping tables are constructed, including: The global entity and related command mapping table GMAP1 has a unique entity ID for each entity of the EDA model and a unique command ID for each command of the entity; The mapping table GMAP1 includes the correspondence between all entities and commands; Establish a global parameterized mapping table GMAP2; The establishment of the global parameterized mapping table GMAP2 specifically includes: The entity ID and command ID are unique. For each attribute of the command, there is also a unique attribute type identifier, which is composed of three data types. Construct a parameterized mapping table GMAP2 using a linked list consisting of parameter names and tuples. The parameterized mapping table GMAP2 includes all parameterized data. For a single command that supports parameterization, a mapping table MAP3 between attribute types and parameter names is constructed; Parameterize single or batch commands; When the value of a parameter is modified, it affects all entities parameterized by the parameter.

2. The method for implementing EDA data parameterized modeling according to claim 1, characterized in that: For a single command supporting parameterization, constructing a mapping table MAP3 between attribute types and parameter names specifically includes: When the mapping table MAP3 includes a certain attribute type, it means that the attribute has been parameterized, and the parameter name corresponding to the attribute type is the parameterized name; When the mapping table MAP3 does not include the attribute type being operated, it means that the attribute has not been parameterized.

3. The method for implementing EDA data parameterized modeling according to claim 1, characterized in that: The parameterization processing of a single or batch command specifically includes: The parameter name entered by the user is used as the key value of the mapping table GMAP2. The linked list consisting of all tuples of entity ID, command ID, and attribute type associated with the parameter name is used as the value of the mapping table GMAP2 to construct the mapping table GMAP2. The single or multiple commands being operated are added to the mapping table MAP3 consisting of their own attribute types and parameter names, and the specific parameterized values ​​are updated to the attributes corresponding to the commands. When performing the Undo operation, the command attributes are restored with the original data, and the corresponding entity ID, command ID, and attribute type tuple are removed from the mapping table GMAP2; If the original data is a value rather than a parameter name, delete the mapping data between the attribute type and the parameter name in the mapping table MAP3 added in the previous step, and update the command attributes at the same time; If the original data is a parameter name, delete the mapping data between the attribute type and the parameter name in the mapping table MAP3 added in the previous step, and add the mapping data consisting of the attribute type and the original data to the mapping table MAP3; Recalculate and render the associated entities.

4. The method for implementing EDA data parameterized modeling according to claim 3, wherein: When modifying the value of a parameter, all entities parameterized by the parameter are affected, including: By traversing the mapping table GMAP2, find the tuple list of all associated entity IDs, command IDs, and attributes that need to be updated in the command; Find the corresponding command in the mapping table GMAP1 using the found entity ID and command ID, and then set the new value to the corresponding attribute of the command found in the previous step and its mapping table MAP3; When performing the Undo operation, the mapping table GMAP2 is also traversed to find the tuple linked list of all associated entity IDs, command IDs, and attribute types. Then, the corresponding command that needs to be Undo is found in the mapping table GMAP1 through the found entity ID and command ID, and the data to be restored is set to the corresponding attribute of the command to be Undo and the mapping table MAP3.

Images