Qiskit / qiskit
90%
main: 89%

LAST BUILD BRANCH: unitary_synth
DEFAULT BRANCH: main
Repo Added
Files 913
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-12215-a41690d6075ac9438ff01b2346a35aa21dc3a568
branch: gh-readonly-queue/main/pr-12215-a41690d6075ac9438ff01b2346a35aa21dc3a568
CHANGE BRANCH
x

coverage: 89.544% (+0.002%) from 89.542%
8914426086

push

github

web-flow 
Support `Var` in circuit-substitution methods (#12215)

* Support `Var` in `QuantumCircuit.compose`

This converts the operation-rewriting step of `QuantumCircuit.compose`
into one that can recurse through control-flow operations rewriting
variables (to avoid conflicts). This initial commit adds two ways of
combining the variables:

1. variables in the `other` are disjoint from those in `self`, and are
   simply added to them.  This makes it easy to join unrelated circuits.
2. variables marked as "captures" in `other` can be inlined onto
   existing variables in `self`.  This makes it possible to build up a
   circuit with variables layer-by-layer.

In support of objective 2, I also taught `copy_empty_like` a way to
produce a new base layer with all the declared variables converted to
"captures" to make it easier to produce new base layers.

I deliberately did not include any _automatic_ variable renaming because
the usability of that seemed very hard to do well; while the circuit can
easily be created in a unique way, the user would then be hard-pressed
to actually retrieve the new `Var` nodes afterwards.  Asking the user to
manually break naming collisions guarantees that they'll be able to find
their variables again afterwards.

* Support `Var` in `DAGCircuit.compose`

This similarly adds support for a `vars_mode` argument to
`DAGCircuit.copy_empty_like` to make using this more convenient.  It
threads the same argument through some of the `DAGCircuit` methods that
build up layers of DAGs, since this is more common here.

Unlike `QuantumCircuit.compose`, `DAGCircuit.compose` does not (yet?)
offer the ability to remap variables during the composition, because the
use-cases for direct `DAGCircuit` composition are typically less about
building up many circuits from scratch and more about rebuilding a DAG
from itself.  Not offering the option makes it simpler to implement.

* Support `Var` in `DAGCircuit.replace_block_with_op`

This is straightforwards,... (continued)

146 of 150 new or added lines in 5 files covered. (97.33%)

25 existing lines in 3 files now uncovered.

61572 of 68762 relevant lines covered (89.54%)

216633.34 hits per line

Relevant lines Covered
68762 RELEVANT LINES 61572 COVERED LINES
216633.34 HITS PER LINE
Source Files on gh-readonly-queue/main/pr-12215-a41690d6075ac9438ff01b2346a35aa21dc3a568

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
8914426086 gh-readonly-queue/main/pr-12215-a41690d6075ac9438ff01b2346a35aa21dc3a568 Support `Var` in circuit-substitution methods (#12215) * Support `Var` in `QuantumCircuit.compose` This converts the operation-rewriting step of `QuantumCircuit.compose` into one that can recurse through control-flow operations rewriting variabl... push web-flow github
89.54
See All Builds (9024)