Qiskit / qiskit
88%
main: 88%

LAST BUILD BRANCH: gh-readonly-queue/main/pr-15036-7f641edc873829ad1ffd795765f769b215d4d5db
DEFAULT BRANCH: main
Repo Added
Files 871
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-14317-3f247830137c7d584e1e76b2f653b4e84306796f
branch: gh-readonly-queue/main/pr-14317-3f247830137c7d584e1e76b2f653b4e84306796f
CHANGE BRANCH
x

coverage: 87.748% (-0.03%) from 87.781%
16144776592

push

github

web-flow 
Rewrite Sabre interfaces to be Rust native (#14317)

* Add further creation and destructuring methods to `NLayout`

These are to allow more efficient Rust-space use of the object, allowing
reallocations to be avoided when doing things like ancilla expansion and
layout transformations at a scale larger than token swapping.

* Rewrite Sabre interfaces to be Rust native

This is a major rewrite of all the Sabre interfaces, though the core
routing logic is unchanged.  Note that the test suite is unaltered.

At least as far as the test suite covers, this change is RNG compatible
with its parent, and in several places, explicit code is added to
achieve this.  Given the neighbour-tracking structures are updated,
there can be some divergences, however, depending on how the order that
a coupling map was defined.

Changes to data structures
==========================

Changed `SabreDAG`
------------------

`SabreDAG` is now completely Rust-internal and not even exposed to
Python.  It's constructed directly from a `DAGCircuit`.  When
control-flow blocks are encountered, the temporary `DAGCircuit` backing
them is stored within the `SabreDAG` node itself, so there's no need for
all the `block_results` side-car handling.

The nodes in the graph explicitly store how the node affects routing:
they can be `TwoQ` (the actual routing target), `Synchronize` (a
non-routing object that has only data dependencies) or `ControlFlow`.
This simplifies the internal handling within the router, since now it
doesn't need to re-infer it.  It also lets us decay control-flow
operations to simple `Synchronize` points when we're in layout mode,
similar to how clearing the `block_nodes` field could implicitly do
before.

A follow-up commit (which necessarily changes the RNG compatibility)
makes stronger use of this new `SabreDAG` form to compress the
interaction graph during construction, reducing the amount of work done
by routing trials when advancing the state after a gate is routed.
... (continued)

944 of 1088 new or added lines in 10 files covered. (86.76%)

41 existing lines in 9 files now uncovered.

81262 of 92608 relevant lines covered (87.75%)

548564.8 hits per line

Relevant lines Covered
92608 RELEVANT LINES 81262 COVERED LINES
548564.8 HITS PER LINE
Source Files on gh-readonly-queue/main/pr-14317-3f247830137c7d584e1e76b2f653b4e84306796f

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
16144776592 gh-readonly-queue/main/pr-14317-3f247830137c7d584e1e76b2f653b4e84306796f Rewrite Sabre interfaces to be Rust native (#14317) * Add further creation and destructuring methods to `NLayout` These are to allow more efficient Rust-space use of the object, allowing reallocations to be avoided when doing things like ancilla... push web-flow github
87.75
See All Builds (14018)