Parametric-driven PCB design data processing methods, devices, and storage media

Abstract

This application discloses a parametric-driven PCB design data processing method, device, and storage medium. Relating to the fields of PCB design and simulation technology, the parametric-driven PCB design data processing method includes: receiving a PCB design file; creating parametric objects corresponding to each element in the PCB design file based on a pre-established data model; generating geometric data based on the parametric objects in response to a simulation request, using a unified geometry generation interface defined in the data model and the business type of the simulation request; and releasing the geometric data in response to a simulation end request. This application achieves the technical effect of reducing system memory resource consumption and supporting large-scale PCB design data processing through a mechanism of parametric storage, on-demand generation, and release after use.

Description

Technical Field

[0001] This application relates to the field of PCB design and simulation technology, and in particular to a parametrically driven PCB design data processing method, device and storage medium. Background Technology

[0002] In the field of PCB design and simulation, layout data management is the foundation of downstream simulation. Existing architectures mostly employ either a direct geometry model or a module-based independent conversion model. The former expands all primitives into explicit geometric shapes during the import phase, leading to memory bloat and excessively long initialization times; the latter has each simulation module independently maintaining its conversion logic, causing data redundancy and consistency issues. Both models suffer from the drawback of tight coupling between parametric data and geometry generation. Therefore, existing PCB design data management solutions suffer from excessive memory resource consumption.

[0003] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0004] The main purpose of this application is to provide a parametric-driven PCB design data processing method, device, and storage medium, which aims to solve the technical problem of large memory consumption in the existing PCB layout data management architecture, where parametric data and geometry generation are tightly coupled, making it impossible to generate geometric shapes on demand according to business needs.

[0005] To achieve the above objectives, this application provides a parameter-driven PCB design data processing method, which includes: Receive PCB design files; Based on the pre-established data model, create parametric objects corresponding to each element in the PCB design file; In response to a simulation request, geometric data is generated based on the parameterized object using the unified geometry generation interface defined in the data model and the business type of the simulation request. In response to the simulation end request, the geometric data is released.

[0006] In one embodiment, the data model defines a layer container class and a parameterized primitive abstract base class. The layer container class is used to define at least one layer, including a layer name, a layer type identifier, a layer thickness parameter, and parameterized primitives on the layer. The parameterized primitive abstract base class defines virtual functions and parameterized structures for multiple primitive types.

[0007] In one embodiment, prior to the step of generating geometric data based on the parameterized object in response to a simulation request, using the unified geometry generation interface defined in the data model and the business type of the simulation request, the method includes: The virtual function is defined as a unified geometry generation interface of the parameterized primitive abstract base class, and the input of the unified geometry generation interface includes a precision parameter; the unified geometry generation interface is used to convert the parameterized data of the parameterized object into geometric data.

[0008] In one embodiment, the step of creating parametric objects corresponding to each element in the PCB design file based on a pre-established data model includes: Based on the primitive type of the primitive, the parameterized structure is determined in the parameterized primitive abstract base class of the data model; Determine the geometric attribute parameters of the primitive and write the geometric attribute parameters into the parameterized structure; The layer parameters corresponding to the layer container class of the data model are determined based on the layer to which the graphic element belongs; Based on the written parameterized structure and the corresponding layer parameters, create parameterized objects corresponding to each primitive.

[0009] In one embodiment, after the step of creating parametric objects corresponding to each element in the PCB design file based on a pre-established data model, the method includes: Obtain the network identifier of the graphic element, and construct a network index based on the network identifier; Based on the network index, primitives with the same network identifier are associated with the primitive type of the parameterized primitive abstract base class corresponding to the data model.

[0010] In one embodiment, the step of generating geometric data based on the parameterized object in response to a simulation request, using a unified geometry generation interface defined in the data model and the business type of the simulation request, includes: Determine the generation strategy corresponding to the service type of the simulation request; The target parameterized object corresponding to the simulation request is determined according to the generation strategy; Determine the precision parameters of the unified geometry generation interface; Based on the target parameterized object and the precision parameters, the unified geometry generation interface is invoked to generate geometric data.

[0011] In one embodiment, the step of generating geometric data based on the parameterized object in response to a simulation request, using the unified geometry generation interface defined in the data model and the business type of the simulation request, further includes: When the simulation request is a structural and fluid simulation, the current generation strategy is determined to require only the coverage ratio of copper in space; Based on the generation strategy, the parameterized objects corresponding to the structural and fluid simulations are determined to be the pad symbol parameter class in the parameterized primitive abstract base class; Determine the precision parameters of the unified geometry generation interface; Geometric data is generated based on the unified geometry generation interface called according to the pad symbol parameter class and the precision parameter.

[0012] In one embodiment, the step of generating geometric data based on the parameterized object in response to a simulation request, using the unified geometry generation interface defined in the data model and the business type of the simulation request, further includes: When the simulation request is mesh partitioning, the current generation strategy is determined to be that only the connected geometric regions of the electrical network are needed. Based on the generation strategy, the target parameterized object corresponding to the mesh partitioning is determined to be an electrical network parameter class; Determine the precision parameters of the unified geometry generation interface; Geometric data is generated based on the unified geometry generation interface invoked according to the electrical network parameter class and the precision parameters.

[0013] In addition, to achieve the above objectives, this application also provides a parameter-driven PCB design data processing device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the parameter-driven PCB design data processing method described above.

[0014] In addition, to achieve the above objectives, this application also provides a storage medium, which is a computer-readable storage medium, storing a program that implements a parameterized PCB design data processing method. The program that implements the parameterized PCB design data processing method is executed by a processor to implement the steps of the parameterized PCB design data processing method as described above.

