A layout design method and device, electronic equipment and readable storage medium

Abstract

The application discloses a layout design method and device, electronic equipment and readable storage medium, and relates to the technical field of chips. The layout design method comprises the following steps: obtaining a quantum device construction list and a quantum device connection list; instantiating each type of quantum device model based on the quantum device construction list; constructing each quantum device corresponding to the quantum device construction list based on the instantiated quantum device model; determining the start anchor point coordinates and the end anchor point coordinates corresponding to each connection relationship in the quantum device connection list based on the quantum device connection list, the quantum device construction list, a connection model and a device anchor point rule; the device anchor point rule comprises a device static anchor point rule and a dynamic anchor point calculation script; and generating a connection path for each quantum device based on the start anchor point coordinates and the end anchor point coordinates corresponding to each connection relationship, so as to obtain a quantum chip layout of the quantum device.

Description

Technical Field

[0001] This application relates to the field of chip technology, and in particular to a layout design method, apparatus, electronic device and readable storage medium. Background Technology

[0002] Currently, the layout design of quantum chips mainly relies on traditional electronic design automation (EDA) tools. While these tools perform well in classical integrated circuit design, they have some shortcomings in quantum chip design. First, some quantum devices have unique physical properties and structures, such as superconducting qubits, resonant cavities, and Josephson junctions. The modeling and design of these devices require specialized tools and methods, and traditional EDA tools lack specific support for these quantum devices, failing to meet the special needs of quantum chip design. Second, the layout design of quantum chips requires handling a large number of devices and complex layouts. Traditional EDA tools are often inefficient in handling these complex designs, making it difficult to meet the high-efficiency requirements of quantum chip design. Summary of the Invention

[0003] In view of the above, embodiments of this application provide a layout design method, apparatus, electronic device, and readable storage medium.

[0004] According to a first aspect of this application, embodiments of this application provide a layout design method, including:

[0005] Obtain the quantum device construction list and the quantum device connection list;

[0006] Based on the quantum device construction list, predefined quantum device models of various types are instantiated. The quantum device models include device model classes and device model tables.

[0007] Based on the instantiated quantum device models, construct each quantum device corresponding to the quantum device construction list;

[0008] Based on the quantum device connection list, quantum device construction list, predefined connection models, and predefined device anchor point rules, the starting and ending anchor point coordinates corresponding to each connection relationship in the quantum device connection list are determined. The device anchor point rules include static anchor point rules and dynamic anchor point calculation scripts. The static anchor point rules include the connection anchor points in each quantum device. The dynamic anchor point calculation script is used to calculate the offset of the connection anchor point coordinates of the quantum devices based on the quantum device attribute data in the quantum device construction list. Based on the offset of the connection anchor point coordinates of the quantum devices, the starting and ending anchor point coordinates corresponding to each connection relationship are determined.

[0009] Based on the starting and ending anchor coordinates of each connection, the connection paths of each constructed quantum device are generated to obtain the quantum chip layout of the quantum device.

[0010] Optionally, based on the quantum device connection list, the quantum device construction list, the predefined connection model, and the predefined device anchor point rules, the starting anchor point coordinates and ending anchor point coordinates corresponding to each connection relationship in the quantum device connection list are determined, including:

[0011] Based on the quantum device connection list and the predefined connection model, the starting quantum device and the ending quantum device corresponding to each connection relationship in the quantum device connection list are determined.

[0012] Based on the starting quantum device, ending quantum device, quantum device construction list, and device static anchor point rules in the device anchor point rules, the first initial anchor point coordinates corresponding to each starting quantum device and the second initial anchor point coordinates corresponding to each ending quantum device are determined.

[0013] Based on the dynamic anchor point calculation script and the quantum device attribute data in the quantum device construction list, the anchor point coordinate offset corresponding to each starting quantum device and the anchor point coordinate offset corresponding to each ending quantum device are calculated.

[0014] Based on the anchor point coordinate offsets corresponding to each starting quantum device and each ending quantum device, the first initial anchor point coordinates corresponding to each starting quantum device and the second initial anchor point coordinates corresponding to each ending quantum device are adjusted to obtain the starting anchor point coordinates and ending anchor point coordinates corresponding to each connection relationship.

[0015] Optionally, based on the starting quantum device, ending quantum device, quantum device construction list, and static anchor point rules in the device anchor point rules corresponding to each connection relationship, the first initial anchor point coordinates corresponding to each starting quantum device and the second initial anchor point coordinates corresponding to each ending quantum device are determined, including:

[0016] Based on the starting quantum device, ending quantum device and device static anchor point rule in the device anchor point rule corresponding to each connection relationship, determine the connection anchor point corresponding to each starting quantum device and the connection anchor point corresponding to each ending quantum device.

[0017] Based on the connection anchor points corresponding to each starting quantum device and each ending quantum device, as well as the quantum device construction list, the coordinates of the first initial anchor point corresponding to each starting quantum device and the coordinates of the second initial anchor point corresponding to each ending quantum device are determined.

[0018] Optionally, the quantum device model types include: pad device model, superconducting quantum bit device model, resonant cavity device model, air bridge device model, Josephson junction device model, and general device model.

[0019] Optionally, the device model class defines the quantum device identifier, quantum device parameter attributes, the layer where the quantum device is located, and the quantum device coordinates; the device model table defines the quantum device identifier field, multiple parameter fields, layer field, and coordinate field.

[0020] Optionally, based on the starting and ending anchor coordinates corresponding to each connection relationship, connection paths are generated for each constructed quantum device, including:

[0021] Based on the starting and ending anchor coordinates of each connection relationship, a path planning strategy to avoid obstacles is invoked to generate connection paths for each connection relationship among the constructed quantum devices.

[0022] Alternatively, the layout design method also includes:

[0023] Output the quantum chip layout in JSON data format.

[0024] Alternatively, the layout design method also includes:

[0025] Based on predefined layout design models and device model classes, the quantum chip layout in JSON data format is parsed to obtain the coordinate data and layer data of each quantum device;

