Skip to content

Local linting

The linter runs before any network call. Capacity violations and interaction hotspots surface on your laptop, with no cloud round trip.

Capacity audit

Qiskit's transpiler checks coupling maps during compilation. Limbo's linter checks layout feasibility up front and raises a structured exception you can catch:

from limbo_quantum import CircuitParser, LocalStaticLinter, TopologyCapacityError

ir = CircuitParser.from_qiskit(qc)
linter = LocalStaticLinter(ir, num_qpus=2, max_capacity_per_qpu=4)
try:
    linter.capacity_audit()
except TopologyCapacityError as exc:
    # Caught locally. No paid API call spent.
    print(f"needed {exc.num_qubits} qubits, layout had {exc.target_capacity}")

Hotspot detection

Hotspots are "hub" qubits whose interaction degree dominates the circuit: the ones that will generate the most cross-chip traffic once the circuit is partitioned. By default, any qubit carrying more than 30% of the total degree is flagged.

report = linter.hotspot_detection(threshold_ratio=0.30)

With verbose=True (the default) it prints a table; the structured report is always returned for CI.