[0015] This application provides a parameterized-driven PCB design data processing method. By receiving a PCB design file and creating parameterized objects corresponding to each element in the PCB design file based on a pre-established data model, the method stores each element in the PCB design file as parameterized data. This allows the PCB design data to be handled with significantly less memory than geometric data, avoiding the technical problem of memory overflow caused by loading all geometric data at once, which would prevent the processing of complex PCB designs. In response to a simulation request, based on the generation strategy corresponding to the business type of the simulation request and using a unified geometry generation interface, geometric data is generated from the parameterized objects. This enables simulation calculations to generate geometric data on demand, eliminating the need to pre-load all geometric data. In response to a simulation end request, the geometric data is released, allowing the system to return to a lightweight state with only parameterized data after the simulation is completed. This avoids the technical problem of subsequent simulation tasks being unable to be processed due to continuous memory occupation by geometric data, achieving the technical effect of low-memory PCB design data management.

[0016] This application stores PCB design data as parametric objects and generates geometric data on demand in response to simulation requests and releases geometric data in response to simulation end requests. This ensures that only parametric data is retained in memory, avoiding the continuous residence of memory-intensive geometric data throughout the simulation process. This reduces the dependence on memory capacity and improves the system's ability to process large-scale PCB design data. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 A flowchart illustrating an embodiment of the parameter-driven PCB design data processing method of this application; Figure 2 A flowchart illustrating Embodiment 2 of the parameter-driven PCB design data processing method of this application; Figure 3 A flowchart is provided for Embodiment 3 of the parameter-driven PCB design data processing method of this application; Figure 4 This is a simplified flowchart illustrating the parameterized PCB design data processing method provided in Embodiment 3 of this application.

[0020] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0021] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of this application and are not intended to limit this application.

[0022] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0023] Currently, traditional PCB design and simulation data management solutions typically load all geometric data from the PCB design file into memory at once, which can then be used for various business scenarios such as electromagnetic simulation, structural simulation, and fluid simulation. However, with the increasing complexity of PCB designs, the number of primitives in the design file grows exponentially. The high memory consumption of complete geometric data makes the traditional full-load solution unsuitable for handling ultra-large-scale PCB design data with limited memory resources, leading to frequent memory overflows or a sharp decline in processing efficiency. Therefore, current PCB design data management solutions suffer from the technical problem of excessive memory resource consumption.

[0024] The main solution of this application is as follows: receiving PCB design files; creating parametric objects corresponding to each element in the PCB design files according to a pre-established data model; generating geometric data based on the parametric objects in response to a simulation request, using a unified geometry generation interface defined in the data model and the business type of the simulation request; and releasing the geometric data in response to a simulation end request. This application solves the technical problem of excessive memory resource consumption by storing each element in the PCB design file as parametric data, generating geometric data on demand in response to simulation requests, and releasing geometric data in response to simulation end requests, thus ensuring that only parametric data is retained in memory.

[0025] It should be noted that the execution subject in this embodiment can be a parameter-driven PCB design data processing device, or a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, server, etc., or a PCB design data management system capable of implementing the above functions, etc. This embodiment does not specifically limit it. The following uses a parameter-driven PCB design data processing device as the execution subject as an example to describe this embodiment and the following embodiments.

[0026] Based on this, Embodiment 1 of this application proposes a parameter-driven PCB design data processing method, please refer to... Figure 1The parameterized PCB design data processing method includes steps S10 to S40: Step S10: Receive PCB design files.

[0027] In this embodiment, the PCB design file is a raw data file used to describe the physical structure and electrical connections of a printed circuit board. The PCB design file includes, but is not limited to, the following data: geometric attribute parameters of each element, layer information to which each element belongs, and net identifiers of each element.

[0028] As an optional implementation, a file receiving and parsing mechanism is set at the input interface of the data model. This mechanism receives the PCB design file and identifies its format type. For PCB design files using open formats such as Gerber, ODB++, and IPC-2580, the corresponding format parser is invoked to directly read the layer data, primitive geometric parameters, and network connection information from the file. For PCB design files using proprietary binary formats, a corresponding third-party parsing library is invoked to extract the design data.

[0029] Step S20: Based on the pre-established data model, create parametric objects corresponding to each element in the PCB design file.

[0030] In this embodiment, the data model refers to a pre-established structured framework for organizing and managing the parametric data of various elements in the PCB design file. It consists of a layer container class and a parametric element abstract base class, serving as the input source for all geometry generation operations. The layer container class defines and manages each layer in the PCB design file and its parametric elements, including the layer name, layer type identifier, layer thickness parameter, and a collection of all parametric elements on that layer. The parametric element abstract base class contains public data members and various parametric element types. The public data members include bounding box parameters, network identifier, and element type enumeration. The bounding box parameter is used for rapid spatial range lookup and visibility determination. By storing the minimum and maximum coordinate range of the element on the two-dimensional plane, it enables rapid spatial location of the element. The network identifier is used to associate the element with the electrical network it belongs to, so that elements can be aggregated by electrical network and network-level geometric data can be generated subsequently. The element type enumeration is used for runtime type identification, enabling the system to determine the specific type of the element at runtime to execute the corresponding processing logic. The line segment parameter class inherits from the parameterized primitive abstract base class and describes a line segment parametrically, including start coordinates, end coordinates, line width, and line cap style parameters. The arc segment parameter class inherits from the parameterized primitive abstract base class and describes an arc parametrically, including center coordinates, radius, start angle, end angle, line width, and arc direction parameters. The circle parameter class inherits from the parameterized primitive abstract base class and describes a solid circle or annulus parametrically, including center coordinates, outer radius, and inner radius parameters. The fill surface parameter class inherits from the parameterized primitive abstract base class and describes a fill area of ​​arbitrary shape parametrically, including... The class includes a sequence of outer boundary vertex coordinates, a list of inner hole vertex coordinate sequences, and a fill type identifier parameter; the pad symbol parameter class inherits from the parametric primitive abstract base class and describes the type definition of a pad in a parametric manner, including the pad symbol name, pad shape type, shape size parameters, and drilling parameters; the pad instance parameter class inherits from the parametric primitive abstract base class and describes the specific placement instance of a pad in a parametric manner, including a reference to the pad symbol parameter class, the center position coordinates of the pad, and rotation angle parameters; the electrical network parameter class represents an electrical network and is a container class that aggregates references to all primitives belonging to the same electrical network.