[0026] Based on the coordinate data and layer data of each quantum device, as well as the data conversion rules, the quantum chip layout in JSON data format is converted into a quantum chip layout in GDS data format.

[0027] Alternatively, the layout design method also includes:

[0028] The target quantum chip layout in GDS data format is obtained. The version of the target quantum chip layout in GDS data format is different from that of the quantum chip layout.

[0029] Extracting the geometric features of the GDS polygon in the target quantum chip layout in GDS data format;

[0030] Based on the polygonal geometric features of GDS, the target quantum chip layout in GDS data format is converted into a target quantum chip layout in JSON data format corresponding to the version of the quantum chip layout.

[0031] Optionally, based on the polygonal geometric features of GDS, the target quantum chip layout in GDS data format is converted into a target quantum chip layout in JSON data format corresponding to the version of the quantum chip layout, including:

[0032] Encode the geometric features of GDS polygons into hash values;

[0033] The model is searched in the model library based on the hash value to determine the combined device model corresponding to the hash value; the combined device model is a combined device model in JSON data format corresponding to the version of the quantum chip layout.

[0034] Based on the combined device model, a target quantum chip layout in JSON data format is generated.

[0035] According to a second aspect of this application, embodiments of this application provide a layout design apparatus, including:

[0036] The acquisition module is used to obtain the quantum device construction list and the quantum device connection list;

[0037] The instantiation module is used to instantiate predefined quantum device models of various types based on the quantum device building manifest. The quantum device models include device model classes and device model tables.

[0038] The building module is used to construct each quantum device corresponding to the quantum device building list based on the instantiated quantum device models;

[0039] The determination module is used to determine the starting and ending anchor coordinates of each connection in the quantum device connection list based on the quantum device connection list, the quantum device construction list, the predefined connection model, and the predefined device anchor rules. The device anchor rules include static anchor rules and dynamic anchor calculation scripts. The static anchor rules include the connection anchors in each quantum device. The dynamic anchor calculation script is used to calculate the offset of the connection anchor coordinates of the quantum devices based on the quantum device attribute data in the quantum device construction list. Based on the offset of the connection anchor coordinates of the quantum devices, the starting and ending anchor coordinates of each connection are determined.

[0040] The generation module is used to generate connection paths for each constructed quantum device based on the starting anchor coordinates and ending anchor coordinates corresponding to each connection relationship, thereby obtaining the quantum chip layout of the quantum device.

[0041] Optionally, the determination module is used to determine the starting quantum device and the ending quantum device corresponding to each connection relationship in the quantum device connection list based on the quantum device connection list and the predefined connection model;

[0042] Based on the starting quantum device, ending quantum device, quantum device construction list, and device static anchor point rules in the device anchor point rules, the first initial anchor point coordinates corresponding to each starting quantum device and the second initial anchor point coordinates corresponding to each ending quantum device are determined.

[0043] Based on the dynamic anchor point calculation script and the quantum device attribute data in the quantum device construction list, the anchor point coordinate offset corresponding to each starting quantum device and the anchor point coordinate offset corresponding to each ending quantum device are calculated.

[0044] Based on the anchor point coordinate offsets corresponding to each starting quantum device and each ending quantum device, the first initial anchor point coordinates corresponding to each starting quantum device and the second initial anchor point coordinates corresponding to each ending quantum device are adjusted to obtain the starting anchor point coordinates and ending anchor point coordinates corresponding to each connection relationship.

[0045] Optionally, the determining module is used to determine the connection anchor point corresponding to each starting quantum device and the connection anchor point corresponding to each ending quantum device based on the starting quantum device, the ending quantum device corresponding to each connection relationship, and the device static anchor point rule in the device anchor point rule.

[0046] Based on the connection anchor points corresponding to each starting quantum device and each ending quantum device, as well as the quantum device construction list, the coordinates of the first initial anchor point corresponding to each starting quantum device and the coordinates of the second initial anchor point corresponding to each ending quantum device are determined.

[0047] Optionally, the quantum device model types include: pad device model, superconducting quantum bit device model, resonant cavity device model, air bridge device model, Josephson junction device model, and general device model.

[0048] Optionally, the device model class defines the quantum device identifier, quantum device parameter attributes, the layer where the quantum device is located, and the quantum device coordinates; the device model table defines the quantum device identifier field, multiple parameter fields, layer field, and coordinate field.

[0049] Optionally, the generation module is used to call a path planning strategy to avoid obstacles based on the starting anchor coordinates and ending anchor coordinates corresponding to each connection relationship, so as to generate connection paths for each quantum device.

[0050] Optionally, the layout design device also includes:

[0051] The output module is used to output the quantum chip layout in JSON data format.

[0052] According to a third aspect of this application, embodiments of this application provide an electronic device, including:

[0053] 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, the instructions being executed by the at least one processor to cause the at least one processor to perform a layout design method as described in the first aspect or any embodiment of the first aspect.

[0054] According to a fourth aspect of this application, embodiments of this application provide a computer-readable storage medium storing computer instructions for causing a computer to perform a layout design method as described in the first aspect or any embodiment of the first aspect.

[0055] According to a fifth aspect of this application, an embodiment of this application provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement the layout design method in the first aspect or any embodiment of the first aspect.

[0056] The layout design method, apparatus, electronic device, and readable storage medium provided in this application achieve standardized and regulated management of quantum devices by defining various quantum device models. During the layout design process, these predefined quantum device models can be directly instantiated and combined, avoiding the tedious process of designing each quantum device from scratch, significantly shortening the layout design cycle and improving design efficiency. Furthermore, with the help of predefined connection models and predefined device anchor point rules, the starting and ending anchor point coordinates of the quantum devices to be connected can be accurately determined based on the actual attribute data of the quantum devices, and reasonable connection paths can be generated. This not only reduces the complexity and error rate of manual operations but also further enables the connections to be precisely connected to the specified positions of the devices according to actual design requirements, avoiding connection deviations or incorrect connections, and further improving the accuracy and reliability of the layout design.

