Rule checking method and system for quantum layout design and storage medium
Through the rule adapter plug-in and plug-in model loading mechanism, the inspection rules of quantum layout design are dynamically adapted, which solves the problems of inaccurate rule checking and high cost in traditional methods and realizes efficient and flexible quantum layout design quality control.
Patent Information
- Application Number
- CN202510763357.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-09
- Publication Date
- 2025-09-16
Smart Images
Figure CN120654645A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of quantum chip manufacturing and integrated circuit design, and in particular to a rule checking method, system and storage medium for quantum layout design. Background Art
[0002] In quantum layout design, rule checking is a critical step in ensuring that the design meets manufacturing process requirements and performance standards. Its purpose is to identify and correct potential design issues, such as isolated devices, insufficient connections, device overlap, improper placement of air bridge piers and bridge decks, and inconsistent Josephson junction angles. If these issues are not discovered and addressed promptly, they can lead to quantum chip failures during manufacturing or poor performance during operation.
[0003] Traditional rule checking methods rely mainly on manual review or automated checking tools based on fixed rules. However, facing the complexity and diversity of quantum layout design, these methods have significant drawbacks:
[0004] Quantum layout design involves complex rules and constraints (such as device connectivity, layout optimization, and physical limitations). Traditional methods struggle to comprehensively and accurately cover all of these rules, leading to missed design errors and impacting chip performance and reliability.
[0005] With the development of quantum chip technology, new rules and constraints continue to emerge. Traditional methods require frequent code modifications to adapt, which is costly and inefficient. Summary of the Invention
[0006] The present disclosure provides a rule checking method, system and storage medium for quantum layout design to at least solve the above technical problems existing in the prior art.
[0007] In one aspect, the present disclosure provides a rule checking method for quantum layout design, comprising:
[0008] Based on a target rule check performed on a target quantum layout design, a corresponding rule adapter plug-in is loaded, wherein the rule adapter plug-in includes basic information metadata for describing plug-in information, result metadata for describing a data structure of a check result, and a rule method for executing the rule check; the target rule check includes insufficient device connection check and / or Josephson junction angle check;
[0009] Loading the target quantum layout design and parsing it to obtain layout data;
[0010] Based on the layout data, executing the target rule check to obtain check result data;
[0011] When the target rule check fails, the check result data is output according to the result metadata.
[0012] The step of loading the target quantum layout design includes:
[0013] Creating a rule check object, configuring the identifier of the quantum layout design application and the address of the target quantum layout design in the rule check object;
[0014] Initialize the data interaction channel based on the initialization method included in the rule adapter plug-in;
[0015] Based on the resource loading method included in the rule adapter plug-in, the identifier and the address are obtained from the rule check object, and the target quantum layout design is obtained according to the identifier and the address.
[0016] Wherein, when the target rule check is a check on insufficient device connection, performing the target rule check based on the layout data includes:
[0017] Acquire a coordinate point set of a device to be inspected and a coordinate point set of a line object from the layout data;
[0018] and generating a structural diagram of the device to be inspected according to the coordinate point set of the device to be inspected;
[0019] Acquire the connection points of the device to be inspected from the structural diagram;
[0020] When it is determined that the connection point belongs to the coordinate point set of the connection object, the device to be inspected is fully connected; otherwise, the device to be inspected is not fully connected.
[0021] Wherein, obtaining the connection points of the device to be inspected from the structure diagram includes:
[0022] Classifying the coordinate points of the device to be inspected according to the structural diagram to obtain a set of coordinate points of each connection portion of the device to be inspected;
[0023] The coordinate point set of the connection part is traversed, and the extreme value coordinate point of the corresponding connection part is extracted as the connection point.
[0024] The step of determining that the connection point belongs to a coordinate point set of the line object includes:
[0025] If the first direction coordinate value of the connection point is the same as the first direction coordinate value of any coordinate point in the coordinate set of the connection object, and the difference in the second direction coordinate value is within the set error range, then the connection point is determined to belong to the coordinate point set of the connection object; otherwise, the connection point is determined not to belong to the coordinate point set of the connection object;
[0026] The first direction is the geometric orientation of the connecting portion.
[0027] When the target rule check fails, the inspection result data is output according to the result metadata, including: prompt information for indicating that the connection of the device to be inspected is insufficient, and the coordinates of the connection points that do not belong to the coordinate point set of the connection object.
[0028] Wherein, when the target rule check is the Josephson junction angle check, performing the rule check based on the layout data includes:
[0029] Obtaining Josephson junction angles of all devices to be inspected from the layout data;
[0030] The devices to be inspected are grouped according to the Josephson junction angle, and the Josephson junction angles of the devices to be inspected contained in a group are the same;
[0031] If a group is obtained, it is determined that the Josephson junction angles of the devices to be inspected are consistent;
[0032] If there are multiple groups, it is determined that the Josephson junction angles of the device to be inspected are inconsistent.
[0033] When the target rule check fails, the inspection result data is output according to the result metadata, including: prompt information for characterizing that the Josephson junction angles of the device to be inspected are inconsistent, and the coordinates of the Josephson junctions of each device to be inspected in the group containing the least number of devices to be inspected among the multiple groups.
[0034] A second aspect of the present disclosure further provides a rule checking platform for quantum layout design, comprising:
[0035] A plug-in management module is configured to load a corresponding rule adapter plug-in based on a target rule check performed on a target quantum layout design; the rule adapter plug-in includes basic information metadata for describing plug-in information, result metadata for describing the data structure of the check result, and a rule implementation class for performing the rule check; the target rule check includes insufficient device connection check and / or Josephson junction angle check;
[0036] A rule container data acquisition module is used to load the target quantum layout design and parse it to obtain layout data;
[0037] The rule event engine is driven to drive the rule implementation class to perform the target rule check based on the layout data; when the target rule check fails, the rule implementation class is triggered to encapsulate the inspection result data according to the result metadata and output the encapsulated inspection result data.
[0038] The third aspect of the present disclosure further provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program is used to execute the rule checking method for quantum layout design.
[0039] In the above solution, special inspection logic (such as insufficient device connection and Josephson junction angle inspection) is encapsulated through the rule adapter plug-in, and precise rules are designed for the characteristics of quantum devices, which can avoid the subjectivity of traditional manual inspection and the one-sidedness of fixed rule tools; different inspection types are dynamically adapted through the rule plug-in model loading mechanism. When adding new rules, only new plug-ins need to be developed without code modification, which is low-cost and high-efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] Figure 1 A schematic diagram of a rule checking method for quantum layout design according to an example of the present disclosure is shown;
[0041] Figure 2 A schematic diagram of a target quantum layout design loading method according to an example of the present disclosure is shown;
[0042] Figure 3 A schematic diagram of a target rule checking process according to an example of the present disclosure is shown;
[0043] Figure 4 A schematic diagram of a device structure of an example of the present disclosure is shown;
[0044] Figure 5 A schematic diagram of a target rule checking process of another example of the present disclosure is shown;
[0045] Figure 6 A schematic diagram of the structure of a rule checking platform for quantum layout design according to an example of the present disclosure is shown. DETAILED DESCRIPTION
[0046] In order to make the purposes, features, and advantages of the present invention more obvious and easy to understand, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of the present invention.
[0047] like Figure 1 As shown, the present disclosure provides a rule checking method for quantum layout design, which is applied to a rule checking platform for quantum layout design (hereinafter referred to as the platform), including:
[0048] Operation S101 is to load a corresponding rule adapter plug-in based on a target rule check performed on a target quantum layout design. The rule adapter plug-in includes: basic information for describing plug-in information, result metadata for describing the data structure of the check result, and a rule implementation class for performing the rule check; the target rule check includes: insufficient device connection check and / or Josephson junction angle check.
[0049] To ensure that the quantum layout design complies with the physical properties and manufacturing rules of quantum devices and to prevent chip failures due to design flaws, rule checking is required. Various rule checks can be performed, depending on the needs, such as for isolated devices, insufficient connections, device overlap, improper positioning of air bridge piers and bridge decks, and inconsistent Josephson junction angles. In this disclosure, the rule checks required for the quantum layout design, i.e., the target rule checks, can be determined first. Then, a rule adapter plugin corresponding to the target rule check can be loaded into the platform.
[0050] The rule adapter plug-in is used to encapsulate specific rule checking logic. A plug-in encapsulates at least one target rule checking logic. If there is no corresponding plug-in for the target rule checking, the solution of this disclosure supports dynamic expansion of the target rule checking logic of the existing plug-in, or a new dedicated plug-in can be added.
[0051] Each rule adapter plug-in consists of rule metadata and rule implementation class.
[0052] Rule metadata includes basic information metadata for describing plug-in information and result metadata for describing the data structure of the inspection result.
[0053] Plugin registration, identification, and management can be achieved based on basic information metadata. Basic information metadata can include: a unique identifier (providing a unique identifier for the rule adapter plugin to facilitate identification and management of different plugins and avoid conflicts), a functional description and scope of application (clarifying the plugin's function, such as "detecting insufficient Xmon device connections"), applicable scenarios (such as Xmon quantum device layout design), and version information. Any information that can explain the nature of the plugin can be used as basic information metadata.
[0054] The rule check result can be output in a standardized manner based on the result metadata. When building a plug-in, the content of the result metadata, that is, the data structure of the rule check result, can be configured as needed, and this disclosure does not impose any restrictions on this.
[0055] In addition, the rule metadata can also include layout rule source metadata, which is used to explain the basis for checking the rules, and can include a statement of the rule's authority. Since the purpose of rule checking is to make the layout design comply with the general process requirements of this field and ensure the implementation of industry standards, a statement of the rule's authority is required, such as the referenced industry standards and process specifications.
[0056] The rule implementation class is the core component of the rule adapter plug-in, used to implement specific rule checking logic, such as insufficient device connection checking and Josephson junction angle checking. In this disclosure, the rule implementation class mainly includes rule methods, such as the method for insufficient device connection checking and the method for Josephson junction angle checking. By executing these rule methods, the corresponding rule checks can be implemented.
[0057] Operation S102: Load the target quantum layout design and perform analysis to obtain layout data.
[0058] The target quantum layout design file format can be parsed using a corresponding parser, such as a GDSII parser or a JSON parser. Quantum layouts are used to describe quantum devices (such as Xmons, SQUIDs, and Josephson junctions) and their connections. Therefore, the layout data obtained by parsing the target quantum layout design primarily includes the coordinate data of quantum devices and connection objects (connections between devices).
[0059] Depending on the device, the coordinate data of the device may be a one-dimensional array. For example, for polygonal devices such as pads and SQUIDs, the coordinate points are arranged in a set order as a one-dimensional array (such as [x1, y1, x2, y2, ...], where x1 and y1 indicate the horizontal and vertical coordinates of coordinate point 1). The coordinate data of the device may also be a two-dimensional array. For example, for composite devices such as Xmon and resonant cavities, they are composed of multiple independent polygons. Each polygon requires an independent description of the coordinate points, that is, the coordinate points of each polygon are arranged in order as a one-dimensional array, and these one-dimensional arrays are merged into a two-dimensional array.
[0060] The coordinate data of a line object is also a two-dimensional array. For example, a simple straight line contains two vertices (the starting point and the end point). The coordinates of the starting point [x1, y1] and the end point [x2, y2] are one-dimensional arrays, and the coordinate data of the line [[x1, y1], [x2, y2]] is a two-dimensional array. For another example, a broken line contains multiple vertices: the starting point [x1, y1], the inflection point [x2, y2], and the end point [x3, y3], which are one-dimensional arrays, and the coordinate data of the broken line [[x1, y1], [x2, y2], [x3, y3]] is a two-dimensional array. In the present disclosure, the coordinate data of the connection object is converted from a two-dimensional array to a one-dimensional array, for example, the two-dimensional array [[x1, y1], [x2, y2], [x3, y3]] is converted to a one-dimensional array [x1, y1, x2, y2, x3, y3], so that when the rule check is subsequently performed, the coordinate points can be quickly traversed and efficiently queried.
[0061] The parsed layout data is used by the rule method of the rule implementation class to call.
[0062] Operation S103 : performing target rule check based on the layout data to obtain check result data.
[0063] After obtaining the layout data, you can execute the rule method in the rule implementation class to perform the target rule check and obtain the check result data. The specific rule check process will be explained in the following examples.
[0064] In operation S104 , when the target rule check fails, the check result data is output according to the result metadata.
[0065] When the target rule check fails, the check result data is encapsulated according to the result metadata and the encapsulated check result data is output.
[0066] In the above solution, special inspection logic (such as insufficient device connection and Josephson junction angle inspection) is encapsulated through the rule adapter plug-in, and precise rules are designed for the characteristics of quantum devices. This can avoid the subjectivity of traditional manual inspection and the one-sidedness of fixed rule tools; different inspection types can be dynamically adapted through the rule plug-in model loading mechanism. When adding new rules, only new plug-ins need to be developed without code modification, which is low-cost and high-efficiency.
[0067] In one example, if Figure 2 As shown, the process of loading the target quantum layout design includes:
[0068] Operation S201: Create a rule check object, and configure the identifier of the quantum layout design application and the address of the target quantum layout design in the rule check object.
[0069] The rule check object is the core data structure in the platform that carries the target quantum layout design and serves as the entry point for triggering the target rule check process. It forms a complete rule check task description by integrating the layout design software identifier, the target quantum layout design address, and the selected rule adapter plug-in.
[0070] Configuring the quantum layout design application identifier in the rule-checking object ensures that the platform correctly identifies the quantum layout design application corresponding to the target quantum layout design. Because different quantum layout design applications may have different data storage structures, coordinate systems, and device models, the identifier is required to match the corresponding initialization method (operation S202) and resource loading method (operation S203).
[0071] The address of the target quantum layout design is used by the resource loading method to read the target quantum layout design through this address, ensuring the accuracy and traceability of the data acquisition. In this disclosure, the address of the target quantum layout design can point to the platform database or an external database, and this disclosure does not impose any restrictions on this.
[0072] Operation S202: Initialize the data interaction channel based on the initialization method included in the rule adapter plug-in.
[0073] In this example, the rule implementation class also includes an initialization method, whose core function is to establish a data exchange channel between the platform and the quantum layout design application, ensuring that the platform can read, parse, and process the target quantum layout design. This method is the foundation of the rule checking process and directly determines the feasibility and stability of data exchange.
[0074] After creating the rule check object, the platform needs to call the initialization method before loading the target quantum layout design. In this disclosure, the initialization method supports two modes: default channel and custom channel:
[0075] Default channel: Check the address of the target quantum layout design in the object according to the rules. If it is determined that the target quantum layout design is stored locally on the platform (such as the platform's built-in database or local file system), a data interaction channel is established between the platform and the quantum layout design application.
[0076] Custom channel: Check the address of the target quantum layout design in the object according to the rules. When it is determined that the target quantum layout design is stored in an external platform or third-party design software (such as Cadence, L-Edit, etc.), a data interaction channel is established between the platform and the external platform or third-party design software.
[0077] Operation S203 : Based on the resource loading method included in the rule adapter plug-in, obtain the identifier and the address from the rule check object, and obtain the target quantum layout design according to the identifier and the address.
[0078] In this example, the above rule implementation class may also include a resource loading method, whose core function is to load the target quantum layout design.
[0079] After the data interaction channel is initialized, the platform can call the resource loading method that matches the quantum layout design application, and accurately load the target quantum layout design according to the quantum layout design application identifier and target quantum layout design address in the inspection rules.
[0080] Through the loading process of the target quantum layout design, seamless integration and efficient interaction between the platform and quantum layout design applications can be achieved.
[0081] After the target quantum layout design is loaded, it can be parsed, as described in the above operation S102, which will not be repeated here. Based on the parsed layout data, a target rule check can be performed.
[0082] In one example, if the target rule check is insufficient device connectivity check, the check process is as follows: Figure 3 Shown include:
[0083] Operation S301: Acquire a coordinate point set of a device to be inspected and a coordinate point set of a line object from the layout data.
[0084] There are many devices that can be used to check for insufficient device connections, such as Xmon devices, resonant cavities, and pads. This example uses the Xmon device as an example.
[0085] Get the coordinate point set (two-dimensional array) of each Xmon device from the parsed layout data. Figure 4 The figure shows the structure of an Xmon device. The Xmon device mainly includes the device body and connection parts (such as control lines). The two-dimensional array of the Xmon device is composed of multiple one-dimensional arrays. Some of the one-dimensional arrays contain the coordinate points of the Xmon device body, while some of the one-dimensional arrays contain the coordinate points of the connection parts. Each connection part corresponds to a one-dimensional array. For example, if the connection part of the Xmon device is a control line, each control line is a connection part, corresponding to a one-dimensional array.
[0086] In addition, it is necessary to obtain the coordinate point set of all connection objects from the parsed layout data. As described in operation S102, the coordinate data of each connection object has been converted into a one-dimensional array, and the coordinate point set of the connection object contains multiple one-dimensional arrays, each one-dimensional array corresponding to a connection.
[0087] Operation S302 : generating a structural diagram of the device to be inspected according to the coordinate point set of the device to be inspected.
[0088] According to the coordinate point set of the Xmon device, draw a coordinate structure diagram, such as Figure 4 As shown, the geometric shape and connection position of each part of the device can be clearly determined based on the structural diagram. The geometric direction of the connection can also be determined, which helps to determine the connection points described below.
[0089] Operation S303: Acquire connection points of the device to be inspected from the structure diagram.
[0090] The coordinate points of the device to be inspected are classified according to the structural diagram to obtain a coordinate point set of each connection part of the device to be inspected; the coordinate point set of the connection part is traversed to extract the extreme value coordinate point of the corresponding connection part as the connection point.
[0091] Because the device coordinate point set obtained from the parsed layout data contains the coordinate point set of each part of the device and is discrete data, it lacks semantic annotations of the function or structure of each part of the device (such as "connection part" and "main body"). Based on the coordinate point set, it is difficult to distinguish which points belong to the device's connection part and which belong to the main body, which may lead to misjudgment of connection adequacy. Therefore, the structure diagram can assign functional semantics to the group points to accurately determine which coordinate points belong to the device's connection part and which belong to the main body.
[0092] In addition, the device orientation, the geometric direction of the connection, etc. can be determined based on the structure diagram, so that the connection points on the connection can be accurately and quickly determined based on the coordinate set of the connection. Usually, the orientation of the Xmon device in the quantum layout design is consistent and fixed, and the number, position and direction of the connection parts are also fixed. For example Figure 4 The top side of the Xmon device shown is the connection portion (four control lines). The coordinate points corresponding to the four control lines (a one-dimensional array) are labeled 0 / 1 / 3 / 4 in the Xmon device's two-dimensional array. The four control lines run vertically and extend upward. Thus, by traversing the one-dimensional array labeled 0 / 1 / 3 / 4, the coordinate point with the largest y value is found, which is the connection point of the Xmon device. The number of identified connection points may be one or more.
[0093] The coordinate point with the largest y value here is only an example, and the specific value can be determined according to the structure diagram of the device. For example, if the geometric direction of the connection part is horizontal and extends to the right, the coordinate point with the largest x value is the connection point.
[0094] Operation S304 : When it is determined that the connection point belongs to the coordinate point set of the line object, the device to be inspected is fully connected; otherwise, the device to be inspected is not fully connected.
[0095] If the first direction coordinate value of the connection point is the same as the first direction coordinate value of any coordinate point in the coordinate set of the connection object, and the difference in the second direction coordinate value is within the set error range, then it is determined that the connection point belongs to the coordinate point set of the connection object; otherwise, it is determined that the connection point does not belong to the coordinate point set of the connection object; the first direction is the geometric direction of the connection part.
[0096] For example, the coordinates of connection point 1 of Xmon device 1 are (50, 250), the coordinates of connection point 2 of Xmon device 2 are (190, 200), and the coordinate point set of the connection object is [100, 200, 200, 200]. If there is no coordinate point with y=250 in the coordinate point set of the connection object, then connection point 1 does not belong to the coordinate point set of the connection object, that is, Xmon device 1 is not fully connected; if there are coordinate points (100, 200) and (200, 200) with y=200 in the coordinate point set of the connection object, and the difference between the x coordinate values of connection point 2 (190) and (200, 200) is 10 microns, which is within the preset reasonable error range, then connection point 2 belongs to the coordinate point set of the connection object, that is, Xmon device 2 is fully connected.
[0097] In one example, when a target rule check fails, check result data is output based on result metadata. In this disclosure, the result metadata includes at least prompt information and coordinate point information. The prompt information is used to indicate that the target rule check fails, and the coordinate point information is the coordinates of the key coordinate points based on which the target rule check fails.
[0098] For example, the inspection result data output for Xmon device 1 includes: prompt information for indicating that the device to be inspected (Xmon device 1) is not sufficiently connected, and the coordinates of the connection point that does not belong to the coordinate point set of the connection object (ie (50, 250)).
[0099] In one example, if the target rule check is the Josephson junction angle check, the check process is as follows: Figure 5 Shown include:
[0100] Operation S501 : Acquire the Josephson junction angles of all devices to be inspected from the layout data.
[0101] By analyzing the target quantum layout design, the coordinate data and property information of devices containing Josephson junctions (such as SQUID devices) can also be obtained.
[0102] Taking the SQUID device as an example, its attribute information may include the angle parameter of the Josephson junction. Then, the Josephson junction angles of all devices to be inspected can be obtained from the layout data.
[0103] Operation S502 : Group the devices to be inspected according to their Josephson junction angles. The devices to be inspected in a group have the same Josephson junction angle.
[0104] If multiple devices to be inspected have Josephson junction angles, the Josephson junction angle is checked independently for each device to be inspected. Taking SQUID devices as an example, a mapping relationship between angles and device sets is constructed. In one example, this can be achieved using a hash table: all SQUID devices to be inspected are traversed, the angle value of each device is used as a key, and the device object is added to the list of corresponding keys. That is, the key of a mapping relationship (group) is the angle, and the value is a list of SQUID devices with the same angle.
[0105] Operation S503: If a group is obtained, it is determined that the Josephson junction angles of the devices to be inspected are consistent.
[0106] After grouping, you can check the number of groups. If the number is 1, the devices have the same Josephson junction angle. For example, if all SQUID devices have an angle of 0°, then after grouping, there will be only one group {"0":[squid1,squid2,...]}, which indicates that the angles are consistent and meet the design rules. This means that the target rule check has passed.
[0107] Operation S504: If there are multiple groups, determine that the Josephson junction angles of the device to be inspected are inconsistent.
[0108] After grouping, the number of groups can be checked. If there are multiple groups, such as 2, it indicates that there are two different Josephson junction angles. For example, if the group contains 0° (10 SQUID devices) and 90° (2 SQUID devices), the Josephson junction angles are considered inconsistent, and the target rule check fails.
[0109] If the Josephson junction angle inspection fails, in one example, inspection result data can be output, including: prompt information indicating that the Josephson junction angles of the device to be inspected are inconsistent, and the coordinates of the Josephson junctions of each device to be inspected in the group containing the fewest devices to be inspected among the multiple groups. For example, if the group contains 0° (10 SQUID devices) and 90° (2 SQUID devices), a prompt indicating inconsistent Josephson junction angles can be output, and the coordinate data of the two SQUID devices at 90° can be output. In this way, based on the inspection result data, the two abnormal SQUID devices can be located using the coordinate data, and the Josephson junction angles can be adjusted. After the adjustment, steps S501-504 are re-executed until only one group is obtained after grouping.
[0110] Through the above scheme, the present disclosure achieves automated inspection of quantum layout designs. By designing precise rules for quantum device characteristics (such as the aforementioned insufficient device connection and Josephson junction angle inspection), the subjectivity of traditional manual inspection and the one-sidedness of fixed rule tools can be avoided. In addition, the rule plug-in model loading mechanism dynamically adapts to different inspection types. When adding new rules, only new plug-ins need to be developed, without modifying the code. The rule checking method disclosed in the present disclosure not only improves the accuracy and efficiency of rule checking, but also enhances its flexibility and scalability, providing strong support for quality control and optimization of quantum layout design.
[0111] The above rule checking method is applied to the rule checking platform (hereinafter referred to as the platform) for quantum layout design. In one example of the present disclosure, the platform has functions such as rule adapter plug-in loading, rule container data collection and event driving. Figure 6 As shown, the present disclosure provides a rule checking platform for quantum layout design, comprising:
[0112] The plug-in management module 601 implements the rule adapter plug-in loading function. Specifically, it is used to load the corresponding rule adapter plug-in based on the target rule check of the target quantum layout design. The rule adapter plug-in includes basic information metadata describing the plug-in information, result metadata describing the data structure of the check result, and a rule implementation class for performing the rule check. The target rule check includes insufficient device connection check and / or Josephson junction angle check. The specific implementation of this module is described in operation S101 and will not be repeated here.
[0113] The rule container data acquisition module 602 can realize the rule container data acquisition function and provide basic data support for subsequent rule checking. Specifically, it is used to load the target quantum layout design and parse it to obtain layout data.
[0114] The specific process of loading the target quantum layout design by the rule container data acquisition module 602 is as described in operations S201-S203 and will not be repeated here. The parsed layout data can be stored in the rule adapter plug-in. In one example of the present disclosure, the rule adapter plug-in can also define an object model to store the layout data, specifically including:
[0115] Device models that can store the coordinate data and attribute data of various devices, as well as connection models used to store the coordinate data of all connections in the quantum map. Among them, device models, for example:
[0116] Xmon model: used to store the coordinate data of the Xmon device;
[0117] SQUID model: used to store the coordinate data and property data (Josephson junction angle) of the SQUID device.
[0118] The coordinate data structure defined in the above model can be a two-dimensional array or a one-dimensional array, depending on the needs. For example, the coordinate data of Xmon and connection objects are two-dimensional arrays. If the data structure defined in the model is a one-dimensional array, it is necessary to convert the two-dimensional array into a one-dimensional array before storage according to the model requirements.
[0119] The coordinate data of a line object is a two-dimensional array. For example, a simple straight line contains two vertices (the start and end points). The coordinates of the start point [x1, y1] and the end point [x2, y2] are each one-dimensional arrays. Therefore, the coordinate data of the line [[x1, y1], [x2, y2]] is a two-dimensional array. For another example, a polyline contains multiple vertices: the start point [x1, y1], the inflection point [x2, y2], and the end point [x3, y3] are each one-dimensional arrays. The coordinate data of the polyline [[x1, y1], [x2, y2], [x3, y3]] is a two-dimensional array. Converting the coordinate data of a line object from a two-dimensional array to a one-dimensional array, for example, converting the two-dimensional array [[x1, y1], [x2, y2], [x3, y3]] to the one-dimensional array [x1, y1, x2, y2, x3, y3], allows for fast traversal and efficient querying of coordinate points during subsequent rule checking.
[0120] Xmon is a composite device, and its coordinate data is a two-dimensional array consisting of multiple one-dimensional arrays. For example: [[x01,y01,x02,y02],[x11,y11],[x21,y21]], where the coordinates of the main body are [x01,y01,x02,y02] (a one-dimensional array with subscript 0), the coordinates of connection 1 are [x11,y11] (a one-dimensional array with subscript 1), and the coordinates of connection 2 are [x21,y21] (a one-dimensional array with subscript 2). The two-dimensional array [[x01,y01,x02,y02], [x11,y11], [x21,y21]] is converted to the one-dimensional array [x01,y01,x02,y02,x11,y11,x21,y21].
[0121] That is, the coordinate points in the two-dimensional array can be arranged as needed and converted into a one-dimensional array.
[0122] The rule event engine driver 603 can realize the event-driven function, specifically: it is used to drive the rule implementation class to perform target rule checks based on layout data; when the target rule check fails, the rule implementation class is triggered to encapsulate the inspection result data according to the result metadata and output the encapsulated inspection result data.
[0123] Specifically, the rule event engine driver 603 can use a publish-subscribe mechanism to listen for layout data loading completion events from the rule container data acquisition module 602, or for externally input rule check events, thereby invoking the rule implementation class in the rule adapter plug-in to perform target rule checks. The specific check process is described in operations S301-S304 and S501-S504 and will not be repeated here. During the check process, the layout data stored in the object model is passed to the rule implementation class for use by the check logic.
[0124] The rule event engine driver 603 can use a publish-subscribe mechanism to listen for target rule check failure events, thereby triggering the rule implementation class to encapsulate the inspection result data according to the result metadata; after the rule implementation class encapsulates the result, it publishes the encapsulated inspection result data to a specified storage unit (e.g., a rule data container); the rule event engine driver 603 listens to the inspection result data of the storage unit, thereby triggering a display event, which pushes the inspection result data to the platform front-end interface for display. In addition, the rule event engine driver 603 can also flexibly expand rule events, such as publishing abnormal results directly to other clients for display, or storing abnormal data, providing interfaces for other platforms to call, etc. This allows the inspection results to be presented to relevant personnel in a timely and accurate manner, making it convenient for them to quickly take measures to adjust and optimize.
[0125] Illustratively, the present disclosure further provides an electronic device, including:
[0126] processor;
[0127] a memory for storing instructions executable by the processor;
[0128] The processor is configured to read the executable instructions from the memory and execute the instructions to implement the above-mentioned rule checking method for quantum layout design.
[0129] Illustratively, the present invention further provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program is used to execute the above-mentioned rule checking method for quantum layout design.
[0130] In addition to the above-mentioned methods and devices, an embodiment of the present application may also be a computer program product, which includes computer program instructions, which, when executed by a processor, enable the processor to execute the steps of the method according to various embodiments of the present application described in the above-mentioned "Exemplary Method" section of this specification.
[0131] The computer program product may be written in any combination of one or more programming languages to implement the program code for performing the operations of the embodiments of the present application, including object-oriented programming languages such as Java, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.
[0132] In addition, an embodiment of the present application may also be a computer-readable storage medium having computer program instructions stored thereon, which, when executed by a processor, enable the processor to execute the steps of the method according to various embodiments of the present application described in the above "Exemplary Method" section of this specification.
[0133] The computer-readable storage medium can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can, for example, include but is not limited to a system, device or component of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.
[0134] The basic principles of the present application have been described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, and effects mentioned in this application are merely illustrative and not restrictive, and it should not be assumed that these advantages, strengths, and effects are required of each embodiment of this application. In addition, the specific details disclosed above are merely illustrative and facilitating understanding, and are not restrictive. The above details do not limit this application to necessarily being implemented using the above specific details.
[0135] The block diagrams of the devices, devices, equipment, and systems involved in this application are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As will be appreciated by those skilled in the art, these devices, devices, equipment, and systems can be connected, arranged, or configured in any manner. Words such as "include," "comprise," "have," and the like are open-ended words, meaning "including but not limited to," and can be used interchangeably therewith. The words "or" and "and" used herein refer to the words "and / or" and can be used interchangeably therewith, unless the context clearly indicates otherwise. The word "such as" used herein refers to the phrase "such as but not limited to," and can be used interchangeably therewith.
[0136] It should also be noted that in the apparatus, device, and method of the present application, each component or each step can be decomposed and / or recombined, and such decomposition and / or recombination should be regarded as equivalent solutions of the present application.
[0137] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present application. Therefore, the present application is not intended to be limited to the aspects shown herein, but rather to be accorded the widest scope consistent with the principles and novel features disclosed herein.
[0138] The above description has been provided for the purpose of illustration and description. Furthermore, this description is not intended to limit the embodiments of the present application to the forms disclosed herein. Although a number of example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations thereof.
Claims
1. A rule checking method for quantum layout design, characterized in that: include: Based on a target rule check performed on a target quantum layout design, a corresponding rule adapter plug-in is loaded, wherein the rule adapter plug-in includes basic information metadata for describing plug-in information, result metadata for describing a data structure of a check result, and a rule method for executing the rule check; the target rule check includes insufficient device connection check and / or Josephson junction angle check; Loading the target quantum layout design and parsing it to obtain layout data; Based on the layout data, executing the target rule check to obtain check result data; When the target rule check fails, the check result data is output according to the result metadata.
2. The method according to claim 1, characterized in that The loading of the target quantum layout design includes: Creating a rule check object, configuring the identifier of the quantum layout design application and the address of the target quantum layout design in the rule check object; Initialize the data interaction channel based on the initialization method included in the rule adapter plug-in; Based on the resource loading method included in the rule adapter plug-in, the identifier and the address are obtained from the rule check object, and the target quantum layout design is obtained according to the identifier and the address.
3. The method according to claim 1, characterized in that When the target rule check is a check on insufficient device connection, performing the target rule check based on the layout data includes: Acquire a coordinate point set of a device to be inspected and a coordinate point set of a line object from the layout data; and generating a structural diagram of the device to be inspected according to the coordinate point set of the device to be inspected; Acquire the connection points of the device to be inspected from the structural diagram; When it is determined that the connection point belongs to the coordinate point set of the connection object, the device to be inspected is fully connected; otherwise, the device to be inspected is not fully connected.
4. The method according to claim 3, characterized in that The obtaining of the connection points of the device to be inspected from the structure diagram includes: Classifying the coordinate points of the device to be inspected according to the structural diagram to obtain a set of coordinate points of each connection portion of the device to be inspected; The coordinate point set of the connection part is traversed, and the extreme value coordinate point of the corresponding connection part is extracted as the connection point.
5. The method according to claim 4, characterized in that Determining that the connection point belongs to the coordinate point set of the line object includes: If the first direction coordinate value of the connection point is the same as the first direction coordinate value of any coordinate point in the coordinate set of the connection object, and the difference in the second direction coordinate value is within the set error range, then the connection point is determined to belong to the coordinate point set of the connection object; otherwise, the connection point is determined not to belong to the coordinate point set of the connection object; The first direction is the geometric orientation of the connecting portion.
6. The method according to any one of claims 3 to 5, characterized in that: When the target rule check fails, the inspection result data is output according to the result metadata, including: prompt information for indicating that the connection of the device to be inspected is insufficient, and the coordinates of the connection points that do not belong to the coordinate point set of the connection object.
7. The method according to claim 1, characterized in that When the target rule check is the Josephson junction angle check, performing the rule check based on the layout data includes: Obtaining Josephson junction angles of all devices to be inspected from the layout data; The devices to be inspected are grouped according to the Josephson junction angle, and the Josephson junction angles of the devices to be inspected contained in a group are the same; If a group is obtained, it is determined that the Josephson junction angles of the devices to be inspected are consistent; If there are multiple groups, it is determined that the Josephson junction angles of the device to be inspected are inconsistent.
8. The method according to claim 6, characterized in that When the target rule check fails, the inspection result data is output according to the result metadata, including: prompt information for characterizing that the Josephson junction angles of the device to be inspected are inconsistent, and the coordinates of the Josephson junctions of each device to be inspected in the group containing the least number of devices to be inspected among the multiple groups.
9. A rule checking platform for quantum layout design, characterized in that: include: A plug-in management module is used to load the corresponding rule adapter plug-in according to the target rule check of the target quantum layout design; The rule adapter plug-in includes: basic information metadata for describing plug-in information, result metadata for describing the data structure of the inspection result, and a rule implementation class for performing rule inspection; the target rule inspection includes: insufficient device connection inspection and / or Josephson junction angle inspection; A rule container data acquisition module is used to load the target quantum layout design and parse it to obtain layout data; The rule event engine is driven to drive the rule implementation class to perform the target rule check based on the layout data; when the target rule check fails, the rule implementation class is triggered to encapsulate the inspection result data according to the result metadata and output the encapsulated inspection result data.
10. A computer-readable storage medium, characterized in that The storage medium stores a computer program, and the computer program is used to execute the rule checking method for quantum layout design according to any one of claims 1 to 8.