quantcore_circuits.assembly.drc =============================== .. py:module:: quantcore_circuits.assembly.drc .. autoapi-nested-parse:: Connectivity DRC: every pin, endpoint and handle connected to something, nothing outside the chip, no crossings. ======================== ======== ==================================================================================== rule severity check ======================== ======== ==================================================================================== ``dangling_port`` warning a component port with no route or snap on it (e.g. an unused claw) ``no_lom`` warning a component with ports but no LOM model (its ports stay bare nodes in the circuit) ``outside_chip`` error a component box or route vertex outside the chip box ``overlap`` warning two component boxes overlap on a chip face both draw on (snapped pairs excepted; a TSV or bump on another component only where its via or bump lands on that component's etch) ``crossing`` error two route centre lines cross on the same chip face (a CPW crossing needs an airbridge) ``open``/``short`` error declared vs extracted connectivity (KQC netlist, see :mod:`.netlist`) ``open_conductor`` error a route and the component port it ends on are not one piece of metal (etch between them on the centre line, e.g. a pin whose gap runs past the pin), judged on the face that route end is drawn on ``route_failed`` error a route could not be built (keep-going build): it is not in the layout, with the reason ``route_overlap`` error two routes' *built* centre conductors overlap on the same face (meanders included; also two routes on one component, away from it) ``route_clearance`` warning two routes' built gap etch touches (no ground strip between the two CPWs) ``route_self_overlap`` error a route's built centre conductor runs over itself (nodes looping back across an earlier straight, meander turns landing on another part of the same route) ``route_over_component`` error a route's built conductor or gap overlaps the etch of a component that is not one of its ends (the route runs across it) ``airbridge_short`` error a route's airbridge pad lands on another route's conductor or gap (shorts it to ground) ``frame_margin`` warning a component (not a pad) reaches into the die margin of the PDK frame ``frame_keepout`` warning a component or route on a frame marker area or the device ID ``pad_edge`` design PDK pad rule: a bond pad / launcher (or ``TaperedPad`` ring) whose outer etch edge is not ``frame.pad_edge`` (100 µm) from the nearest die edge (fix: ``place.edge``) ``pdk_rn`` design PDK margin: a junction's R_n (from the instance's L_J) outside the junction window ``pdk_fq`` design PDK margin: a qubit's f_q target outside the PDK qubit band (4–8 GHz) ``pdk_claw`` design PDK margin: a ``metal:TransmonCross`` claw long enough to reach the side arms (fix: a longer ``cross_length``) ======================== ======== ==================================================================================== The ``pad_edge`` and ``pdk_*`` rows are **design warnings** (severity ``"design"``, 2026-11-03): the design system builds any values; it flags where a design leaves the PDK margins and never blocks the build. A report with only design warnings still reads "DRC clean" (with their count) and is ``ok``. ``check(..., netlist=False)`` skips the KQC netlist extraction; that fast variant runs on every build and is written into the KLayout sidecar so the plugin can mark the issues in place. Classes ------- .. autoapisummary:: quantcore_circuits.assembly.drc.DrcIssue quantcore_circuits.assembly.drc.DrcReport Functions --------- .. autoapisummary:: quantcore_circuits.assembly.drc.check quantcore_circuits.assembly.drc.device_id_block quantcore_circuits.assembly.drc.pdk_margin_issues Module Contents --------------- .. py:class:: DrcIssue .. py:attribute:: message :type: str .. py:attribute:: objects :type: list[str] :value: [] .. py:attribute:: rule :type: str .. py:attribute:: severity :type: str .. py:attribute:: where :type: list[tuple[float, float]] :value: [] .. py:class:: DrcReport .. py:method:: to_json() -> list[dict] .. py:property:: design :type: list[DrcIssue] PDK design warnings (pad edge, junction R_n window, f_q band, claw length): flagged, never enforced. .. py:property:: errors :type: list[DrcIssue] .. py:attribute:: issues :type: list[DrcIssue] .. py:property:: ok :type: bool .. py:property:: warnings :type: list[DrcIssue] .. py:function:: check(source, netlist: bool = True, keep_going: bool = False) -> DrcReport DRC of a design or build result. ``keep_going`` builds a design file with the routes that fail left out, and the report names them (``route_failed``); the default raises on a route that cannot be built. .. py:function:: device_id_block(result) Where the chip put its device ID (``qcc_device_id_p1/p2`` refpoints, µm), or None (no frame / older build). .. py:function:: pdk_margin_issues(design, boxes: dict) -> list[DrcIssue] PDK design warnings (flagged, never enforced): pad edge distance, junction R_n window, f_q band, TransmonCross claw vs arm length.