[0057] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0058] Figure 1 This is a flowchart illustrating a layout design method according to an embodiment of this application;

[0059] Figure 2 This is a diagram illustrating the anchor points for quantum device connections in the static anchor point rules of this application.

[0060] Figure 3 This is a schematic diagram of the pad structure in an embodiment of this application;

[0061] Figure 4 This is a schematic diagram of the Xmon device structure in the embodiments of this application;

[0062] Figure 5 This is a schematic diagram of a data converter in an embodiment of this application;

[0063] Figure 6 This is a schematic diagram of the structure of a layout design device according to an embodiment of this application;

[0064] Figure 7 This is a schematic diagram of the hardware structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0065] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0066] This application provides a layout design method, such as... Figure 1 As shown, it includes:

[0067] S101, obtain the quantum device construction list and the quantum device connection list.

[0068] In this embodiment, the quantum device construction list includes quantum device type data, quantum device identification data, quantum device attribute data, and quantum device coordinate data; the quantum device connection list includes multiple connection relationships between quantum devices. The quantum device identification data can be the specific name of the quantum device.

[0069] S102, based on the quantum device construction list, instantiates predefined quantum device models of various types. The quantum device models include device model classes and device model tables.

[0070] In some embodiments, the quantum device model types include: pad device model, superconducting quantum bit (Xmon) device model, resonant cavity device model, air bridge device model, Josephson junction device model, and general device model.

[0071] In some embodiments, the device model class defines a quantum device identifier, quantum device parameter attributes, the layer where the quantum device resides, and quantum device coordinates; the device model table defines a quantum device identifier field, multiple parameter fields, a layer field, and a coordinate field. The quantum device identifier can specifically be the name of the quantum device.

[0072] In this embodiment, each device model class defines in detail the key information such as the device name, parameter attributes, layer and coordinates, and the device model table records the relevant table fields. This precise definition method ensures the accuracy and consistency of quantum devices in layout design and avoids design defects caused by unclear device parameters or incorrect coordinates.

[0073] Specifically, the pad device model includes a pad device model class and a pad device model table; the Xmon device model includes an Xmon device model class and an Xmon device model table; the resonant cavity device model includes a resonant cavity device model class and a resonant cavity device model table; the air bridge device model includes an air bridge device model class and an air bridge device model table; the Josephson junction device model includes a Josephson junction device model class and a Josephson junction device model table; and the general device model includes a general device model class and a general device model table.

[0074] The pad device model class mainly defines the pad name, pad parameter attributes, the layer where the pad is located, and the one-dimensional coordinates that make up the pad. The corresponding pad device model table defines the relevant table fields, including name, parameter 1, parameter 2, parameter n, layer, and coordinate data fields.

[0075] The Xmon device model class mainly defines the Xmon name, Xmon parameter attributes, the layer where Xmon is located, and the two-dimensional coordinates that make up Xmon. The Xmon device model table defines the relevant table fields, including name, parameter 1, parameter 2, parameter n, layer, and coordinate data fields.

[0076] The resonant cavity device model class mainly defines the resonant cavity name, resonant cavity parameter attributes, the layer where the resonant cavity is located, and the two-dimensional coordinates that make up the resonant cavity. The resonant cavity device model table defines the relevant table fields, including name, parameter 1, parameter 2, parameter n, layer, and coordinate data fields.

[0077] The air bridge device model class mainly defines the air bridge name, air bridge parameter attributes, the layer where the air bridge is located, and the one-dimensional coordinates that make up the air bridge. The corresponding air bridge device model table defines relevant table fields, including name, parameter 1, parameter 2, parameter n, layer, and coordinate data fields.

[0078] The Josephson junction device model class mainly defines the Josephson junction name, Josephson junction parameter attributes, the layer where the Josephson junction is located, and the one-dimensional coordinates that make up the Josephson junction. The Josephson junction device model table defines the relevant table fields, including name, parameter 1, parameter 2, parameter n, layer, and coordinate data fields.

[0079] The general model class mainly defines the general component name, general parameter attributes, the layer it belongs to, and the one-dimensional coordinates of the components. The general component model table defines the relevant table fields, including name, parameter 1, parameter 2, parameter n, layer, and coordinate data fields.

[0080] In this embodiment, since the quantum device construction list includes quantum device type data, quantum device identification data, quantum device attribute data, and quantum device coordinate data, the quantum device construction list can be used to instantiate predefined quantum device models of various types, thereby obtaining quantum device instances under each type of quantum device model, and then maintaining and managing the quantum device instances according to type.

[0081] In this embodiment, quantum device instances are maintained and managed according to type, realizing centralized and standardized management of devices. This not only makes it easier for designers to find and use the required devices, but also facilitates unified updates and maintenance of devices, ensuring device consistency and availability.

[0082] In this embodiment, a device model library can be used to store various types of quantum device models, which facilitates the provision of abundant device resources for layout design.

[0083] S103, based on the instantiated quantum device models, construct each quantum device corresponding to the quantum device construction list.

[0084] In this embodiment, by combining the device build list, each quantum device corresponding to the quantum device build list can be constructed in the layout design model by combining various quantum device instances.

[0085] The layout design model includes a layout design model class and a layout design model table. The layout design model class includes layout design name, pad device object, Xmon device object, resonant cavity device object, air bridge device object, Josephson junction device object, general device object, line object, and user object. The layout design model table mainly includes layout design name, layout design data, and designer.

[0086] S104, based on the quantum device connection list, quantum device construction list, predefined connection model, and predefined device anchor point rules, determine the starting anchor point coordinates and ending anchor point coordinates corresponding to each connection relationship in the quantum device connection list; the device anchor point rules include static anchor point rules and dynamic anchor point calculation scripts; the static anchor point rules include the connection anchor points in each quantum device; the dynamic anchor point calculation script is used to calculate the offset of the connection anchor point coordinates of the quantum device based on the quantum device attribute data in the quantum device construction list; based on the offset of the connection anchor point coordinates of the quantum device, determine the starting anchor point coordinates and ending anchor point coordinates corresponding to each connection relationship.

