Qiskit / qiskit
89%
main: 88%

LAST BUILD BRANCH: struct-eq
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/stable/1.4/pr-14108-2df128f8697d89a86f89349fffb1bf97af2a629a
branch: gh-readonly-queue/stable/1.4/pr-14108-2df128f8697d89a86f89349fffb1bf97af2a629a
CHANGE BRANCH
x

coverage: 88.802% (+0.01%) from 88.789%
14202845288

push

github

web-flow 
Fix handling of custom gates named unitary in Split2qUnitaries (#14108)

Normally creating a custom gate class that overloads the name of a
Qiskit defined operation is not valid and not allowed. The names have
meaning and are often used as identifiers and this overloading the name
will prevent Qiskit from correctly identifying an operation. However as
was discovered in #14103 there are some paths available around
serialization and I/O where Qiskit does this itself. For example, qasm
(both 2 and 3) is a lossy serialization format and qasm2 doesn't have a
representation of a UnitaryGate. So when the qasm2 exporter encounteres
a `UnitaryGate` it is serialized as a custom gate definition with the
name "unitary" in the output qasm2 and the definition is a decomposition
of the unitary from the `UnitaryGate`. When that qasm2 program is
subsequently deserialized by qiskit parser the custom gate named "unitary"
is added as a `_DefinedGate` subclass which includes an `__array__`
implementation which computes the unitary from the definition using
the quantum info Operator class. This makes the custom gate parsed from
qasm2 look like a `UnitaryGate` despite not actually one so this is
typically fine for most use cases. However, if you then qpy serialize
the circuit that contains a custom `_DefinedGate` instance that's named
"unitary", QPY doesn't understand what `_DefinedGate` is and assumes that
it can not fully recreate it because it's outside the standard Qiskit data
model. In these cases qpy serializes the fields from the standard data
model defined in Qiskit which it knows about: name, params, definition, etc
and encodes that as a custom gate. When deserializing that custom gate it
populates the standard fields, but anything defined outside of that is
lost through the serialization because it's defined outside of Qiskit.
This means the custom `__array__` implementation is missing from the
qpy round-tripped, previously qasm2 round-tripped, `UnitaryGate`
insta... (continued)

3 of 3 new or added lines in 1 file covered. (100.0%)

5 existing lines in 2 files now uncovered.

79448 of 89466 relevant lines covered (88.8%)

354695.81 hits per line

Relevant lines Covered
89466 RELEVANT LINES 79448 COVERED LINES
354695.81 HITS PER LINE
Source Files on gh-readonly-queue/stable/1.4/pr-14108-2df128f8697d89a86f89349fffb1bf97af2a629a

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
14202845288 gh-readonly-queue/stable/1.4/pr-14108-2df128f8697d89a86f89349fffb1bf97af2a629a Fix handling of custom gates named unitary in Split2qUnitaries (#14108) Normally creating a custom gate class that overloads the name of a Qiskit defined operation is not valid and not allowed. The names have meaning and are often used as identif... push web-flow github
88.8
See All Builds (13944)