qiskit 1.3.1__cp39-abi3-win32.whl → 1.3.2__cp39-abi3-win32.whl

qiskit/circuit/library/overlap.py

@@ -128,6 +128,7 @@ def unitary_overlap(
     **Reference Circuit:**
 
     .. plot::
+        :alt: Circuit diagram output by the previous code.
         :include-source:
 
         import numpy as np

qiskit/circuit/library/phase_estimation.py

@@ -76,6 +76,7 @@ class PhaseEstimation(QuantumCircuit):
 
         Reference Circuit:
             .. plot::
+               :alt: Diagram illustrating the previously described circuit.
 
                from qiskit.circuit import QuantumCircuit
                from qiskit.circuit.library import PhaseEstimation
@@ -131,6 +132,7 @@ def phase_estimation(
     **Reference Circuit:**
 
     .. plot::
+       :alt: Circuit diagram output by the previous code.
        :include-source:
 
        from qiskit.circuit import QuantumCircuit

qiskit/circuit/library/quantum_volume.py

@@ -35,6 +35,7 @@ class QuantumVolume(QuantumCircuit):
     **Reference Circuit:**
 
     .. plot::
+       :alt: Diagram illustrating the previously described circuit.
 
        from qiskit.circuit.library import QuantumVolume
        circuit = QuantumVolume(5, 6, seed=10)
@@ -43,6 +44,7 @@ class QuantumVolume(QuantumCircuit):
     **Expanded Circuit:**
 
     .. plot::
+       :alt: Diagram illustrating the previously described circuit.
 
        from qiskit.circuit.library import QuantumVolume
        from qiskit.visualization.library import _generate_circuit_library_visualization
@@ -150,6 +152,7 @@ def quantum_volume(
     **Reference Circuit:**
 
     .. plot::
+       :alt: Diagram illustrating the previously described circuit.
 
        from qiskit.circuit.library import quantum_volume
        circuit = quantum_volume(5, 6, seed=10)

qiskit/circuit/operation.py

@@ -34,6 +34,7 @@ class Operation(ABC):
         Add a Clifford and a Toffoli gate to a :class:`QuantumCircuit`.
 
         .. plot::
+           :alt: Circuit diagram output by the previous code.
            :include-source:
 
            from qiskit import QuantumCircuit

qiskit/circuit/parameter.py

@@ -41,6 +41,7 @@ class Parameter(ParameterExpression):
         Construct a variable-rotation X gate using circuit parameters.
 
         .. plot::
+           :alt: Circuit diagram output by the previous code.
            :include-source:
 
            from qiskit.circuit import QuantumCircuit, Parameter

qiskit/circuit/parameterexpression.py

@@ -340,7 +340,7 @@ class ParameterExpression:
         either a constant or a second ParameterExpression.
 
         Args:
-            operation: One of operator.{add,sub,mul,truediv}.
+            operation: An operator, such as add, sub, mul, and truediv.
             other: The second argument to be used with self in operation.
             reflected: Optional - The default ordering is "self operator other".
                        If reflected is True, this is switched to "other operator self".

qiskit/circuit/quantumcircuit.py

@@ -835,6 +835,7 @@ class QuantumCircuit:
     Consider the following circuit:
 
     .. plot::
+       :alt: Circuit diagram output by the previous code.
        :include-source:
 
        from qiskit import QuantumCircuit
@@ -887,25 +888,6 @@ class QuantumCircuit:
 
        assert qc.size() == 19
 
-    A particularly important circuit property is known as the circuit :meth:`depth`.  The depth
-    of a quantum circuit is a measure of how many "layers" of quantum gates, executed in
-    parallel, it takes to complete the computation defined by the circuit.  Because quantum
-    gates take time to implement, the depth of a circuit roughly corresponds to the amount of
-    time it takes the quantum computer to execute the circuit.  Thus, the depth of a circuit
-    is one important quantity used to measure if a quantum circuit can be run on a device.
-
-    The depth of a quantum circuit has a mathematical definition as the longest path in a
-    directed acyclic graph (DAG).  However, such a definition is a bit hard to grasp, even for
-    experts.  Fortunately, the depth of a circuit can be easily understood by anyone familiar
-    with playing `Tetris <https://en.wikipedia.org/wiki/Tetris>`_.  Lets see how to compute this
-    graphically:
-
-    .. image:: /source_images/depth.gif
-
-    We can verify our graphical result using :meth:`QuantumCircuit.depth`::
-
-       assert qc.depth() == 9
-
     .. automethod:: count_ops
     .. automethod:: depth
     .. automethod:: get_instructions
@@ -2169,6 +2151,7 @@ class QuantumCircuit:
         Examples:
 
             .. plot::
+               :alt: Circuit diagram output by the previous code.
                :include-source:
 
                from qiskit import QuantumCircuit
@@ -3425,6 +3408,7 @@ class QuantumCircuit:
 
         Example:
             .. plot::
+               :alt: Circuit diagram output by the previous code.
                :include-source:
 
                from qiskit import QuantumRegister, ClassicalRegister, QuantumCircuit
@@ -3484,6 +3468,14 @@ class QuantumCircuit:
     ) -> int:
         """Return circuit depth (i.e., length of critical path).
 
+        The depth of a quantum circuit is a measure of how many
+        "layers" of quantum gates, executed in parallel, it takes to
+        complete the computation defined by the circuit.  Because
+        quantum gates take time to implement, the depth of a circuit
+        roughly corresponds to the amount of time it takes the quantum
+        computer to execute the circuit.
+
+
         .. warning::
             This operation is not well defined if the circuit contains control-flow operations.
 
@@ -4306,6 +4298,7 @@ class QuantumCircuit:
             Create a parameterized circuit and assign the parameters in-place.
 
             .. plot::
+               :alt: Circuit diagram output by the previous code.
                :include-source:
 
                from qiskit.circuit import QuantumCircuit, Parameter
@@ -4321,6 +4314,7 @@ class QuantumCircuit:
             Bind the values out-of-place by list and get a copy of the original circuit.
 
             .. plot::
+               :alt: Circuit diagram output by the previous code.
                :include-source:
 
                from qiskit.circuit import QuantumCircuit, ParameterVector

qiskit/circuit/random/utils.py

@@ -37,6 +37,7 @@ def random_circuit(
     from the set of standard gates in :mod:`qiskit.circuit.library.standard_gates`. For example:
 
     .. plot::
+       :alt: Circuit diagram output by the previous code.
        :include-source:
 
        from qiskit.circuit.random import random_circuit
@@ -295,6 +296,7 @@ def random_clifford_circuit(num_qubits, num_gates, gates="all", seed=None):
     gates from the set of standard gates in :mod:`qiskit.circuit.library.standard_gates`. For example:
 
     .. plot::
+       :alt: Circuit diagram output by the previous code.
        :include-source:
 
        from qiskit.circuit.random import random_clifford_circuit

qiskit/converters/dag_to_circuit.py

@@ -34,6 +34,7 @@ def dag_to_circuit(dag, copy_operations=True):
 
     Example:
         .. plot::
+           :alt: Circuit diagram output by the previous code.
            :include-source:
 
            from qiskit import QuantumRegister, ClassicalRegister, QuantumCircuit

qiskit/primitives/statevector_estimator.py

@@ -49,6 +49,7 @@ class StatevectorEstimator(BaseEstimatorV2):
         ``StatevectorEstimator(seed=123)``.
 
     .. plot::
+        :alt: Output from the previous code.
         :include-source:
 
         from qiskit.circuit import Parameter, QuantumCircuit

qiskit/providers/fake_provider/__init__.py

@@ -29,6 +29,7 @@ Example Usage
 Here is an example of using a simulated backend for transpilation and running.
 
 .. plot::
+   :alt: Output from the previous code.
    :include-source:
 
    from qiskit import QuantumCircuit, transpile

qiskit/pulse/builder.py

@@ -39,6 +39,7 @@ execution. For example, to play a series of pulses on channels is as simple as:
 
 
 .. plot::
+   :alt: Output from the previous code.
    :include-source:
 
    from qiskit import pulse
@@ -61,6 +62,7 @@ statements. For example, below we write a simple program that :func:`play`\s
 a pulse:
 
 .. plot::
+   :alt: Output from the previous code.
    :include-source:
 
    from qiskit import pulse
@@ -90,6 +92,7 @@ state we prepared. This program which mixes circuits and pulses will be
 automatically lowered to be run as a pulse program:
 
 .. plot::
+   :alt: Output from the previous code.
    :include-source:
 
    from math import pi
@@ -273,6 +276,7 @@ Instructions
 Pulse instructions are available within the builder interface. Here's an example:
 
 .. plot::
+   :alt: Output from the previous code.
    :include-source:
 
     from qiskit import pulse
@@ -321,6 +325,7 @@ example an alignment context like :func:`align_right` may
 be used to align all pulses as late as possible in a pulse program.
 
 .. plot::
+   :alt: Output from the previous code.
    :include-source:
 
    from qiskit import pulse
@@ -1165,6 +1170,7 @@ def align_equispaced(duration: int | ParameterExpression) -> Generator[None, Non
     Examples:
 
     .. plot::
+       :alt: Output from the previous code.
        :include-source:
 
         from qiskit import pulse
@@ -1219,6 +1225,7 @@ def align_func(
     Examples:
 
     .. plot::
+       :alt: Output from the previous code.
        :include-source:
 
         import numpy as np
@@ -2043,6 +2050,7 @@ def macro(func: Callable):
     Examples:
 
     .. plot::
+       :alt: Output from the previous code.
        :include-source:
 
         from qiskit import pulse

qiskit/pulse/library/symbolic_pulses.py

@@ -330,6 +330,7 @@ class SymbolicPulse(Pulse):
     without knowing the envelope definition. Now you need to provide the envelope.
 
     .. plot::
+       :alt: Output from the previous code.
        :include-source:
 
         import sympy

qiskit/qasm2/export.py

@@ -314,8 +314,8 @@ def _define_custom_operation(operation, gates_to_define):
     # definition, but still continue to return the given object as the call-site object.
     if operation.base_class in known_good_parameterized:
         parameterized_operation = type(operation)(*_FIXED_PARAMETERS[: len(operation.params)])
-    elif hasattr(operation, "_qasm2_decomposition"):
-        new_op = operation._qasm2_decomposition()
+    elif hasattr(operation, "_qasm_decomposition"):
+        new_op = operation._qasm_decomposition()
         parameterized_operation = operation = new_op.copy(name=_escape_name(new_op.name, "gate_"))
     else:
         parameterized_operation = operation

qiskit/qasm3/__init__.py

@@ -126,6 +126,7 @@ For example, we can define a quantum program using OpenQASM 3, and use :func:`lo
 convert it into a :class:`.QuantumCircuit`:
 
 .. plot::
+    :alt: Circuit diagram output by the previous code.
     :include-source:
 
     import qiskit.qasm3

qiskit/qasm3/exporter.py

@@ -1180,13 +1180,16 @@ class QASM3Builder:
 
         This will also push the gate into the symbol table (if required), including recursively
         defining the gate blocks."""
-        ident = self.symbols.get_gate(instruction.operation)
+        operation = instruction.operation
+        if hasattr(operation, "_qasm_decomposition"):
+            operation = operation._qasm_decomposition()
+        ident = self.symbols.get_gate(operation)
         if ident is None:
-            ident = self.define_gate(instruction.operation)
+            ident = self.define_gate(operation)
         qubits = [self._lookup_bit(qubit) for qubit in instruction.qubits]
         parameters = [
             ast.StringifyAndPray(self._rebind_scoped_parameters(param))
-            for param in instruction.operation.params
+            for param in operation.params
         ]
         if not self.disable_constants:
             for parameter in parameters:

qiskit/quantum_info/operators/symplectic/pauli_list.py

@@ -445,16 +445,14 @@ class PauliList(BasePauli, LinearMixin, GroupMixin):
                 f"Index {ind} is greater than number of qubits"
                 f" in the PauliList ({self.num_qubits})"
             )
-        if len(value) == 1:
-            # Pad blocks to correct size
-            value_x = np.vstack(size * [value.x])
-            value_z = np.vstack(size * [value.z])
-            value_phase = np.vstack(size * [value.phase])
-        elif len(value) == size:
+        if len(value) == size:
             #  Blocks are already correct size
             value_x = value.x
             value_z = value.z
-            value_phase = value.phase
+        elif len(value) == 1:
+            # Pad blocks to correct size
+            value_x = np.vstack(size * [value.x])
+            value_z = np.vstack(size * [value.z])
         else:
             # Blocks are incorrect size
             raise QiskitError(
@@ -465,7 +463,7 @@ class PauliList(BasePauli, LinearMixin, GroupMixin):
         # Build new array by blocks
         z = np.hstack([self.z[:, :ind], value_z, self.z[:, ind:]])
         x = np.hstack([self.x[:, :ind], value_x, self.x[:, ind:]])
-        phase = self.phase + value_phase
+        phase = self.phase + value.phase
 
         return PauliList.from_symplectic(z, x, phase)
 
@@ -1121,6 +1119,8 @@ class PauliList(BasePauli, LinearMixin, GroupMixin):
         Returns:
             PauliList: the constructed PauliList.
         """
+        if isinstance(phase, np.ndarray) and np.ndim(phase) > 1:
+            raise ValueError(f"phase should be at most 1D but has {np.ndim(phase)} dimensions.")
         base_z, base_x, base_phase = cls._from_array(z, x, phase)
         return cls(BasePauli(base_z, base_x, base_phase))
 

qiskit/quantum_info/operators/symplectic/sparse_pauli_op.py

@@ -165,7 +165,16 @@ class SparsePauliOp(LinearOp):
             # move the phase of `pauli_list` to `self._coeffs`
             phase = pauli_list._phase
             count_y = pauli_list._count_y()
-            self._coeffs = np.asarray((-1j) ** (phase - count_y) * coeffs, dtype=coeffs.dtype)
+
+            # Compute exponentiation via integer arithmetic and lookup table to avoid
+            # floating point errors
+            exponent = (phase - count_y) % 4
+            lookup = np.array([1 + 0j, -1j, -1 + 0j, 1j], dtype=coeffs.dtype)
+
+            vals = lookup[exponent]
+            self._coeffs = vals * coeffs
+
+            # Update pauli_list phase
             pauli_list._phase = np.mod(count_y, 4)
             self._pauli_list = pauli_list
 

qiskit/quantum_info/states/statevector.py

@@ -181,6 +181,7 @@ class Statevector(QuantumState, TolerancesMixin):
             Plot one of the Bell states
 
             .. plot::
+               :alt: Output from the previous code.
                :include-source:
 
                 from numpy import sqrt

qiskit/synthesis/arithmetic/multipliers/hrs_cumulative_multiplier.py

@@ -27,6 +27,7 @@ def multiplier_cumulative_h18(
     performs a non-modular multiplication on two 3-qubit sized registers is:
 
     .. plot::
+        :alt: Circuit diagram output by the previous code.
         :include-source:
 
         from qiskit.synthesis.arithmetic import multiplier_cumulative_h18

qiskit/synthesis/arithmetic/multipliers/rg_qft_multiplier.py

@@ -35,6 +35,7 @@ def multiplier_qft_r17(
     For example, on 3 state qubits, a full multiplier is given by:
 
     .. plot::
+        :alt: Circuit diagram output by the previous code.
         :include-source:
 
         from qiskit.synthesis.arithmetic import multiplier_qft_r17

qiskit/synthesis/evolution/product_formula.py

@@ -191,12 +191,6 @@ class ProductFormula(EvolutionSynthesis):
             "preserve_order": self.preserve_order,
         }
 
-    def _normalize_coefficients(
-        self, paulis: list[str | list[int], float | complex | ParameterExpression]
-    ) -> list[str | list[int] | ParameterValueType]:
-        """Ensure the coefficients are real (or parameter expressions)."""
-        return [[(op, qubits, real_or_fail(coeff)) for op, qubits, coeff in ops] for ops in paulis]
-
     def _custom_evolution(self, num_qubits, pauli_rotations):
         """Implement the evolution for the non-standard path.
 

qiskit/synthesis/evolution/suzuki_trotter.py

@@ -18,7 +18,9 @@ import inspect
 import typing
 from collections.abc import Callable
 from itertools import chain
+import numpy as np
 
+from qiskit.circuit.parameterexpression import ParameterExpression
 from qiskit.circuit.quantumcircuit import QuantumCircuit
 from qiskit.quantum_info.operators import SparsePauliOp, Pauli
 from qiskit.utils.deprecation import deprecate_arg
@@ -138,7 +140,7 @@ class SuzukiTrotter(ProductFormula):
 
         .. code-block:: text
 
-            ("X", [0], t), ("ZZ", [0, 1], 2t), ("X", [0], 2)
+            ("X", [0], t), ("ZZ", [0, 1], 2t), ("X", [0], t)
 
         Note that the rotation angle contains a factor of 2, such that that evolution
         of a Pauli :math:`P` over time :math:`t`, which is :math:`e^{itP}`, is represented
@@ -157,7 +159,10 @@ class SuzukiTrotter(ProductFormula):
         time = evolution.time
 
         def to_sparse_list(operator):
-            paulis = (time * (2 / self.reps) * operator).to_sparse_list()
+            paulis = [
+                (pauli, indices, real_or_fail(coeff) * time * 2 / self.reps)
+                for pauli, indices, coeff in operator.to_sparse_list()
+            ]
             if not self.preserve_order:
                 return reorder_paulis(paulis)
 
@@ -171,9 +176,6 @@ class SuzukiTrotter(ProductFormula):
             # here would be the location to do so.
             non_commuting = [[op] for op in to_sparse_list(operators)]
 
-        # normalize coefficients, i.e. ensure they are float or ParameterExpression
-        non_commuting = self._normalize_coefficients(non_commuting)
-
         # we're already done here since Lie Trotter does not do any operator repetition
         product_formula = self._recurse(self.order, non_commuting)
         flattened = self.reps * list(chain.from_iterable(product_formula))
@@ -213,3 +215,18 @@ class SuzukiTrotter(ProductFormula):
                 ],
             )
             return outer + inner + outer