[0087] In this embodiment, the interconnection model includes an interconnection model class and an interconnection model table. The interconnection model class includes the interconnection name, starting device object, ending device object, coordinates, and layer attributes. The interconnection model table records the interconnection relationships and path data, including the layout to which it belongs, the starting quantum device, the ending quantum device, the layer, and the coordinate attributes. Through the interconnection model, the interconnection relationships between quantum devices can be clearly managed and represented, providing effective data support and management methods for routing operations in layout design, enabling complex routing networks to be systematically organized and stored.

[0088] In this embodiment, each connection relationship includes a starting quantum device and an ending quantum device. The anchor coordinates of the connection between the starting quantum devices are the starting anchor coordinates, and the anchor coordinates of the connection between the ending quantum devices are the ending anchor coordinates.

[0089] In this embodiment, the device anchor rules include static device anchor rules and dynamic anchor calculation scripts. The static device anchor rules include the connection anchors for each quantum device. For example, such as... Figure 2 As shown, the anchor points for pad connections are the points with indices 1, 2, 8, and 9 in the pads. The anchor points for Xmon devices are the points with indices 0, 1, 3, and 4 in the Xmon device. The anchor points for left connections are the points with indices 0 and 1, and the anchor points for right connections are the points with indices 3 and 4. The input to the dynamic anchor point calculation script is the coordinates of the anchor points for the quantum devices and the quantum device attribute data of the quantum device in the quantum device build manifest. The output is the dynamically generated start point or end point coordinates.

[0090] In some embodiments, based on a quantum device wiring list, a quantum device construction list, a predefined wiring model, and predefined device anchor point rules, the starting anchor point coordinates and ending anchor point coordinates corresponding to each wiring relationship in the quantum device wiring list are determined, including:

[0091] Based on the quantum device connection list and a predefined connection model, the starting quantum device and ending quantum device corresponding to each connection relationship in the quantum device connection list are determined. Based on the starting quantum device and ending quantum device corresponding to each connection relationship, the quantum device construction list, and the static anchor point rules in the device anchor point rules, the first initial anchor point coordinates corresponding to each starting quantum device and the second initial anchor point coordinates corresponding to each ending quantum device are determined. Based on the dynamic anchor point calculation script and the quantum device attribute data in the quantum device construction list, the anchor point coordinate offsets corresponding to each starting quantum device and the anchor point coordinate offsets corresponding to each ending quantum device are calculated. Based on the anchor point coordinate offsets corresponding to each starting quantum device and the anchor point coordinate offsets corresponding to each ending quantum device, the first initial anchor point coordinates corresponding to each starting quantum device and the second initial anchor point coordinates corresponding to each ending quantum device are adjusted to obtain the starting anchor point coordinates and ending anchor point coordinates corresponding to each connection relationship.

[0092] In some embodiments, based on the starting quantum device, ending quantum device, quantum device construction list, and device static anchor point rules in the device anchor point rules corresponding to each connection relationship, the first initial anchor point coordinates corresponding to each starting quantum device and the second initial anchor point coordinates corresponding to each ending quantum device are determined, including:

[0093] Based on the starting quantum device and ending quantum device corresponding to each connection relationship, as well as the static anchor point rule in the device anchor point rule, the connection anchor point corresponding to each starting quantum device and the connection anchor point corresponding to each ending quantum device are determined; based on the connection anchor point corresponding to each starting quantum device and the connection anchor point corresponding to each ending quantum device, as well as the quantum device construction list, the first initial anchor point coordinates corresponding to each starting quantum device and the second initial anchor point coordinates corresponding to each ending quantum device are determined.

[0094] In practice, for each connection relationship, the starting quantum device and the ending quantum device can be determined. For the starting quantum device corresponding to the connection relationship, based on the device type, the specific device anchor point rules are read, and the corresponding first initial anchor point coordinates are obtained based on the static anchor point rules. The starting quantum device is generally an Xmon device or a resonant cavity device. For example, if the starting quantum device is an Xmon device, when routing the left connection, the static anchor point rules of the Xmon left connection are read to obtain the connection anchor point of the Xmon device in the left connection. Then, the first initial anchor point coordinates corresponding to the connection anchor point of the Xmon device in the left connection can be found from the quantum device build list. Then, based on the dynamic anchor point calculation script and the Xmon device attribute data in the quantum device build list, the anchor point coordinate offset corresponding to the Xmon device can be calculated. Based on the anchor point coordinate offset corresponding to the Xmon device, the first initial anchor point coordinates corresponding to the connection anchor point of the Xmon device are adjusted to obtain the anchor coordinates of the Xmon device, which is also the starting anchor point coordinates corresponding to this connection relationship. For the endpoint quantum device corresponding to this connection, the anchor point coordinates of the endpoint device can be obtained in the same way, that is, the anchor point coordinates of the endpoint corresponding to this connection. The endpoint quantum device is generally a pad device.

[0095] S105, based on the starting point coordinates and ending point coordinates of each connection relationship, generates connection paths for each constructed quantum device to obtain the quantum chip layout of the quantum device.

[0096] In some embodiments, connection paths are generated for each constructed quantum device based on the starting anchor coordinates and ending anchor coordinates corresponding to each connection relationship, including:

[0097] Based on the starting and ending anchor coordinates of each connection relationship, a path planning strategy to avoid obstacles is invoked to generate connection paths for each connection relationship among the constructed quantum devices.

