Qiskit / qiskit
89%
main: 88%

LAST BUILD BRANCH: dynamic_range_expr
DEFAULT BRANCH: main
Repo Added
Files 876
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-14177-6b844e85ddd09159f06e54f1c43e8416c85b1e5c
branch: gh-readonly-queue/main/pr-14177-6b844e85ddd09159f06e54f1c43e8416c85b1e5c
CHANGE BRANCH
x

coverage: 88.709% (+0.02%) from 88.69%
15026896607

push

github

web-flow 
Port disjoint layout utils in rust (#14177)

* Port disjoint layout utils in rust

This commit ports the disjoint layout utils into rust. The eventual goal
of this is to enable porting the full DenseLayout and SabreLayout pass
to rust so it's a standalone function. This will enable us exposing
these passes as a C function. Since the eventual goal of this
functionality is to expose it as a C function this attempts to do as
much as possible without a py token. A standalone rust entrypoint is
added which will serve as what is called from the standalone rust passes
in the future, this is then wrapped in a python entrypoint.

If we have a target that can't build a coupling map from Rust the
disjoint utils return None. This could be because the target could be
global and not have any connectivity constraints, or it could be caused
by having a FakeTarget that doesn't expose certain constraints to rust.
This commit fixes this by falling back to the coupling map python path
in these cases since we can get the python coupling map and use the
python version of the disjoint utils.

* Improve ergonomics of rust interface

* Run rustfmt

* Remove stale comment

* Use Graph instead of StableGraph and UnGraph for coupling

This commit moves to using a regular Graph instead of StableGraph
internally in the disjoint utils. We are never removing nodes from
interaction graphs or coupling graphs so we don't need index stability
on removals and using Graph avoids the overhead for tracking the free
list. Additionally we can use undirected graphs for the coupling graph
since we don't have physical gates defined in the layout stage because
we need to pick the qubits first before we can worry about the
directionality of the gates selected. The one caveat with this is the
CouplingMap in Python is directed so we need to add the reverse edge
when making the coupling map object in Python to ensure we're not
representing things differently.

* Remove python implementation of disjoi... (continued)

434 of 480 new or added lines in 7 files covered. (90.42%)

8 existing lines in 3 files now uncovered.

76379 of 86101 relevant lines covered (88.71%)

427087.62 hits per line

Relevant lines Covered
86101 RELEVANT LINES 76379 COVERED LINES
427087.62 HITS PER LINE
Source Files on gh-readonly-queue/main/pr-14177-6b844e85ddd09159f06e54f1c43e8416c85b1e5c

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
15026896607 gh-readonly-queue/main/pr-14177-6b844e85ddd09159f06e54f1c43e8416c85b1e5c Port disjoint layout utils in rust (#14177) * Port disjoint layout utils in rust This commit ports the disjoint layout utils into rust. The eventual goal of this is to enable porting the full DenseLayout and SabreLayout pass to rust so it's a st... push web-flow github
88.71
See All Builds (14532)