+
+
+def real_or_fail(value, tol=100):
+    """Return real if close, otherwise fail. Unbound parameters are left unchanged.
+
+    Based on NumPy's ``real_if_close``, i.e. ``tol`` is in terms of machine precision for float.
+    """
+    if isinstance(value, ParameterExpression):
+        return value
+
+    abstol = tol * np.finfo(float).eps
+    if abs(np.imag(value)) < abstol:
+        return np.real(value)
+
+    raise ValueError(f"Encountered complex value {value}, but expected real.")

qiskit/transpiler/__init__.py

@@ -33,6 +33,8 @@ branches, and other complex behaviors. That being said, the standard
 compilation flow follows the structure given below:
 
 .. image:: /source_images/transpiling_core_steps.png
+   :alt: The transpilation process takes the input circuit, applies the transpilation \
+      passes, then produces the output circuit.
 
 .. raw:: html
 
@@ -331,7 +333,8 @@ example 3 qubit :class:`~.Target` above:
 
 .. plot::
    :include-source:
-
+   :alt: Output from the previous code.
+   
    from qiskit.circuit import Parameter, Measure
    from qiskit.transpiler import Target, InstructionProperties
    from qiskit.circuit.library import UGate, RZGate, RXGate, RYGate, CXGate, CZGate