[0098] In some embodiments, when a user modifies the parameter data of a quantum device in the quantum device build manifest, a database trigger detects the field update and can invoke the dynamic anchor point calculation script in the device anchor point rules to read the current parameter data, calculate the new anchor point coordinates, and thus generate a new connection path. For example, Figure 3 As shown, for pads, the parameters affecting anchor point coordinates are tgw and tw. When the values ​​of tgw and tw change, meaning the pad's parameter data is modified, the dynamic anchor point calculation script in the device anchor point rules can be called to read the current parameter data and calculate the new anchor point coordinates. For example... Figure 4As shown, for the Xmon device, the parameters affecting the anchor point coordinates are qflv, qflh, zbs, and xys. When the values ​​of qflv, qflh, zbs, and xys change, that is, the parameter data of the Xmon device is modified, the dynamic anchor point calculation script in the device anchor point rules can be called to read the current parameter data and calculate the new anchor point coordinates.

[0099] The layout design method provided in this application achieves standardized and normalized management of quantum devices by defining various quantum device models. During the layout design process, these predefined quantum device models can be directly called for instantiation and combination, avoiding the tedious process of designing each quantum device from scratch, greatly shortening the layout design cycle and improving design efficiency. Furthermore, with the help of predefined connection models and predefined device anchor point rules, the starting and ending anchor point coordinates of the quantum devices to be connected can be accurately determined based on the actual attribute data of the quantum devices, and reasonable connection paths can be generated. This not only reduces the complexity and error rate of manual operation, but also enables the connections to be accurately connected to the specified positions of the devices according to the actual design requirements, avoiding connection deviations or incorrect connections, and further improving the accuracy and reliability of the layout design.

[0100] In an optional embodiment, the layout design method further includes:

[0101] Output the quantum chip layout in JSON data format.

[0102] In practice, after the layout design is completed, the layout design is saved as a quantum chip layout in JSON data format according to the predefined layout design model.

[0103] In an optional embodiment, the layout design method further includes:

[0104] Based on predefined layout design models and device model classes, the quantum chip layout in JSON data format is parsed to obtain the coordinate data and layer data of each quantum device;

[0105] Based on the coordinate data and layer data of each quantum device, as well as the data conversion rules, the quantum chip layout in JSON data format is converted into a quantum chip layout in GDS data format.

[0106] In this embodiment, the data conversion rules include: the layout GDS file consists of a top-level cell and multiple sub-cells (cells are CELLs); devices on the same layer are placed in the same sub-cell; a cell can store multiple devices or combinations of devices on the same layer.

[0107] In this embodiment, a quantum chip layout in JSON data format can be converted into a quantum chip layout in GDS data format using a data converter.

[0108] Specifically, data converters can exist in the form of data converter plugins. Data converter plugins include... Figure 5 As shown, the data converter includes metadata and a conversion implementation class. The metadata in the data converter can be defined according to actual conversion needs, mainly including basic metadata, such as layout name and designer; business attribute metadata, such as device name, device coordinate attributes, and device layer; and rule mapping metadata, which refers to the relationships between devices, layers, and units. The conversion implementation class mainly implements mutual parsing of devices between JSON and GDS, device construction, unit mapping, and coordinate system conversion. For example, the coordinates of a device instance in JSON are converted to polygons or paths in GDS; the connecting paths in JSON are converted to Bézier curves or straight line segment metadata in GDS; and device IDs and parameters are embedded in the attribute fields of the GDS file to achieve reverse tracing of JSON data. The conversion implementation class mainly includes three methods: one is an initialization method used to initialize some basic parameters and converter startup parameters; the other two methods are a JSON data to GDS data conversion method and a GDS data to JSON data conversion method. Figure 5 As shown, when it's necessary to convert a JSON data file to a GDS data file, a data converter can be defined according to the requirements, then loaded, the JSON data file bound to the data converter, and the data converter will convert the JSON data file to a GDS data file. Similarly, when it's necessary to convert a GDS data file to a JSON data file, a data converter can be defined according to the requirements, then loaded, and the data converter will convert the GDS data file to a JSON data file.

[0109] The specific implementation of converting layout design JSON data to GDS data is as follows: Parse the layout JSON data, obtain all device objects in the layout based on the layout design model and device model classes, and obtain the coordinates and layer of each device object. For each object, obtain the device layer and coordinates, define a top-level unit and multiple sub-units according to the data conversion rules, and each sub-unit receives device object data. Specifically, a GDS file is generated using the Gdstk library in Python. Since the coordinate system in JSON and the coordinate system in Gdstk are inconsistent, a unified coordinate system conversion is required. After the coordinate conversion, the coordinates are uniformly organized according to the polygon device generation standard of the Gdstk library. After the device is constructed, it is added to the sub-unit; devices on the same layer are in the same unit. Finally, it is added to the top-level unit, and the corresponding position is set.

[0110] In this embodiment, the conversion of layout design GDS data to JSON data can also be implemented. The implementation is as follows: parsing the layout GDS data, obtaining the top-level unit, traversing the top-level unit, and obtaining the sub-unit and device data according to the data conversion rules. Since the coordinate system in GDS and the coordinate system in JSON are inconsistent, a unified coordinate system conversion is required. After the coordinate conversion, the JSON data is encapsulated and constructed through the device model class and the layout model class.

[0111] In this embodiment, a converter is established between layout design JSON data and GDS data, enabling convenient conversion between the two data formats. This allows designers to quickly generate the required GDS files according to actual needs, without the need for complex manual data conversion operations, improving work efficiency and reducing problems caused by data conversion errors.

[0112] In this embodiment, design data can be saved in both JSON and GDS formats. JSON format facilitates data storage, transmission, and database management, while GDS format is suitable for subsequent manufacturing processes. This support for multiple data formats meets the data format requirements of different stages, improving the flexibility and adaptability of data processing.

[0113] In an optional embodiment, the layout design method further includes:

[0114] The target quantum chip layout in GDS data format is obtained. The version of the target quantum chip layout in GDS data format is different from that of the quantum chip layout. The GDS polygon geometric features in the target quantum chip layout in GDS data format are extracted. Based on the GDS polygon geometric features, the target quantum chip layout in GDS data format is converted into a target quantum chip layout in JSON data format corresponding to the version of the quantum chip layout.