[0031] As an optional implementation, the element type and geometric attribute parameters of each element are extracted from the elements in the PCB design file. Based on the element type of each element, the corresponding parameterized structure is matched in the parameterized element abstract base class of the data model, and the geometric attribute parameters of each element are written into the corresponding attribute fields of the parameterized structure. At the same time, based on the layer to which each element belongs, the corresponding layer container is determined in the layer container class of the data model, and the parameterized object corresponding to each element is created based on the written parameterized structure and the corresponding layer container.

[0032] Optionally, after importing the layout design file, corresponding parametric objects are created based on the primitive records in the design file and organized by layers and networks. This process does not trigger the generation of any geometry.

[0033] Optionally, the pad instance parameter class describes the pad instance by referencing the pad symbol parameter class object and attaching position coordinates and rotation angles, so that multiple pad instances of the same specification can share the same shape parameter definition, achieving separate storage of symbols and instances.

[0034] Optionally, the electrical network parameter class aggregates references to all primitives under the network, and its geometry generation interface traverses all sub-primitives to generate geometric data respectively, and can selectively perform Boolean union operations on the generated geometric data to merge connected regions.

[0035] Step S30: In response to the simulation request, generate geometric data based on the parameterized object using the unified geometry generation interface defined in the data model and the business type of the simulation request.

[0036] In this embodiment, a simulation request refers to a geometric data acquisition request initiated by downstream applications such as electromagnetic simulation, structural and fluid simulation, and mesh generation during the PCB design and simulation process. The simulation request carries a business type identifier to indicate the type of the current simulation scenario. The business type refers to the specific simulation scenario category corresponding to the simulation request, including but not limited to electromagnetic simulation and structural and fluid simulation. Different business types have different accuracy requirements and focus dimensions for geometric data. The generation strategy refers to the geometric data generation rules corresponding to each business type, used to determine the range of parameterized objects and the configuration of accuracy parameters required when generating geometric data. The unified geometry generation interface refers to a virtual function defined in the parameterized primitive abstract base class. The input of the unified geometry generation interface includes accuracy parameters, and the output is geometric data. Geometric data refers to closed polygon geometric data used for simulation calculations, generated by converting parameterized objects through the unified geometry generation interface.

[0037] As an optional implementation, a generation strategy corresponding to the business type of the simulation request is determined, a target parameterized object corresponding to the simulation request is determined according to the generation strategy, and the precision parameters of the unified geometry generation interface are determined. The unified geometry generation interface is then called according to the target parameterized object and the precision parameters to generate geometric data.

[0038] Optionally, when geometric data is required, the parameterized object can dynamically calculate and generate the geometric data based on its stored parameters by calling the unified geometry generation interface.

[0039] Optionally, the unified geometry generation interface is controlled by a precision parameter, and different discretization precisions can be selected for different business scenarios to achieve a flexible balance between geometric precision and computation speed.

[0040] Step S40: In response to the simulation end request, release the geometric data.

[0041] In this embodiment, the simulation end request refers to a geometric data release instruction triggered by the simulation module or upper-layer business code after the simulation calculation is completed. This instruction notifies the system that the geometric data required for the current simulation has been used up. Releasing refers to the operation of returning the memory space occupied by the geometric data to the operating system or memory manager.

[0042] As an optional implementation, the computational status of geometric data is monitored. When the computational operation on the geometric data is detected to be complete, the memory space occupied by the geometric data is released, and the memory management record is updated to mark this part of the memory as reclaimable for subsequent computational tasks to reallocate. Although regenerating geometric data on demand each time incurs additional CPU time overhead, the parameterization-to-geometry conversion algorithm executed by the unified geometry generation interface is a pure numerical calculation, which modern CPUs can complete in a very short time. The resulting memory savings, especially for large-scale PCB layout scenarios, far outweigh the small overhead of regeneration. Furthermore, since the parameterized data is immutable after import, the results produced by each call to the unified geometry generation interface are naturally consistent, eliminating issues of cache invalidation or data inconsistency.

[0043] Optionally, after the business calculation is completed, the geometric data is released, and the system reverts to a lightweight state that only maintains parameterized data.

[0044] Through the above steps, this application provides a parameterized-driven PCB design data processing method. By constructing a data model including a layer container class and a parameterized primitive abstract base class, each primitive is stored in a parameterized structure, which can carry large-scale PCB design data with a memory footprint far lower than that of geometric data. By defining virtual functions in the parameterized primitive abstract base class as a unified geometry generation interface, and having each subclass implement this interface, it is possible to avoid modifying the upper-level business logic when adding new primitive types, thus avoiding the technical defects of poor system scalability and high maintenance costs. It avoids the technical defects of memory overflow, poor scalability and high scene adaptation costs in traditional solutions, and achieves the technical effects of low memory footprint, high scalability and multi-scene reuse.

[0045] In one possible implementation, step B31 may be included before step S30: Step B31: Define the virtual function as a unified geometry generation interface of the parameterized primitive abstract base class. The input of the unified geometry generation interface includes a precision parameter. The unified geometry generation interface is used to convert the parameterized data of the parameterized object into geometric data.