@@ -390,6 +393,7 @@ see the individual connectivity, you can pass the operation name to
 :meth:`.CouplingMap.build_coupling_map`:
 
 .. plot::
+   :alt: Output from the previous code.
    :include-source:
 
    from qiskit.circuit import Parameter, Measure
@@ -445,6 +449,7 @@ see the individual connectivity, you can pass the operation name to
    target.build_coupling_map('cx').draw()
 
 .. plot::
+   :alt: Output from the previous code.
    :include-source:
 
    from qiskit.circuit import Parameter, Measure
@@ -532,6 +537,7 @@ Every quantum circuit run on the target device must be expressed using only thes
 For example, to run a simple phase estimation circuit:
 
 .. plot::
+   :alt: Circuit diagram output by the previous code.
    :include-source:
 
    import numpy as np
@@ -557,6 +563,7 @@ the target IBM Quantum device (the :class:`~.GenericBackendV2` class generates
 a fake backend with a specified number of qubits for test purposes):
 
 .. plot::
+   :alt: Circuit diagram output by the previous code.
    :include-source:
 
    from qiskit import transpile
@@ -608,6 +615,7 @@ It is important to highlight two special cases:
       ['id', 'rz', 'sx', 'x', 'cx', 'measure', 'delay']
 
    .. plot:
+      :alt: Circuit diagram output by the previous code.
       :include-source:
 
       from qiskit.circuit import QuantumCircuit
@@ -628,6 +636,7 @@ It is important to highlight two special cases:
    this gate must be decomposed.  This decomposition is quite costly:
 
    .. plot::
+      :alt: Circuit diagram output by the previous code.
       :include-source:
 
       from qiskit.circuit import QuantumCircuit
@@ -653,6 +662,7 @@ qubits used in computations.  We need to be able to map these virtual qubits in
 manner to the "physical" qubits in an actual quantum device.
 
 .. image:: /source_images/mapping.png
+   :alt: Diagram illustrating how virtual qubits are mapped to physical qubits.
 
 
 By default, qiskit will do this mapping for you.  The choice of mapping depends on the
@@ -700,6 +710,7 @@ and we can view this layout selection graphically using
 :func:`qiskit.visualization.plot_circuit_layout`:
 
 .. plot::
+   :alt: Circuit diagram output by the previous code.
    :include-source:
 
    from qiskit import QuantumCircuit, transpile
@@ -718,6 +729,7 @@ and we can view this layout selection graphically using
 - **Layout Using Optimization Level 0**
 
    .. plot::
+      :alt: Output from the previous code.
       :include-source:
 
       from qiskit import QuantumCircuit, transpile