[0115] In this embodiment, the target quantum chip layout in GDS data format differs from the version of the quantum chip layout. For example, the target quantum chip layout in GDS data format may have been exported from another layout design tool. Consequently, the current layout system cannot recognize the combined polygons in the target quantum chip layout in GDS data format, such as pads, resonant cavities, Xmon, and other combined devices defined by the current layout system. Therefore, a custom converter can be used to convert the target quantum chip layout in GDS data format into a target quantum chip layout in JSON data format corresponding to the version of the quantum chip layout. This enables the conversion and maintenance of layout design files exported from other layout design tools within the current layout design system.

[0116] In this embodiment, the customized converter needs to analyze the target quantum chip layout in GDS data format to determine whether to perform a direct conversion or convert it to an existing combined device model in the current layout design tool. If it is converted to an existing combined device model, a pre-set associated data matching list is required. A combination identifier is established through the list to adapt to the existing combined device model in the current layout.

[0117] In some embodiments, based on GDS polygonal geometric features, the target quantum chip layout in GDS data format is converted into a target quantum chip layout in JSON data format corresponding to the version of the quantum chip layout, including:

[0118] The geometric features of the GDS polygons are encoded into hash values; a search is performed in the model library based on the hash values ​​to determine the combined device model corresponding to the hash values; the combined device model is a combined device model in JSON data format corresponding to the version of the quantum chip layout; based on the combined device model, the target quantum chip layout in JSON data format is generated.

[0119] In this embodiment, the combined device model in JSON data format corresponding to the version of the quantum chip layout is pre-calculated with a hash value and stored.

[0120] In this embodiment, the customized converter is divided into a geometric feature extractor, a topological fingerprint generator, a model matching engine, and a metadata binding module. The geometric feature extractor is used to parse GDS polygon data and extract geometric features. The topological fingerprint generator encodes the geometric features into hash values. The model matching engine matches the current system's combined model library based on fingerprint similarity. The metadata binding module associates the matching results with quantum parameters to generate an editable JSON structure.

[0121] For example, the target quantum chip layout in GDS data format exported by an external tool contains a cross-shaped polygon (12 vertices). Through feature extraction, the geometric features of the GDS polygon are obtained, including 12 sides, symmetry of 0.92, and area ratio of 0.28. These geometric features are encoded into a hash value: hash("12-0.92-0.28") → 0x7a3e. This hash value matches the hash value 0x7a3e of the Xmon device in the model library (Hamming distance = 3). Therefore, it is determined that the target quantum chip layout in GDS data format contains an Xmon device. Then, based on the dimensions of the cross, the capacitor arm length is calculated to be 80μm, and the quantum frequency is approximately 5.2GHz. This allows the generation of an editable Xmon object in JSON data format, which can then be parameterized to obtain the target quantum chip layout in JSON data format.

[0122] This application also provides a layout design apparatus, such as... Figure 6As shown, it includes:

[0123] The acquisition module 41 is used to acquire the quantum device construction list and the quantum device connection list.

[0124] The instantiation module 42 is used to instantiate predefined quantum device models of various types based on the quantum device construction list. The quantum device models include device model classes and device model tables.

[0125] Module 43 is used to construct each quantum device corresponding to the quantum device build list based on the instantiated quantum device models.

[0126] Module 44 is used to determine the starting and ending anchor coordinates of each connection in the quantum device connection list based on the quantum device connection list, the quantum device construction list, the predefined connection model, and the predefined device anchor rules. The device anchor rules include static anchor rules and dynamic anchor calculation scripts. The static anchor rules include the connection anchors in each quantum device. The dynamic anchor calculation script is used to calculate the offset of the connection anchor coordinates of the quantum devices based on the quantum device attribute data in the quantum device construction list. Based on the offset of the connection anchor coordinates of the quantum devices, the starting and ending anchor coordinates of each connection are determined.

[0127] The generation module 45 is used to generate connection paths for each constructed quantum device based on the starting anchor coordinates and ending anchor coordinates corresponding to each connection relationship, so as to obtain the quantum chip layout of the quantum device.

[0128] The layout design apparatus provided in this application achieves standardized and regulated management of quantum devices by defining various quantum device models. During the layout design process, these predefined quantum device models can be directly called for instantiation and combination, avoiding the tedious process of designing each quantum device from scratch, greatly shortening the layout design cycle and improving design efficiency. Furthermore, with the help of predefined connection models and predefined device anchor point rules, the starting and ending anchor point coordinates of the quantum devices to be connected can be accurately determined based on the actual attribute data of the quantum devices, and reasonable connection paths can be generated. This not only reduces the complexity and error rate of manual operation, but also enables the connections to be precisely connected to the specified positions of the devices according to actual design requirements, avoiding connection deviations or incorrect connections, and further improving the accuracy and reliability of layout design.

[0129] In some embodiments, the determining module 44 is used to determine the starting quantum device and the ending quantum device corresponding to each connection relationship in the quantum device connection list based on the quantum device connection list and a predefined connection model; based on the starting quantum device and the ending quantum device corresponding to each connection relationship, the quantum device construction list, and the device static anchor point rules in the device anchor point rules, determine the first initial anchor point coordinates corresponding to each starting quantum device and the second initial anchor point coordinates corresponding to each ending quantum device; based on the dynamic anchor point calculation script and the quantum device attribute data in the quantum device construction list, calculate the anchor point coordinate offset corresponding to each starting quantum device and the anchor point coordinate offset corresponding to each ending quantum device; based on the anchor point coordinate offset corresponding to each starting quantum device and the anchor point coordinate offset corresponding to each ending quantum device, adjust the first initial anchor point coordinates corresponding to each starting quantum device and the second initial anchor point coordinates corresponding to each ending quantum device to obtain the starting anchor point coordinates and the ending anchor point coordinates corresponding to each connection relationship.