[0046] In this embodiment, the unified geometry generation interface refers to a virtual function defined in the parameterized primitive abstract base class. Its input parameters include a precision parameter, and its output is geometric data. The precision parameter controls the precision of the geometric data discretization, used to adjust the fineness of geometry generation in different business scenarios, such as the piecewise linearization step size of arc segments or the polygon approximation angle step size of circular boundaries. A virtual function is a function declared in the base class without providing an implementation. Since the geometry generation logic of different primitive types is completely different, the parameterized primitive abstract base class cannot provide a unified default implementation. Therefore, the unified geometry generation interface is defined as a virtual function, forcing each subclass to implement its own geometry generation logic. Upper-level business code can trigger geometry generation through a base class pointer without needing to know the specific subclass type, thus achieving polymorphic access to parameterized data types.

[0047] As an optional implementation, the specific geometric generation logic of the virtual function implemented by each parameterized primitive type is as follows: The line segment parameter class determines the centerline direction based on the start and end coordinates, and offsets the centerline outward by half a line width along the normal direction according to the line width parameter, constructing a rectangular closed loop with the centerline as the axis. When the line cap style is a flat cap, a rectangular closed loop composed of four vertices is generated; when the line cap style is a round cap, a discretized vertex sequence of a semicircular region is added to each end of the rectangular closed loop to generate a closed loop with rounded corners; the arc segment parameter class determines the direction of the centerline based on the starting angle. The angle range of the arc segment is determined by the termination angle. The center arc is offset inward and outward by half a line width along its normal direction. Simultaneously, the end caps at both ends of the arc segment are geometrically processed to generate closed polygonal loops. The curved portion of the arc segment is approximated using piecewise linearization, with the angle step size controlled by the input precision parameter. For circular parameters, polygonal approximations are performed on the outer and inner circle boundaries respectively, generating outer and inner loops that form a closed polygonal region with holes. For solid circles, only the outer loop is generated; for toroidal bodies, both the outer and inner loops are generated simultaneously. The polygonal approximation accuracy of the circular boundary is determined by the input precision parameter. The control and filling parameters class uses the stored outer boundary vertex coordinate sequence as the outer ring and the inner hole vertex coordinate sequence as the inner ring to generate the corresponding closed polygonal region. The pad symbol parameter class generates the corresponding closed polygonal ring or closed region with holes according to the pad shape type and shape size parameters. For rectangles, a rectangular closed ring is generated according to the width and height. For ellipses, an elliptical closed ring is generated by polygon approximation. For rounded rectangles, a rectangular closed ring with rounded corners is generated. For custom polygons, a closed ring is generated by taking the vertex sequence of the custom polygon. The drill diameter is used to generate the inner hole boundary. The pad instance parameter class obtains the shape parameters defined in the referenced pad symbol parameter class to generate the geometric ring of the pad symbol. Then, it performs coordinate transformation on the geometric ring according to the position coordinates and rotation angle of the pad instance to generate the final geometric data corresponding to the pad instance. The electrical network parameter class traverses all aggregated sub-primitives, calls the geometric generation interface of each sub-primitive in turn to generate the geometric data corresponding to each sub-primitive, and performs Boolean union operation on each geometric data to merge the geometric rings of mutually contacting or overlapping primitives into connected geometric rings to obtain the network-level geometric data of the electrical network. In the above manner, each parametric primitive type implements its own geometric generation logic according to its stored parameters and the input precision parameters, and generates the corresponding geometric data.

[0048] Optionally, parameterized data is immutable after import, and the unified geometry generation interface always returns consistent geometry data for the same input parameters, eliminating the need to maintain cache invalidation or data consistency mechanisms.

[0049] Through the above steps, this application completes the definition of the unified geometry generation interface in the base class and its implementation in each subclass. Upper-level business code can call the unified geometry generation interface through the base class pointer to implement the geometry generation logic of different subclasses. When adding a new primitive type, only a new subclass needs to be added and the interface implemented; no modification to any upper-level business logic is required. The precision parameter serves as the interface input, allowing different business scenarios to control the geometry discretization precision as needed. This reduces computational overhead while ensuring simulation accuracy, achieving a flexible balance between precision and performance.

[0050] Based on Embodiment 1, Embodiment 2 of this application proposes a parameter-driven PCB design data processing method, referring to... Figure 2 Step S20 may include steps A21 to A24: Step A21: Determine the parameterized structure in the parameterized primitive abstract base class of the data model according to the primitive type of the primitive.

[0051] In this embodiment, a parameterized structure refers to a predefined structured data template in the parameterized primitive abstract base class for each primitive type, used to describe the set of parameter items that need to be stored for that type of primitive. Since there are various primitive types in PCB design files, and different primitive types require different parameter items, it is necessary to match a corresponding parameterized structure for each primitive type.

[0052] As an optional implementation, each element in the PCB design file is traversed, and the corresponding parameterized structure is matched in the parameterized element abstract base class of the data model according to the element type. When a line segment element is encountered, the parameterized structure corresponding to the line segment parameter class is matched according to the line segment element type. The line segment parameterized structure includes a start coordinate field, an end coordinate field, a line width field, and a line cap style field. When a pad element is encountered, the parameterized structure corresponding to the pad instance parameter class is matched according to the pad element type. The pad instance parameterized structure includes a center position coordinate field, a reference symbol name field, and a rotation angle field. When a via element is encountered, the parameterized structure corresponding to the circle parameter class is matched according to the via element type. The circle parameterized structure includes a center coordinate field, an outer radius field, and an inner radius field. Thus, each element is matched with its corresponding parameterized structure, preparing for the subsequent writing of geometric attribute parameters into the corresponding fields.