@@ -737,6 +749,7 @@ and we can view this layout selection graphically using
 - **Layout Using Optimization Level 3**
 
    .. plot::
+      :alt: Output from the previous code.
       :include-source:
 
       from qiskit import QuantumCircuit, transpile
@@ -760,6 +773,7 @@ keyword argument, where the index labels the virtual qubit in the circuit and th
 corresponding value is the label for the physical qubit to map onto:
 
 .. plot::
+   :alt: Output from the previous code.
    :include-source:
 
    from qiskit import QuantumCircuit, transpile
@@ -807,6 +821,7 @@ In order to highlight this, we run a GHZ circuit 100 times, using a "bad" (disco
 ``initial_layout`` in a heavy hex coupling map:
 
 .. plot::
+   :alt: Diagram illustrating the previously described circuit.
 
    from qiskit import QuantumCircuit, transpile
 
@@ -816,6 +831,7 @@ In order to highlight this, we run a GHZ circuit 100 times, using a "bad" (disco
    ghz.draw(output='mpl')
 
 .. plot::
+   :alt: Output from the previous code.
    :include-source:
 
    import matplotlib.pyplot as plt
@@ -888,6 +904,7 @@ setting the optimization level higher:
 
 
 .. plot::
+   :alt: Diagram illustrating the previously described circuit.
 
    import matplotlib.pyplot as plt
    from qiskit import QuantumCircuit, transpile
@@ -900,6 +917,7 @@ setting the optimization level higher:
    ghz.draw(output='mpl')
 
 .. plot::
+   :alt: Output from the previous code.
    :include-source:
 
    import matplotlib.pyplot as plt
@@ -946,6 +964,7 @@ for idle time on the qubits between the execution of instructions. For example,
 circuit such as:
 
 .. plot::
+   :alt: Diagram illustrating the previously described circuit.
 
    from qiskit import QuantumCircuit
 
@@ -957,6 +976,7 @@ circuit such as:
 we can then call :func:`~.transpile` on it with ``scheduling_method`` set:
 
 .. plot::
+   :alt: Circuit diagram output by the previous code.
    :include-source:
 
    from qiskit import QuantumCircuit, transpile
@@ -976,6 +996,7 @@ account for idle time on each qubit. To get a better idea of the timing of the c
 also look at it with the :func:`.timeline.draw` function:
 
 .. plot::
+   :alt: Output from circuit timeline drawer.
 
    from qiskit.visualization.timeline import draw as timeline_draw
 

qiskit/transpiler/layout.py

@@ -455,6 +455,7 @@ class TranspileLayout:
     let the input circuit be:
 
     .. plot::
+       :alt: Circuit diagram output by the previous code.
        :include-source:
 
        from qiskit.circuit import QuantumCircuit, QuantumRegister
@@ -470,6 +471,7 @@ class TranspileLayout:
     Suppose that during the layout stage the transpiler reorders the qubits to be:
 
     .. plot::
+       :alt: Circuit diagram output by the previous code.
        :include-source:
 
        from qiskit import QuantumCircuit
@@ -498,6 +500,7 @@ class TranspileLayout:
     becomes:
 
     .. plot::
+       :alt: Circuit diagram output by the previous code.
        :include-source:
 
        from qiskit import QuantumCircuit

qiskit/transpiler/passes/routing/star_prerouting.py

@@ -89,6 +89,7 @@ class StarPreRouting(TransformationPass):
     For example:
 
       .. plot::
+         :alt: Circuit diagram output by the previous code.
          :include-source:
 
          from qiskit.circuit import QuantumCircuit

qiskit/transpiler/passes/scheduling/dynamical_decoupling.py

@@ -47,6 +47,7 @@ class DynamicalDecoupling(TransformationPass):
     (including global phase).
 
     .. plot::
+       :alt: Output from the previous code.
        :include-source:
 
         import numpy as np