[0130] In some embodiments, the determining module 44 is used to determine the connection anchor points corresponding to each starting quantum device and the connection anchor points corresponding to each ending quantum device based on the starting quantum device, the ending quantum device, and the device static anchor point rules in the device anchor point rules; and to determine the first initial anchor point coordinates corresponding to each starting quantum device and the second initial anchor point coordinates corresponding to each ending quantum device based on the connection anchor points corresponding to each starting quantum device, the connection anchor points corresponding to each ending quantum device, and the quantum device construction list.

[0131] In some embodiments, the quantum device model types include: pad device model, superconducting quantum bit device model, resonant cavity device model, air bridge device model, Josephson junction device model, and general device model.

[0132] In some embodiments, the device model class defines a quantum device identifier, quantum device parameter attributes, the layer where the quantum device is located, and quantum device coordinates; the device model table defines a quantum device identifier field, multiple parameter fields, a layer field, and a coordinate field.

[0133] In some embodiments, the generation module 45 is used to call a path planning strategy to avoid obstacles based on the starting anchor coordinates and ending anchor coordinates corresponding to each connection relationship, so as to generate connection paths for each quantum device.

[0134] In some embodiments, the layout design apparatus further includes:

[0135] The output module is used to output the quantum chip layout in JSON data format.

[0136] According to embodiments of this application, this application also provides an electronic device.

[0137] Figure 7 A schematic block diagram of an example electronic device 800 that can be used to implement embodiments of this application is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the application described and / or claimed herein.

[0138] like Figure 7 As shown, the electronic device 800 includes a computing unit 801, which can perform various appropriate actions and processes based on a computer program stored in a read-only memory (ROM) 802 or a computer program loaded from a storage unit 808 into a random access memory (RAM) 803. The RAM 803 may also store various programs and data required for the operation of the electronic device 800. The computing unit 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0139] Multiple components in electronic device 800 are connected to I / O interface 805, including: input unit 806, such as keyboard, mouse, etc.; output unit 807, such as various types of displays, speakers, etc.; storage unit 808, such as disk, optical disk, etc.; and communication unit 809, such as network card, modem, wireless transceiver, etc. Communication unit 809 allows electronic device 800 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0140] The computing unit 801 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 performs the various methods and processes described above, such as layout design methods. For example, in some embodiments, the layout design method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 800 via ROM 802 and / or communication unit 809. When the computer program is loaded into RAM 803 and executed by the computing unit 801, one or more steps of the layout design method described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform layout design methods by any other suitable means (e.g., by means of firmware).

[0141] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transferring data and instructions to the storage system, the at least one input device, and the at least one output device.

[0142] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0143] This application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the layout design method described above in this application.

[0144] This application provides a computer-readable storage medium storing executable instructions, wherein the executable instructions are stored and when executed by a processor, they will cause the processor to execute the layout design method provided in this application.

[0145] In some embodiments, a computer-readable storage medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may be a machine-readable signal medium or a machine-readable storage medium. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0146] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0147] As an example, executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple collaborating files (e.g., a file that stores one or more modules, subroutines, or code sections).

[0148] As an example, executable instructions can be deployed to execute on a single computing device, or on multiple computing devices located in one location, or on multiple computing devices distributed across multiple locations and interconnected via a communication network.

[0149] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0150] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0151] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0152] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this application can be achieved, and this is not limited herein.

[0153] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.

[0154] 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.

Claims

1. A layout design method characterized by comprising: The method comprises the following steps: obtaining a quantum device construction list and a quantum device connection list; instantiating pre-defined quantum device models based on the quantum device construction list, wherein the quantum device models comprise a device model class and a device model table, the device model class defines quantum device identification, quantum device parameter attributes, a layer where the quantum device is located, and quantum device coordinates, and the device model table defines a quantum device identification field, a plurality of parameter fields, a layer field, and a coordinate field; constructing quantum devices corresponding to the quantum device construction list based on the instantiated quantum device models; determining start anchor point coordinates and end anchor point coordinates corresponding to each connection relationship in the quantum device connection list based on the quantum device connection list, the quantum device construction list, pre-defined connection models, and pre-defined device anchor point rules, including: determining start quantum devices and end quantum devices corresponding to each connection relationship in the quantum device connection list based on the quantum device connection list and the pre-defined connection models; determining first initial anchor point coordinates corresponding to each start quantum device and second initial anchor point coordinates corresponding to each end quantum device based on the start quantum devices and the end quantum devices corresponding to each connection relationship, the quantum device construction list, and device static anchor point rules in the device anchor point rules; calculating anchor point coordinate offsets of each start quantum device and anchor point coordinate offsets of each end quantum device based on dynamic anchor point calculation scripts and quantum device attribute data in the quantum device construction list; adjusting the first initial anchor point coordinates corresponding to each start quantum device and the second initial anchor point coordinates corresponding to each end quantum device based on the anchor point coordinate offsets of each start quantum device and the anchor point coordinate offsets of each end quantum device to obtain start anchor point coordinates and end anchor point coordinates corresponding to each connection relationship; the device anchor point rules comprise device static anchor point rules and dynamic anchor point calculation scripts; the device static anchor point rules comprise connection anchor points in each quantum device; the dynamic anchor point calculation scripts are used to calculate offsets of connection anchor point coordinates of quantum devices based on quantum device attribute data in the quantum device construction list; and determining the start anchor point coordinates and the end anchor point coordinates corresponding to each connection relationship based on the offsets of the connection anchor point coordinates of the quantum devices; generating connection paths for the constructed quantum devices based on the start anchor point coordinates and the end anchor point coordinates corresponding to each connection relationship to obtain a quantum chip layout of the quantum devices.

2. The layout design method according to claim 1, wherein determining the first initial anchor point coordinates corresponding to each start quantum device and the second initial anchor point coordinates corresponding to each end quantum device based on the start quantum devices and the end quantum devices corresponding to each connection relationship, the quantum device construction list, and device static anchor point rules in the device anchor point rules, including: determine, based on the start quantum device corresponding to each of the link anchors and the end quantum device corresponding to each of the link anchors and the quantum device construction list, a first initial anchor point coordinate corresponding to each of the start quantum devices and a second initial anchor point coordinate corresponding to each of the end quantum devices. The quantum device model types include: a pad device model, a superconducting quantum bit device model, a resonant cavity device model, an air bridge device model, a Josephson junction device model, and a general device model.