[0053] Step A22: Write the geometric attribute parameters into the parameterized structure according to the geometric attribute parameters of the primitive.

[0054] In this embodiment, geometric attribute parameters refer to the specific numerical values ​​carried by each element in the PCB design file that describe the geometric characteristics of that element. Examples include the start coordinates, end coordinates, and line width of a line segment element, and the center coordinates and shape dimensions of a pad element. Writing refers to filling the aforementioned geometric attribute parameter values ​​into the corresponding fields of the matched parameterized structure.

[0055] As an optional implementation, after extracting the geometric attribute parameters of each element from the PCB design file, each geometric attribute parameter is written into the attribute field of the corresponding parametric structure. For example, for a line segment element with a start coordinate of (10.0, 20.0), an end coordinate of (30.0, 40.0), and a line width of 0.2mm, its start coordinates are written into the start coordinate field of the line segment parametric structure, its end coordinates are written into the end coordinate field, and its line width is written into the line width field.

[0056] Step A23: Determine the layer parameters corresponding to the layer container class of the data model based on the layer to which the graphic element belongs.

[0057] In this embodiment, layer parameters refer to the parameter items defined in the layer container class that describe layer attributes, including layer name, layer type identifier, and layer thickness parameter. Since each graphic element in the PCB design file belongs to a specific layer, the corresponding layer parameters need to be determined based on the layer to which the graphic element belongs when creating a parameterized object.

[0058] As an optional implementation, the corresponding layer parameters are determined in the layer container class of the data model according to the layer to which each graphic element belongs.

[0059] Step A24: Based on the written parameterized structure and the corresponding layer parameters, create parameterized objects corresponding to each graphic element.

[0060] In this embodiment, creating a parameterized object refers to binding the parameterized data of a graphic element with its layer affiliation information based on the parameterized structure after writing the geometric attribute parameters and the determined layer parameters, thereby generating a complete parameterized object instance. The parameterized object is the unique instantiation of a graphic element in the data model; it contains both the geometric attribute parameter values ​​of the graphic element itself and the parameter information of the layer to which the graphic element belongs.

[0061] As an optional implementation, parameterized object instances are created based on the written parameterized structure, and these instances are associated with layer parameters to generate parameterized objects corresponding to each primitive. For multiple primitives belonging to the same layer, their parameterized objects are all bound to the same layer parameters, but each maintains independent geometric attribute parameter values. For example, multiple line segments on the top-level signal layer correspond to multiple line segment parameterized objects, each associated with the layer parameters of the top-level signal layer, but each containing different start-point coordinates, end-point coordinates, and line width values.

[0062] For example, for a PCB design file containing three primitive types—line segments, pads, and vias—the process iterates through each primitive in the PCB design file. When a line segment is encountered, its parametric structure is matched, and the start-point coordinates, end-point coordinates, and line width are written into the corresponding fields of the structure. The layer parameters are then determined based on the layer to which the line segment belongs, and a parametric object for the line segment is created. When a pad is encountered, its parametric structure is matched, and the center coordinates and shape dimensions are written into the corresponding fields of the structure. The layer parameters are then determined based on the layer to which the pad belongs, and a parametric object for the pad is created. When a via is encountered, its parametric structure is matched, and the center coordinates and via diameter are written into the corresponding fields of the structure. The layer parameters are then determined based on the layer to which the via belongs, and a parametric object for the via is created. After all the parametric objects for each primitive are created, the parametric data and layer affiliation information for each primitive are stored in the data model. Only the parametric data of each primitive is retained in memory; no explicit geometric data is included.

[0063] Through the above steps, this application completes the creation of parametric objects for each element in the PCB design file. By matching the corresponding parametric structure according to the element type, different element types are classified and stored, ensuring that different element types such as line segments, pads, and vias have a unified structured representation in the data model. By creating parametric objects based on the written parametric structure and corresponding layer parameters, parametric storage of elements is achieved. Therefore, only the parametric data of each element is retained in memory, without containing any explicit geometric data, providing a lightweight data foundation for subsequent on-demand generation of geometric data and avoiding the technical problem of memory overflow caused by loading all geometric data at once in traditional solutions.

[0064] In one possible implementation, steps S20 may be followed by steps S21-S22: Step S21: Obtain the network identifier of the graphic element and construct a network index based on the network identifier.

[0065] In this embodiment, a network identifier refers to a unique identifier for the electrical network to which each element in a PCB design file belongs, used to distinguish different electrical networks. All elements within the same electrical network have the same network identifier, and these elements are electrically interconnected. A network index is a data structure that uses the network identifier as the key and a list of elements with that network identifier as the value, used to quickly find all elements belonging to the same electrical network. Since a PCB design file contains tens of thousands of elements, traversing all elements to query all elements within a specific electrical network would result in low query efficiency.

[0066] As an optional implementation, after creating parameterized objects for all primitives, the primitives stored in the data model are traversed, and the network identifiers of each primitive are extracted. For each network identifier, if the network identifier already exists, the parameterized object reference of the current primitive is added to the corresponding primitive list; if the network identifier does not exist, a new primitive list is created with the parameterized object reference of the current primitive as the initial element. After traversal, a network index is obtained with the network identifier as the key and the primitive list as the value.

[0067] Step S22: Associate primitives with the same network identifier to the primitive type of the parameterized primitive abstract base class corresponding to the data model according to the network index.

[0068] In this embodiment, the electrical network parameter class is a container class that inherits from the parameterized primitive abstract base class. It is used to aggregate all primitive references belonging to the same electrical network. By associating each primitive with the corresponding electrical network parameter class object, the upper-level business code can call the unified geometry generation interface of the electrical network parameter class to traverse all its aggregated sub-primitives and generate network-level connected geometric data.

