Qiskit / qiskit
88%
main: 88%

LAST BUILD BRANCH: gh-readonly-queue/stable/2.2/pr-15140-041c0425701bc61a61a212bbf2e2716f04993552
DEFAULT BRANCH: main
Repo Added
Files 867
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH gh-readonly-queue/main/pr-14607-1e7a3fe3535f2623eb77f0a068cfdcd11e1dd272
branch: gh-readonly-queue/main/pr-14607-1e7a3fe3535f2623eb77f0a068cfdcd11e1dd272
CHANGE BRANCH
x

coverage: 88.261% (+0.02%) from 88.238%
16950288650

push

github

web-flow 
Collapse Sabre nodes with no routing implications (#14607)

* Collapse Sabre nodes with no routing implications

Not all nodes in the `SabreDAG` actually imply additional routing
constraints.  For example, a 2q gate immediately following a prior 2q
gate on the same qubits doesn't need to be routed; it's automatically
valid as soon as its predecessor is.  Similarly, 1q gates (without
additional classical wires) never impact routing and can be folded into
previous instructions.

More formally, a `Synchronize` node whose incoming edges are all from
the same predecessor (or are at the start of the circuit) does not
actually synchronise anything, and can be folded into any preceding
node.  A `TwoQ` node whose incoming edges are all from the same
predecessor can be folded into that predecessor if it is another `TwoQ`
node (even if there were already intermediate `Synchronize` nodes folded
into that `TwoQ` node).  `ControlFlow` nodes always have to be
considered by the router, because they need to be recursed into.

Collapsing these nodes as part of the `SabreDAG` construction has a few
benefits:

- In layout, when we keep multiple versions of a `SabreDAG`
  around, we have to store less memory, especially because we can
  entirely throw away all tracking of the collapsed DAG nodes, since we
  never need to rebuild afterwards.

- In routing, when we look ahead to populate the extended set, we no
  longer need to have the separate `visit_now` queue because all the
  nodes (and more!) that we would "look through" to make a DFS over the
  2q gates are now automatically folded into the preceding 2q gate
  already.  The behaviour is not entirely identical (the handling of
  wide `Synchronize` items can be slightly different), but the spirit is
  still there, and the handling is much easier.

- When populating the extended set, runs of 2q gates can no longer be
  multiply counted.  Previously, a run _could_ saturate the extended
  set, biasing the algorithm toward... (continued)

65 of 68 new or added lines in 2 files covered. (95.59%)

10 existing lines in 4 files now uncovered.

87249 of 98853 relevant lines covered (88.26%)

508963.48 hits per line

Relevant lines Covered
98853 RELEVANT LINES 87249 COVERED LINES
508963.48 HITS PER LINE
Source Files on gh-readonly-queue/main/pr-14607-1e7a3fe3535f2623eb77f0a068cfdcd11e1dd272

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
16950288650 gh-readonly-queue/main/pr-14607-1e7a3fe3535f2623eb77f0a068cfdcd11e1dd272 Collapse Sabre nodes with no routing implications (#14607) * Collapse Sabre nodes with no routing implications Not all nodes in the `SabreDAG` actually imply additional routing constraints. For example, a 2q gate immediately following a prior 2... push web-flow github
88.26
See All Builds (13976)