Across 6 intersections · 0 blocked links
Compared with the fixed-cycle plan in the latest logged run.
p=1 QAOA circuit model · browser simulator estimate.
Network digital twin
Node color indicates density; selected amber corridor reserves north–south green for the ambulance.
Green corridor active
Ambulance route: I1 → I2 → I5 → I6. Current priority node: I2. The QUBO applies a corridor reward only to the remaining route.
Intersection telemetry
Current state used to build the shared queue, delay, throughput, and coordination QUBO.
| Intersection | Density | Queue | Phase | Pedestrian |
|---|---|---|---|---|
I1 Harbor & 1st | 29% | 12 | NS | Clear |
I2 Harbor & 4th | 43% | 20 | NS | Request active |
I3 Harbor & 7th | 44% | 18 | EW | Clear |
I4 Market & 1st | 68% | 33 | EW | Clear |
I5 Market & 4th | 59% | 26 | EW | Request active |
I6 Market & 7th | 51% | 19 | NS | Clear |
Classical vs quantum comparison
A persisted analysis record is written on every comparison run, then reused by the charts and history below.
Fixed timing
Static current-cycle baseline
I1:NS · I2:EW · I3:EW · I4:EW · I5:NS · I6:NS
Classical optimizer
Exhaustive search over same QUBO
I1:NS · I2:EW · I3:NS · I4:EW · I5:NS · I6:EW
QAOA p=1 simulator
Same QUBO · browser circuit estimator
6 qubits · depth 14
I1:NS · I2:EW · I3:NS · I4:EW · I5:NS · I6:EW
Impact estimate
Classical optimized plan compared with the static fixed-cycle baseline.
Honest benchmark note
For six intersections, this browser-side p=1 QAOA simulator is not expected to beat exhaustive classical search on speed or solution quality. Its role here is to validate the shared QUBO and circuit-ready workflow that could be benchmarked on hardware or larger annealers.
Run log
Comparison artifacts stored in the app’s built-in key-value store.
| Run | Scenario | Fixed cost | Classical cost | QAOA cost | Wait-time change |
|---|---|---|---|---|---|
Tick 1 9/19/2026, 6:50:06 PM | Normal flow | -1.61 | -7.90 | -7.90 | 21.2% |