[0069] As an optional implementation, a corresponding number of electrical network parameter class objects are created based on the number of network identifiers, with each electrical network parameter class object initialized with a network identifier. Based on the constructed network index, references to the parameterized objects of all elements under the same network identifier are added to the element aggregation set of the corresponding electrical network parameter class object. For elements that have already been associated, the reference to their respective electrical network parameter class object is recorded in the network association field of their parameterized object, establishing a bidirectional association relationship.

[0070] Through the above steps, this application completes the aggregation management of various graphic elements according to electrical networks. By constructing a network index, graphic elements with the same network identifier are associated with the corresponding electrical network parameter class object, so that all graphic elements under the same electrical network are aggregated into the same electrical network parameter class object; by associating each graphic element with the graphic element type of the corresponding parameterized graphic element abstract base class, geometric data can be generated in batches, and also can be generated independently on demand for individual graphic elements. Thus, it provides flexible data acquisition capabilities for different business scenarios such as electromagnetic simulation, structural simulation, and fluid simulation.

[0071] Based on Embodiment 1, Embodiment 3 of this application proposes a parameter-driven PCB design data processing method, referring to... Figure 3 Step S30 may include steps S31 to S34.

[0072] Step S31: Determine the generation strategy corresponding to the service type of the simulation request.

[0073] In this embodiment, the generation strategy is a geometric data generation rule determined according to the business type. Different business types correspond to different generation strategies, specifically including the selection rules for the target parameterized object and the determination rules for the precision parameters. Different generation strategies determine the object range and precision configuration when generating geometric data.

[0074] As an optional implementation, a service type identifier is extracted from the simulation request, and the corresponding generation strategy is searched in a preset strategy mapping table based on the service type identifier. The strategy mapping table pre-configured the correspondence between each service type and the generation strategy. Each generation strategy includes two parts: a target selection rule and a precision determination rule. The target selection rule determines the range of target parameterized objects required for this simulation request, and the precision determination rule determines the precision parameters used when calling the unified geometry generation interface. For service scenarios requiring complete trace shapes and pad outline details, the precision determination rule instructs the unified geometry generation interface to be called with high-precision parameters; for service scenarios requiring only the copper coverage ratio in space, the precision determination rule instructs the unified geometry generation interface to be called with low-precision parameters, reducing computational overhead while meeting computational accuracy requirements. For service scenarios requiring electrical network connectivity geometry, the target selection rule instructs the selection of electrical network parameter class objects as target parameterized objects, and the precision determination rule instructs the calling of the unified geometry generation interface with high-precision parameters to ensure the accuracy of geometric boundaries.

[0075] Step S32: Determine the target parameterized object corresponding to the simulation request according to the generation strategy.

[0076] In this embodiment, the target parameterized object refers to the set of parameterized objects for which the current simulation request needs to generate geometric data. Since the PCB design file contains a large number of different types of primitives, and different simulation scenarios require different target objects, it is necessary to determine the target parameterized object corresponding to this simulation request based on the generation strategy.

[0077] As an optional implementation, the scope of target parameterized objects is determined according to the target selection rules in the generation strategy. When the target selection rule indicates that all primitives specified in the simulation request should be selected, the parameterized objects corresponding to each primitive specified in the simulation request are determined as target parameterized objects, forming a set of target parameterized objects. When the target selection rule indicates that only primitives of a specified layer should be selected, all parameterized objects stored in the data model are traversed, and the layer information associated with each parameterized object is used for filtering. Only parameterized objects belonging to the specified layer are determined as target parameterized objects, and parameterized objects not belonging to the specified layer are excluded.

[0078] Step S33: Determine the precision parameters of the unified geometry generation interface.

[0079] In this embodiment, the precision parameter refers to the parameter value that controls the discretization precision of geometric data. Parametric objects of the same primitive call the unified geometry generation interface with different precision parameters, resulting in different vertex densities and geometric approximation precisions in the generated geometric data. A higher precision parameter results in generated geometric data that is closer to the true shape, with more vertices and greater computational overhead; a lower precision parameter results in generated geometric data with fewer vertices and lower computational overhead, but the geometric precision decreases accordingly.

[0080] As an optional implementation, the corresponding precision parameter values ​​are determined based on the precision level configured in the generation strategy. For electromagnetic simulations requiring complete line segment shapes and pad outline details, high-precision parameters are determined, allowing the unified geometry generation interface to discretize curves with a smaller angle step size or chord height tolerance. For structural and fluid simulations requiring only the copper coverage ratio in space, low-precision parameters are determined, allowing the unified geometry generation interface to discretize curves with a larger angle step size or chord height tolerance, minimizing computational overhead while meeting the accuracy requirements for copper ratio calculation.

[0081] Step S34: Based on the target parameterized object and the precision parameters, call the unified geometry generation interface to generate geometric data.

[0082] In this embodiment, calling the unified geometry generation interface refers to calling the virtual function of the target parameterized object through a base class pointer, passing in the precision parameter, and performing the geometric data generation operation. Since the unified geometry generation interface is a virtual function defined in the abstract base class of parameterized primitives, and each parameterized primitive type implements this interface, when called through the base class pointer, the system automatically calls the implementation method of the corresponding subclass according to the actual type of the object pointed to by the pointer, thus achieving polymorphic access to parameterized data types.

[0083] As an optional implementation, the determined set of target parameterized objects is traversed. For each target parameterized object, the unified geometry generation interface is called through a base class pointer, with the determined precision parameters passed in as input. Each parameterized primitive type executes its own geometry generation logic based on its stored parameters and the passed precision parameters to generate corresponding geometric data. When the target parameterized object is an electrical network parameter class object, the unified geometry generation interface of the electrical network parameter class object is called. The electrical network parameter class object traverses all its aggregated sub-primitives, passing the precision parameters to the unified geometry generation interface of each sub-primitive to generate the corresponding geometric data for each sub-primitive. When the target parameterized object is a single primitive, the unified geometry generation interface of that primitive is directly called, with the precision parameters passed in. The primitive generates corresponding geometric data based on its stored parameters.