3. The layout design method according to claim 1, wherein Based on the start anchor point coordinates and the end anchor point coordinates corresponding to each link relationship, a link path generation is performed on each of the constructed quantum devices, including:

4. The layout design method according to claim 1, wherein Based on the start anchor point coordinates and the end anchor point coordinates corresponding to each link relationship, a path planning strategy for avoiding obstacles is called to generate a link path corresponding to each link relationship between the constructed quantum devices, so as to perform a link path generation on each of the constructed quantum devices. Further comprising:

5. The layout design method according to claim 1, wherein outputting the quantum chip layout in a JSON data format. Further comprising:

6. The layout design method according to claim 5, wherein Based on the pre-defined layout design model and the device model class, the JSON data format quantum chip layout is parsed to obtain coordinate data and layer data of each quantum device; Based on the coordinate data and the layer data of each quantum device and a data conversion rule, the JSON data format quantum chip layout is converted into a GDS data format quantum chip layout. Further comprising:

7. The layout design method of claim 1, wherein obtaining a target quantum chip layout in a GDS data format, wherein the target quantum chip layout in the GDS data format is different from a version of the quantum chip layout; extracting GDS polygon geometric features in the target quantum chip layout in the GDS data format; Based on the GDS polygon geometric features, the target quantum chip layout in the GDS data format is converted into a target quantum chip layout in a JSON data format corresponding to the version of the quantum chip layout. Based on the GDS polygon geometric features, the target quantum chip layout in the GDS data format is converted into a target quantum chip layout in a JSON data format corresponding to the version of the quantum chip layout, including:

8. The layout design method according to claim 7, wherein encoding the GDS polygon geometric features into a hash value; based on the hash value, searching in a model library to determine a combined device model corresponding to the hash value; the combined device model is a combined device model in a JSON data format corresponding to the version of the quantum chip layout; based on the combined device model, generating a target quantum chip layout in a JSON data format. including:

9. A layout design device characterized by comprising: an acquisition module, configured to acquire a quantum device construction list and a quantum device link list; ​ The instantiation module is configured to instantiate pre-defined quantum device models based on the quantum device construction list, wherein the quantum device models comprise a device model class and a device model table; the device model class defines quantum device identification, quantum device parameter attributes, a layer where the quantum device is located, and quantum device coordinates; and the device model table defines a quantum device identification field, a plurality of parameter fields, a layer field, and a coordinate field. The construction module is configured to construct quantum devices corresponding to the quantum device construction list based on the instantiated quantum device models. The determination module is configured to determine start point anchor coordinates and end point anchor coordinates corresponding to each connection relationship in the quantum device connection list based on the quantum device connection list, the quantum device construction list, pre-defined connection models, and pre-defined device anchor point rules, including: determining start point quantum devices and end point quantum devices corresponding to each connection relationship in the quantum device connection list based on the quantum device connection list and the pre-defined connection models; determining first initial anchor coordinates corresponding to each start point quantum device and second initial anchor coordinates corresponding to each end point quantum device based on the start point quantum devices and the end point quantum devices corresponding to each connection relationship, the quantum device construction list, and a device static anchor point rule in the device anchor point rules; calculating anchor coordinate offsets of each start point quantum device and anchor coordinate offsets of each end point quantum device based on a dynamic anchor point calculation script and the quantum device attribute data in the quantum device construction list; and adjusting the first initial anchor coordinates corresponding to each start point quantum device and the second initial anchor coordinates corresponding to each end point quantum device based on the anchor coordinate offsets of each start point quantum device and the anchor coordinate offsets of each end point quantum device, to obtain start point anchor coordinates and end point anchor coordinates corresponding to each connection relationship; the device anchor point rules comprise a device static anchor point rule and a dynamic anchor point calculation script; the device static anchor point rule comprises connection anchors in each quantum device; and the dynamic anchor point calculation script is used to calculate offsets of connection anchor coordinates of quantum devices based on quantum device attribute data in the quantum device construction list. The generation module is configured to generate connection paths for the constructed quantum devices based on the start point anchor coordinates and the end point anchor coordinates corresponding to each connection relationship, to obtain a quantum chip layout of quantum devices.

10. The layout design apparatus according to claim 9, wherein The determination module is configured to determine connection anchors corresponding to each start point quantum device and connection anchors corresponding to each end point quantum device based on the start point quantum devices and the end point quantum devices corresponding to each connection relationship and a device static anchor point rule in the device anchor point rules. The first initial anchor point coordinates corresponding to each of the start quantum devices and the second initial anchor point coordinates corresponding to each of the end quantum devices are determined based on the wire anchor points corresponding to each of the start quantum devices and the wire anchor points corresponding to each of the end quantum devices and the quantum device construction list.

11. The layout design device according to Claim 9, wherein The quantum device model types include: a pad device model, a superconducting quantum bit device model, a resonant cavity device model, an air bridge device model, a Josephson junction device model, and a general device model.

12. The layout design apparatus of claim 9, wherein, The generation module is configured to call a path planning strategy for avoiding obstacles based on the start anchor point coordinates and the end anchor point coordinates corresponding to each of the wire relationships, and generate a wire path corresponding to each of the wire relationships between the constructed quantum devices to generate a wire path for each of the quantum devices.

13. The layout design device according to Claim 9, wherein Further comprising: An output module configured to output the quantum chip layout in a JSON data format.

14. An electronic device, comprising: Comprising: at least one processor; and a memory connected to the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to cause the at least one processor to perform the layout design method of any one of claims 1-8.

15. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions for causing a computer to perform the layout design method of any one of claims 1-8.

16. A computer program product comprising computer programs or instructions, characterized in that, The computer program or instructions, when executed by a processor, implement the layout design method of any one of claims 1-8.

Images