planqc / pushquantum-2026-leaderboard
Publicrx and rz run, and AOD move instructions carry them to an entangling zone, where cz
acts on interaction pairs. Your compile_circuit(circuit, architecture_spec) returns the compiled circuit
and an Architecture holding the initial loading of its qubits. The template notebook explains the
architecture and the rules for moves.
Validity. Every compilation must pass two checks: a replay on the architecture (legal moves, a valid
initial loading, each gate in a zone that allows it, cz only on an interaction pair) and equivalence to
the input circuit. If either fails on any benchmark, the submission is rejected.
The metric. Your compiler runs on 36 benchmark circuits: hardware-efficient, IHVA and QAOA ansätze on
12, 20 and 50 qubits. Over all of them we total the move distance (each move counts the farthest any of its
atoms travels) and the depth of the circuits without their moves, and compare each total with that of a naive
compiler, which carries the two atoms of every cz to the entangling zone and back. Your score is
0.8 × the % reduction in move distance + 0.2 × the % reduction in depth. Higher is better: the naive
compiler scores 0%.
How to submit.
compile_circuit in its notebook, as a top-level function
(@app.function).compile_circuit can only rely on those: for example, append
Move(...) to your circuit instead of calling circuit.move(...), which an ordinary cell registers.
It can import marimo, qiskit, numpy and scipy, and it runs without network access.planqc, since this notebook downloads it as planqc.username/workspace and press
Submit. Scoring takes a few minutes, and each compilation may take up to 5 minutes.compile_circuit on
every benchmark.