[0084] Optionally, in the copper ratio calculation scenario of structural and fluid simulation, the geometry generation interface of the parameterized object is called to generate geometric data. Then, the geometric data is discretized and rendered into a single-channel grayscale image. At the same time, the simulation mesh data is rendered into numbered images. The copper ratio value of each mesh unit is calculated in batches through image fusion. After the calculation is completed, the geometric data is released.

[0085] Through the above steps, this application realizes the on-demand generation and accuracy adaptation of geometric data under different business scenarios, so that the same set of data models and unified geometry generation interface can be reused in various business scenarios such as electromagnetic simulation, structural simulation, and fluid simulation. There is no need to build data models separately for different simulation scenarios or repeatedly implement geometry generation logic, which reduces computational overhead and development and maintenance costs while ensuring simulation accuracy.

[0086] For example, when an electromagnetic simulation request requires the generation of geometric data for a line segment and two pads, the parameterized objects of these three primitives are identified as target parameterized objects, and high-precision parameters are determined. High-precision parameters refer to discretizing the curve with a small angular step or chord height tolerance, resulting in a higher vertex density in the generated geometric ring and a shape that more closely approximates the real curve. Subsequently, the three target parameterized objects are traversed sequentially, and the unified geometry generation interface of each object is called through a base class pointer, passing in the high-precision parameters. The line segment object, based on its start and end points, line width, and line cap style, discretizes the rounded corner portion with a small angular step, generating a rounded rectangular ring with dense vertices. The two pad objects, based on their respective center coordinates, reference symbol definitions, and rotation angles, approximate the circular or elliptical boundaries with small angular steps, generating high-precision polygonal rings. After the three geometric data are generated, they are returned to the electromagnetic simulation module for electromagnetic field calculation. After the calculation is completed, in response to the simulation end request, the memory space occupied by the geometric data is released.

[0087] For example, when a structural and fluid simulation request requires calculation of the copper coverage ratio, the current generation strategy is determined to only require the copper coverage ratio in space. The parameterized objects of all primitives in the specified layer are identified as target parameterized objects, and low-precision parameters are determined. Low-precision parameters refer to discretizing curves with a larger angle step size or chord height tolerance, resulting in fewer generated geometric loop vertices and lower computational overhead. Subsequently, the target parameterized objects are traversed sequentially, and the unified geometry generation interface is called with low-precision parameters to generate geometric data for each primitive. The geometric data is discretized and rendered into a grayscale image, and the simulation mesh data is rendered as a numbered image. The copper percentage of each mesh unit is calculated through image fusion, and the copper percentage data is used as the input parameter for structural and fluid simulation. After calculation, the memory space occupied by the geometric data and intermediate image data is released. Furthermore, structural and fluid simulations typically do not concern themselves with the specific line segment shapes and pad outline details, only requiring the copper coverage ratio in space. Therefore, calling the unified geometry generation interface with low-precision parameters minimizes computational overhead while meeting the accuracy requirements for copper percentage calculation.

[0088] For example, when a meshing request requires generating a connected geometric region of an electrical network, the current generation strategy is determined to require a connected geometric region of the electrical network. The electrical network parameter class object is identified as the target parameterized object, and high-precision parameters are determined. Subsequently, the unified geometry generation interface of the electrical network parameter class object is called. The electrical network parameter class object traverses all its aggregated sub-primitives, calling the unified geometry generation interface of each sub-primitive to generate geometric data corresponding to each sub-primitive with high-precision parameters. Then, a Boolean union operation is performed on each geometric data, merging geometric loops of contacting or overlapping primitives into a connected geometric loop, eliminating internal overlapping boundaries and intersections, thus obtaining the network-level connected geometric data of the electrical network. The network-level connected geometric data is then fed into the mesh generator, which generates simulation mesh cells based on the connected geometric data. After meshing is completed, the memory space occupied by the geometric data is released. By calling the unified geometry generation interface of the electrical network parameter class object, all sub-primitives under the same electrical network are merged into a single connected geometric region, avoiding the problem of mesh generation failure caused by small gaps or overlaps between primitives, and ensuring the success rate and quality of mesh generation.

[0089] This application provides a parameter-driven PCB design data processing device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the parameter-driven PCB design data processing method in the above embodiment 1.

[0090] The following is for reference. Figure 4 This document illustrates a structural schematic diagram of a parametrically driven PCB design data processing device suitable for implementing embodiments of this application. The parametrically driven PCB design data processing device in these embodiments may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, personal digital assistants (PDAs), tablets, and in-vehicle terminals, as well as fixed terminals such as digital TVs and desktop computers. Figure 4 The parameterized-driven PCB design data processing device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0091] like Figure 4As shown, the parameter-driven PCB design data processing device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 1002 or a program loaded from storage device 1003 into random access memory (RAM) 1004. The random access memory 1004 also stores various programs and data required for the operation of the parameter-driven PCB design data processing device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the parametrically driven PCB design data processing equipment to exchange data wirelessly or via wired communication with other devices. Although parametrically driven PCB design data processing equipment with various systems is shown in the figures, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems may be implemented alternatively.

[0092] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0093] The parametrically driven PCB design data processing device provided in this application, employing the parametrically driven PCB design data processing method in the above embodiments, can solve the technical problem of excessive memory resource consumption caused by the inability to generate geometric data on demand. Compared with the prior art, the beneficial effects of the parametrically driven PCB design data processing device provided in this application are the same as those of the parametrically driven PCB design data processing device provided in the above embodiments, and other technical features in this parametrically driven PCB design data processing device are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.

[0094] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0095] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0096] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the parameterized driven PCB design data processing method in the above embodiments.

[0097] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, radio frequency (RF), or any suitable combination thereof.

[0098] The aforementioned computer-readable storage medium may be included in a parametrically driven PCB design data processing device; or it may exist independently and not be assembled into a parametrically driven PCB design data processing device.

[0099] The aforementioned computer-readable storage medium carries one or more programs that, when executed by a parameterized PCB design data processing device, cause the parameterized PCB design data processing device to: receive a PCB design file; create parameterized objects corresponding to each element in the PCB design file according to a pre-established data model; generate geometric data based on the parameterized objects in response to a simulation request, using a unified geometry generation interface defined in the data model and the business type of the simulation request; and release the geometric data in response to a simulation end request.

[0100] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

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

[0102] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0103] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described parameterized PCB design data processing method. This solves the technical problem of excessive memory resource consumption due to the inability to generate geometric data on demand. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the parameterized PCB design data processing method provided in the above embodiments, and will not be repeated here.

[0104] This application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the parameterized PCB design data processing method described above.

[0105] The computer program product provided in this application can solve the technical problem of excessive memory resource consumption caused by the inability to generate geometric data on demand. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the parameterized driven PCB design data processing method provided in the above embodiments, and will not be repeated here.

[0106] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent scope of this application.

Claims

1. A parameter-driven PCB design data processing method, characterized in that, The parameter-driven PCB design data processing method includes: Receive PCB design files; Based on the pre-established data model, create parametric objects corresponding to each element in the PCB design file; In response to a simulation request, geometric data is generated based on the parameterized object using the unified geometry generation interface defined in the data model and the business type of the simulation request. In response to the simulation end request, the geometric data is released.

2. The parameter-driven PCB design data processing method as described in claim 1, characterized in that, The data model defines a layer container class and a parameterized primitive abstract base class. The layer container class is used to define at least one layer, including the layer name, layer type identifier, layer thickness parameter, and parameterized primitives on the layer. The parameterized primitive abstract base class defines virtual functions and parameterized structures for multiple primitive types.

3. The parameter-driven PCB design data processing method as described in claim 1, characterized in that, Prior to the step of generating geometric data based on the parameterized object in response to a simulation request, using the unified geometry generation interface defined in the data model and the business type of the simulation request, the following steps are included: The virtual function is defined as a unified geometry generation interface of the parameterized primitive abstract base class, and the input of the unified geometry generation interface includes a precision parameter; the unified geometry generation interface is used to convert the parameterized data of the parameterized object into geometric data.

4. The parameter-driven PCB design data processing method as described in claim 1, characterized in that, The step of creating parametric objects corresponding to each element in the PCB design file based on a pre-established data model includes: Based on the primitive type of the primitive, the parameterized structure is determined in the parameterized primitive abstract base class of the data model; Determine the geometric attribute parameters of the primitive and write the geometric attribute parameters into the parameterized structure; The layer parameters corresponding to the layer container class of the data model are determined based on the layer to which the graphic element belongs; Based on the written parameterized structure and the corresponding layer parameters, create parameterized objects corresponding to each primitive.

5. The parameter-driven PCB design data processing method as described in claim 1, characterized in that, After the step of creating parametric objects corresponding to each element in the PCB design file based on the pre-established data model, the following steps are included: Obtain the network identifier of the graphic element, and construct a network index based on the network identifier; Based on the network index, primitives with the same network identifier are associated with the primitive type of the parameterized primitive abstract base class corresponding to the data model.

6. The parameter-driven PCB design data processing method as described in claim 1, characterized in that, The step of generating geometric data based on the parameterized object in response to a simulation request, using the unified geometry generation interface defined in the data model and the business type of the simulation request, includes: Determine the generation strategy corresponding to the service type of the simulation request; The target parameterized object corresponding to the simulation request is determined according to the generation strategy; Determine the precision parameters of the unified geometry generation interface; Based on the target parameterized object and the precision parameters, the unified geometry generation interface is invoked to generate geometric data.

7. The parameter-driven PCB design data processing method as described in claim 1, characterized in that, The step of generating geometric data based on the parameterized object in response to a simulation request, using the unified geometry generation interface defined in the data model and the business type of the simulation request, further includes: When the simulation request is a structural and fluid simulation, the current generation strategy is determined to require only the coverage ratio of copper in space; Based on the generation strategy, the parameterized objects corresponding to the structural and fluid simulations are determined to be the pad symbol parameter class in the parameterized primitive abstract base class; Determine the precision parameters of the unified geometry generation interface; Geometric data is generated based on the unified geometry generation interface called according to the pad symbol parameter class and the precision parameter.

8. The parameter-driven PCB design data processing method as described in claim 1, characterized in that, The step of generating geometric data based on the parameterized object in response to a simulation request, using the unified geometry generation interface defined in the data model and the business type of the simulation request, further includes: When the simulation request is mesh partitioning, the current generation strategy is determined to be that only the connected geometric regions of the electrical network are needed. Based on the generation strategy, the target parameterized object corresponding to the mesh partitioning is determined to be an electrical network parameter class; Determine the precision parameters of the unified geometry generation interface; Geometric data is generated based on the unified geometry generation interface invoked according to the electrical network parameter class and the precision parameters.

9. A parameter-driven PCB design data processing device, characterized in that, The parameterized PCB design data processing device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the parameterized PCB design data processing method as described in any one of claims 1 to 8.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, it implements the steps of the parameterized PCB design data processing method as described in any one of claims 1 to 8.

Images