z iV  dSrSSKJr SSKrSSKrSSKrSSKrSSK r SSK r SSKJ r SSK J r J r JrJrJrJrJrJrJrJrJrJr SSKJr SSKrSSKJr SSKJr SS KJr SS K J!r! SS K"J#r# SS K$J%r% SS K&J'r' SSK(J)r) SSK*J+r+ SSK,J-r-J.r. SSK/J0r0J1r1J2r2J3r3J4r4J5r5J6r6J7r7 SSK/J8r8 SSK9J:r:J;r; SSKr> SSK?J@r@JArA SSKBJCrCJDrD SSKEJFrFJGrG SSKHJIrIJJrJ SSKKJLrLJMrM SSKNJOrOJPrP SSKQJRrRJSrS SSKTJUrUJVrV SSKWJXrXJYrY SSKZJ[r[ SS K\J]r] SS!K^J_r_ SS"K`Jara SS#KbJcrcJdrd SS$KeJfrf SS%KgJhrh \ R(aSSKjrjSS&KkJlrl SS'KmJnrn SS(KoJprp SS)KqJrrr \"S*5rs\"S+5rt\ \2\1\u\v\\ \2\u44rw\ \5\6\u\v\\ \5\u44rx\"S,\2\55ry"S-S.5rz"S/S0\=5r{S3S1jr|S2r}g)4zQuantum circuit object.) annotationsN) OrderedDict) UnionOptionalTupleTypeTypeVarSequenceCallableMappingIterableAnyLiteraloverload)pi) CircuitData) StandardGate) BitLocations)compute_estimated_duration) QiskitError) Instruction)Gate) Parameter) CircuitError)deprecate_func deprecate_arg)BitQuantumRegisterQubitAncillaRegister AncillaQubitClbitClassicalRegisterRegister)_classical_resource_map) ControlFlowOp_builder_utils)CircuitScopeInterfaceControlFlowBuilderBlock) BreakLoopOpBreakLoopPlaceholder)BoxOp BoxContext)ContinueLoopOpContinueLoopPlaceholder) ForLoopOpForLoopContext)IfElseOp IfContext) SwitchCaseOp SwitchContext) WhileLoopOpWhileLoopContext)exprtypes)ParameterExpressionParameterValueType) ParameterView)ParameterVector)InstructionSet) Operation)QuantumCircuitDataCircuitInstruction)Delay)Store) AnnotationTranspileLayout) BaseOperator) StatevectorSTBitTypec\rSrSrSrSrSrSSSSSSS.SSjjr\\ "S S S S 9S 55r \ RSSj5r \\ "S S S S 9S55r \ RS5r \ GSGSSjj5r\SSSSSS.GSSjj5r\GSSj5r\GSSj5r\RGSSj5r\GSSj5r\GSSj5r\RGSSj5rGS SjrGS SjrGS Sjr\ S5r\ GS Sj5r\ GS S j5rGS S!jrGSS"jrGS S S#.GSS$jjjrGSS%jrGSS&jrGSGSS'jjr SS(.GSS)jjr!GSGSS*jjr"GSGSS+jjr#GSS SSS,.GSS-jjjr$GSGSS.jjr%\GSS/j5r&\GSS0j5r'\GSS1j5r(\GSS2j5r)\GSS3j5r*\*RGS S4j5r*\GS!S5j5r+\+RGS"S6j5r+\GS#S7j5r,\GS S8j5r-\GS S9j5r.\GS S:j5r/\GS S;j5r0\GS S<j5r1\GS S=j5r2\GS S>j5r3\GS S?j5r4GS$S@jr5GS%SAjr6GS$SBjr7GS%SCjr8GS$SDjr9GS&SEjr:GS$SFjr;GS%SGjrGS(SJjr?GS(SKjr@GS SLjrA\BRGS)SMj5rD\BRGS*SNj5rDSOrD\GS+SPj5rEGS,SQjrFGS-SRjrGGS.GS/SSjjrHGS0S ST.GS1SUjjjrI\BRGS2SVj5rJ\BRGS3SWj5rJGS4SSX.GS5SYjjjrJ\BRGS6SZj5rK\BRGS7GS8S\jj5rKGS7GS9S]jjrKGS:S^jrL\BRGS;S_j5rM\BRGS7GSSbjrN\BRGS?Scj5rO\BRGS7GS@Sdjj5rOGS7GS=SejjrOGSASfjrP\BRGSBSgj5rQ\BRGS7GSCShjj5rQGS7GS=SijjrQGSDSjjrRGSESkjrSGSFSljrTGSFSmjrUGSGSnjrVGSHSojrW\BRGSHSpj5rX\BRGSISqj5rXSrrX\BRGSJSsj5rY\BRGS GSKStjj5rYGS GSESujjrYGSLSvjrZGSMSwjr[GSNSxjr\GSOSyjr]GS0GSPSzjjr^GS0GSQS{jjr_GSRGSSS|jjr`GSTGSUS}jjraS~4GSVSjjrbS4GSWSjjrcGS Sjrd\GS Sj5re\GS Sj5rf\GS Sj5rgGSXSjrhGS SjriGSYSjrjGSGSZSjjrkGS SjrlGS SjrmGS GS[SjjrnGS SS.GS\SjjjroGS SjrpGS]SjrqGS^SjrrGS_SjrsGS`SjrtGSaSjruGSbGScSjjrvGSdGSeSjjrwGSbGScSjjrx\GSfSj5ry\GSgSj5rz\GShSj5r{\{RGSiSj5r{\GSjSj5r|\GS Sj5r}GSkSjr~\CGS7S[S[S.GSlSjjj5r\CGS7S[S[S.GSmSjjj5rGSSS S.GSnSjjjrGS SjrGSbGSoSjjrSS.GSpSjjrGS0GSqSjjrGS_SjrGS0GSrSjjrGS_SjrGSsSjrGStSjrGS0GSuSjjrGS GSvSjjrGSGSwSjjrGSxGSySjjrGSGSzSjjrGS{SjrGS|SjrGS}SjrGS~SjrGS GSSjjrGS0GSuSjjrGSSjrGS GSSjjrGS0GSuSjjrGSSjrGSSjrGS0GSuSjjrGSSjrGSSjrGSSjrGS_SjrGS_SjrGS0GSrSjjrGS0GSrSjjrGSSjrGSSjrGS0GSSjjrGS_SjrGS_SjrGS0GSrSjjrGS_SjrGS_SjrGSSjrGS0GSSjjrGS GSSjjrGS0GSrSjjrGSSjrGS GSSjjr\"SSSS9GSGSSjj5rGS_SjrGS0GSrSjjrGS_SjrGS0GSrSjjrGS0GSSjjrGSSjrGSxGSSjjrGSGSSjjrGS GSSjjrGSSjrGSSjrGSGSSjjrGSSjrGSSjrGSSjrGSSSSS[S.GSSjjjr\BRGSSj5r\BRGSSj5rGSSS.Sjjr\BRGSSj5r\BRGSSj5rGSSS.Sjjr\BRGSSj5r\BRSS.GSSjj5rGSSS.SjjrGS GSSjjr\BRGSSj5r\BRGSSj5rGSSS.SjjrGSSjrGSSjrGSSjrGSSjrGSSjrGSGSSjjrSrg(QuantumCircuituCore Qiskit representation of a quantum circuit. .. note:: For more details setting the :class:`QuantumCircuit` in context of all of the data structures that go with it, how it fits into the rest of the :mod:`qiskit` package, and the different regimes of quantum-circuit descriptions in Qiskit, see the module-level documentation of :mod:`qiskit.circuit`. Example: .. plot:: :include-source: :nofigs: from qiskit import QuantumCircuit # Create a new circuit with two qubits qc = QuantumCircuit(2) # Add a Hadamard gate to qubit 0 qc.h(0) # Perform a controlled-X gate on qubit 1, controlled by qubit 0 qc.cx(0, 1) # Return a text drawing of the circuit. qc.draw() .. code-block:: text ┌───┐ q_0: ┤ H ├──■── └───┘┌─┴─┐ q_1: ─────┤ X ├ └───┘ Circuit attributes ================== :class:`QuantumCircuit` has a small number of public attributes, which are mostly older functionality. Most of its functionality is accessed through methods. A small handful of the attributes are intentionally mutable, the rest are data attributes that should be considered immutable. ============================== ================================================================= Mutable attribute Summary ============================== ================================================================= :attr:`global_phase` The global phase of the circuit, measured in radians. :attr:`metadata` Arbitrary user mapping, which Qiskit will preserve through the transpiler, but otherwise completely ignore. :attr:`name` An optional string name for the circuit. ============================== ================================================================= ============================== ================================================================= Immutable data attribute Summary ============================== ================================================================= :attr:`ancillas` List of :class:`AncillaQubit`\ s tracked by the circuit. :attr:`cregs` List of :class:`ClassicalRegister`\ s tracked by the circuit. :attr:`clbits` List of :class:`Clbit`\ s tracked by the circuit. :attr:`data` List of individual :class:`CircuitInstruction`\ s that make up the circuit. :attr:`duration` Total duration of the circuit, added by scheduling transpiler passes. This attribute is deprecated and :meth:`.estimate_duration` should be used instead. :attr:`layout` Hardware layout and routing information added by the transpiler. :attr:`num_ancillas` The number of ancilla qubits in the circuit. :attr:`num_clbits` The number of clbits in the circuit. :attr:`num_captured_vars` Number of captured real-time classical variables. :attr:`num_captured_stretches` Number of captured stretches. :attr:`num_declared_vars` Number of locally declared real-time classical variables in the outer circuit scope. :attr:`num_declared_stretches` Number of locally declared stretches in the outer circuit scope. :attr:`num_input_vars` Number of input real-time classical variables. :attr:`num_parameters` Number of compile-time :class:`Parameter`\ s in the circuit. :attr:`num_qubits` Number of qubits in the circuit. :attr:`num_vars` Total number of real-time classical variables in the outer circuit scope. :attr:`num_stretches` Total number of stretches in the outer circuit scope. :attr:`num_identifiers` Total number of both variables and stretches in the outer circuit. :attr:`op_start_times` Start times of scheduled operations, added by scheduling transpiler passes. :attr:`parameters` Ordered set-like view of the compile-time :class:`Parameter`\ s tracked by the circuit. :attr:`qregs` List of :class:`QuantumRegister`\ s tracked by the circuit. :attr:`qubits` List of :class:`Qubit`\ s tracked by the circuit. :attr:`unit` The unit of the :attr:`duration` field. ============================== ================================================================= The core attribute is :attr:`data`. This is a sequence-like object that exposes the :class:`CircuitInstruction`\ s contained in an ordered form. You generally should not mutate this object directly; :class:`QuantumCircuit` is only designed for append-only operations (which should use :meth:`append`). Most operations that mutate circuits in place should be written as transpiler passes (:mod:`qiskit.transpiler`). .. autoattribute:: data Alongside the :attr:`data`, the :attr:`global_phase` of a circuit can have some impact on its output, if the circuit is used to describe a :class:`.Gate` that may be controlled. This is measured in radians and is directly settable. .. autoattribute:: global_phase The :attr:`name` of a circuit becomes the name of the :class:`~.circuit.Instruction` or :class:`.Gate` resulting from :meth:`to_instruction` and :meth:`to_gate` calls, which can be handy for visualizations. .. autoattribute:: name You can attach arbitrary :attr:`metadata` to a circuit. No part of core Qiskit will inspect this or change its behavior based on metadata, but it will be faithfully passed through the transpiler, so you can tag your circuits yourself. When serializing a circuit with QPY (see :mod:`qiskit.qpy`), the metadata will be JSON-serialized and you may need to pass a custom serializer to handle non-JSON-compatible objects within it (see :func:`.qpy.dump` for more detail). This field is ignored during export to OpenQASM 2 or 3. .. autoattribute:: metadata :class:`QuantumCircuit` exposes data attributes tracking its internal quantum and classical bits and registers. These appear as Python :class:`list`\ s, but you should treat them as immutable; changing them will *at best* have no effect, and more likely will simply corrupt the internal data of the :class:`QuantumCircuit`. .. autoattribute:: qregs .. autoattribute:: cregs .. autoattribute:: qubits .. autoattribute:: ancillas .. autoattribute:: clbits The :ref:`compile-time parameters ` present in instructions on the circuit are available in :attr:`parameters`. This has a canonical order (mostly lexical, except in the case of :class:`.ParameterVector`), which matches the order that parameters will be assigned when using the list forms of :meth:`assign_parameters`, but also supports :class:`set`-like constant-time membership testing. .. autoattribute:: parameters If you have transpiled your circuit, so you have a physical circuit, you can inspect the :attr:`layout` attribute for information stored by the transpiler about how the virtual qubits of the source circuit map to the hardware qubits of your physical circuit, both at the start and end of the circuit. .. autoattribute:: layout If your circuit was also *scheduled* as part of a transpilation, it will expose the individual timings of each instruction, along with the total :attr:`duration` of the circuit. .. autoattribute:: duration .. autoattribute:: unit .. autoattribute:: op_start_times Finally, :class:`QuantumCircuit` exposes several simple properties as dynamic read-only numeric attributes. .. autoattribute:: num_ancillas .. autoattribute:: num_clbits .. autoattribute:: num_captured_vars .. autoattribute:: num_captured_stretches .. autoattribute:: num_declared_vars .. autoattribute:: num_declared_stretches .. autoattribute:: num_input_vars .. autoattribute:: num_identifiers .. autoattribute:: num_parameters .. autoattribute:: num_qubits .. autoattribute:: num_stretches .. autoattribute:: num_vars Creating new circuits ===================== ========================= ===================================================================== Method Summary ========================= ===================================================================== :meth:`__init__` Default constructor of no-instruction circuits. :meth:`copy` Make a complete copy of an existing circuit. :meth:`copy_empty_like` Copy data objects from one circuit into a new one without any instructions. :meth:`from_instructions` Infer data objects needed from a list of instructions. :meth:`from_qasm_file` Legacy interface to :func:`.qasm2.load`. :meth:`from_qasm_str` Legacy interface to :func:`.qasm2.loads`. ========================= ===================================================================== The default constructor (``QuantumCircuit(...)``) produces a circuit with no initial instructions. The arguments to the default constructor can be used to seed the circuit with quantum and classical data storage, and to provide a name, global phase and arbitrary metadata. All of these fields can be expanded later. .. automethod:: __init__ If you have an existing circuit, you can produce a copy of it using :meth:`copy`, including all its instructions. This is useful if you want to keep partial circuits while extending another, or to have a version you can mutate in-place while leaving the prior one intact. .. automethod:: copy Similarly, if you want a circuit that contains all the same data objects (bits, registers, variables, etc) but with none of the instructions, you can use :meth:`copy_empty_like`. This is quite common when you want to build up a new layer of a circuit to then use apply onto the back with :meth:`compose`, or to do a full rewrite of a circuit's instructions. .. automethod:: copy_empty_like In some cases, it is most convenient to generate a list of :class:`.CircuitInstruction`\ s separately to an entire circuit context, and then to build a circuit from this. The :meth:`from_instructions` constructor will automatically capture all :class:`.Qubit` and :class:`.Clbit` instances used in the instructions, and create a new :class:`QuantumCircuit` object that has the correct resources and all the instructions. .. automethod:: from_instructions :class:`QuantumCircuit` also still has two constructor methods that are legacy wrappers around the importers in :mod:`qiskit.qasm2`. These automatically apply :ref:`the legacy compatibility settings ` of :func:`~.qasm2.load` and :func:`~.qasm2.loads`. .. automethod:: from_qasm_file .. automethod:: from_qasm_str Data objects on circuits ======================== .. _circuit-adding-data-objects: Adding data objects ------------------- ============================= ================================================================= Method Adds this kind of data ============================= ================================================================= :meth:`add_bits` :class:`.Qubit`\ s and :class:`.Clbit`\ s. :meth:`add_register` :class:`.QuantumRegister` and :class:`.ClassicalRegister`. :meth:`add_var` :class:`~.expr.Var` nodes with local scope and initializers. :meth:`add_stretch` :class:`~.expr.Stretch` nodes with local scope. :meth:`add_input` :class:`~.expr.Var` nodes that are treated as circuit inputs. :meth:`add_capture` :class:`~.expr.Var` or :class:`~.expr.Stretch` nodes captured from containing scopes. :meth:`add_uninitialized_var` :class:`~.expr.Var` nodes with local scope and undefined state. ============================= ================================================================= Typically you add most of the data objects (:class:`.Qubit`, :class:`.Clbit`, :class:`.ClassicalRegister`, etc) to the circuit as part of using the :meth:`__init__` default constructor, or :meth:`copy_empty_like`. However, it is also possible to add these afterwards. Typed classical data, such as standalone :class:`~.expr.Var` nodes (see :ref:`circuit-repr-real-time-classical`), can be both constructed and added with separate methods. New registerless :class:`.Qubit` and :class:`.Clbit` objects are added using :meth:`add_bits`. These objects must not already be present in the circuit. You can check if a bit exists in the circuit already using :meth:`find_bit`. .. automethod:: add_bits Registers are added to the circuit with :meth:`add_register`. In this method, it is not an error if some of the bits are already present in the circuit. In this case, the register will be an "alias" over the bits. This is not generally well-supported by hardware backends; it is probably best to stay away from relying on it. The registers a given bit is in are part of the return of :meth:`find_bit`. .. automethod:: add_register :ref:`Real-time, typed classical data ` is represented on the circuit by :class:`~.expr.Var` nodes with a well-defined :class:`~.types.Type`. It is possible to instantiate these separately to a circuit (see :meth:`.Var.new`), but it is often more convenient to use circuit methods that will automatically manage the types and expression initialization for you. The two most common methods are :meth:`add_var` (locally scoped variables) and :meth:`add_input` (inputs to the circuit). Additionally, the method :meth:`add_stretch` can be used to add stretches to the circuit. .. automethod:: add_var .. automethod:: add_input .. automethod:: add_stretch In addition, there are two lower-level methods that can be useful for programmatic generation of circuits. When working interactively, you will most likely not need these; most uses of :meth:`add_uninitialized_var` are part of :meth:`copy_empty_like`, and most uses of :meth:`add_capture` would be better off using :ref:`the control-flow builder interface `. .. automethod:: add_uninitialized_var .. automethod:: add_capture Working with bits and registers ------------------------------- A :class:`.Bit` instance is, on its own, just a unique handle for circuits to use in their own contexts. If you have got a :class:`.Bit` instance and a circuit, just can find the contexts that the bit exists in using :meth:`find_bit`, such as its integer index in the circuit and any registers it is contained in. .. automethod:: find_bit Similarly, you can query a circuit to see if a register has already been added to it by using :meth:`has_register`. .. automethod:: has_register Working with compile-time parameters ------------------------------------ .. seealso:: :ref:`circuit-compile-time-parameters` A more complete discussion of what compile-time parametrization is, and how it fits into Qiskit's data model. Unlike bits, registers, and real-time typed classical data, compile-time symbolic parameters are not manually added to a circuit. Their presence is inferred by being contained in operations added to circuits and the global phase. An ordered list of all parameters currently in a circuit is at :attr:`QuantumCircuit.parameters`. The most common operation on :class:`.Parameter` instances is to replace them in symbolic operations with some numeric value, or another symbolic expression. This is done with :meth:`assign_parameters`. .. automethod:: assign_parameters The circuit tracks parameters by :class:`.Parameter` instances themselves, and forbids having multiple parameters of the same name to avoid some problems when interoperating with OpenQASM or other external formats. You can use :meth:`has_parameter` and :meth:`get_parameter` to query the circuit for a parameter with the given string name. .. automethod:: has_parameter .. automethod:: get_parameter .. _circuit-real-time-methods: Working with real-time typed classical data ------------------------------------------- .. seealso:: :mod:`qiskit.circuit.classical` Module-level documentation for how the variable-, expression- and type-systems work, the objects used to represent them, and the classical operations available. :ref:`circuit-repr-real-time-classical` A discussion of how real-time data fits into the entire :mod:`qiskit.circuit` data model as a whole. :ref:`circuit-adding-data-objects` The methods for adding new :class:`~.expr.Var` or :class:`~.expr.Stretch` identifiers to a circuit after initialization. You can retrieve identifiers attached to a circuit (e.g. a :class:`~.expr.Var` or :class:`~.expr.Stretch`) by name with methods :meth:`get_var`, :meth:`get_stretch`, or :meth:`get_identifier`. You can also check if a circuit contains a given identifier with :meth:`has_var`, :meth:`has_stretch`, or :meth:`has_identifier`. .. automethod:: get_var .. automethod:: get_stretch .. automethod:: get_identifier .. automethod:: has_var .. automethod:: has_stretch .. automethod:: has_identifier There are also several iterator methods that you can use to get the full set of identifiers tracked by a circuit. At least one of :meth:`iter_input_vars` and :meth:`iter_captured_vars` will be empty, as inputs and captures are mutually exclusive. All of the iterators have corresponding dynamic properties on :class:`QuantumCircuit` that contain their length: :attr:`num_vars`, :attr:`num_stretches`, :attr:`num_input_vars`, :attr:`num_captured_vars`, :attr:`num_captured_stretches`, :attr:`num_declared_vars`, or :attr:`num_declared_stretches`. .. automethod:: iter_vars .. automethod:: iter_stretches .. automethod:: iter_input_vars .. automethod:: iter_captured_vars .. automethod:: iter_captured_stretches .. automethod:: iter_declared_vars .. automethod:: iter_declared_stretches .. _circuit-adding-operations: Adding operations to circuits ============================= You can add anything that implements the :class:`.Operation` interface to a circuit as a single instruction, though most things you will want to add will be :class:`~.circuit.Instruction` or :class:`~.circuit.Gate` instances. .. seealso:: :ref:`circuit-operations-instructions` The :mod:`qiskit.circuit`-level documentation on the different interfaces that Qiskit uses to define circuit-level instructions. .. _circuit-append-compose: Methods to add general operations --------------------------------- These are the base methods that handle adding any object, including user-defined ones, onto circuits. =============== =============================================================================== Method When to use it =============== =============================================================================== :meth:`append` Add an instruction as a single object onto a circuit. :meth:`_append` Same as :meth:`append`, but a low-level interface that elides almost all error checking. :meth:`compose` Inline the instructions from one circuit onto another. :meth:`tensor` Like :meth:`compose`, but strictly for joining circuits that act on disjoint qubits. =============== =============================================================================== :class:`QuantumCircuit` has two main ways that you will add more operations onto a circuit. Which to use depends on whether you want to add your object as a single "instruction" (:meth:`append`), or whether you want to join the instructions from two circuits together (:meth:`compose`). A single instruction or operation appears as a single entry in the :attr:`data` of the circuit, and as a single box when drawn in the circuit visualizers (see :meth:`draw`). A single instruction is the "unit" that a hardware backend might be defined in terms of (see :class:`.Target`). An :class:`~.circuit.Instruction` can come with a :attr:`~.circuit.Instruction.definition`, which is one rule the transpiler (see :mod:`qiskit.transpiler`) will be able to fall back on to decompose it for hardware, if needed. An :class:`.Operation` that is not also an :class:`~.circuit.Instruction` can only be decomposed if it has some associated high-level synthesis method registered for it (see :mod:`qiskit.transpiler.passes.synthesis.plugin`). A :class:`QuantumCircuit` alone is not a single :class:`~.circuit.Instruction`; it is rather more complicated, since it can, in general, represent a complete program with typed classical memory inputs and outputs, and control flow. Qiskit's (and most hardware's) data model does not yet have the concept of re-usable callable subroutines with virtual quantum operands. You can convert simple circuits that act only on qubits with unitary operations into a :class:`.Gate` using :meth:`to_gate`, and simple circuits acting only on qubits and clbits into a :class:`~.circuit.Instruction` with :meth:`to_instruction`. When you have an :class:`.Operation`, :class:`~.circuit.Instruction`, or :class:`.Gate`, add it to the circuit, specifying the qubit and clbit arguments with :meth:`append`. .. automethod:: append :meth:`append` does quite substantial error checking to ensure that you cannot accidentally break the data model of :class:`QuantumCircuit`. If you are programmatically generating a circuit from known-good data, you can elide much of this error checking by using the fast-path appender :meth:`_append`, but at the risk that the caller is responsible for ensuring they are passing only valid data. .. automethod:: _append In other cases, you may want to join two circuits together, applying the instructions from one circuit onto specified qubits and clbits on another circuit. This "inlining" operation is called :meth:`compose` in Qiskit. :meth:`compose` is, in general, more powerful than a :meth:`to_instruction`-plus-:meth:`append` combination for joining two circuits, because it can also link typed classical data together, and allows for circuit control-flow operations to be joined onto another circuit. The downsides to :meth:`compose` are that it is a more complex operation that can involve more rewriting of the operand, and that it necessarily must move data from one circuit object to another. If you are building up a circuit for yourself and raw performance is a core goal, consider passing around your base circuit and having different parts of your algorithm write directly to the base circuit, rather than building a temporary layer circuit. .. automethod:: compose If you are trying to join two circuits that will apply to completely disjoint qubits and clbits, :meth:`tensor` is a convenient wrapper around manually adding bit objects and calling :meth:`compose`. .. automethod:: tensor As some rules of thumb: * If you have a single :class:`.Operation`, :class:`~.circuit.Instruction` or :class:`.Gate`, you should definitely use :meth:`append` or :meth:`_append`. * If you have a :class:`QuantumCircuit` that represents a single atomic instruction for a larger circuit that you want to re-use, you probably want to call :meth:`to_instruction` or :meth:`to_gate`, and then apply the result of that to the circuit using :meth:`append`. * If you have a :class:`QuantumCircuit` that represents a larger "layer" of another circuit, or contains typed classical variables or control flow, you should use :meth:`compose` to merge it onto another circuit. * :meth:`tensor` is wanted far more rarely than either :meth:`append` or :meth:`compose`. Internally, it is mostly a wrapper around :meth:`add_bits` and :meth:`compose`. Some potential pitfalls to beware of: * Even if you re-use a custom :class:`~.circuit.Instruction` during circuit construction, the transpiler will generally have to "unroll" each invocation of it to its inner decomposition before beginning work on it. This should not prevent you from using the :meth:`to_instruction`-plus-:meth:`append` pattern, as the transpiler will improve in this regard over time. * :meth:`compose` will, by default, produce a new circuit for backwards compatibility. This is more expensive, and not usually what you want, so you should set ``inplace=True``. * Both :meth:`append` and :meth:`compose` (but not :meth:`_append`) have a ``copy`` keyword argument that defaults to ``True``. In these cases, the incoming :class:`.Operation` instances will be copied if Qiskit detects that the objects have mutability about them (such as taking gate parameters). If you are sure that you will not re-use the objects again in other places, you should set ``copy=False`` to prevent this copying, which can be a substantial speed-up for large objects. Methods to add standard instructions ------------------------------------ The :class:`QuantumCircuit` class has helper methods to add many of the Qiskit standard-library instructions and gates onto a circuit. These are generally equivalent to manually constructing an instance of the relevent :mod:`qiskit.circuit.library` object, then passing that to :meth:`append` with the remaining arguments placed into the ``qargs`` and ``cargs`` fields as appropriate. The following methods apply special non-unitary :class:`~.circuit.Instruction` operations to the circuit: =============================== ==================================================== :class:`QuantumCircuit` method :mod:`qiskit.circuit` :class:`~.circuit.Instruction` =============================== ==================================================== :meth:`barrier` :class:`Barrier` :meth:`delay` :class:`Delay` :meth:`initialize` :class:`~library.Initialize` :meth:`measure` :class:`Measure` :meth:`reset` :class:`Reset` :meth:`store` :class:`Store` =============================== ==================================================== These methods apply uncontrolled unitary :class:`.Gate` instances to the circuit: =============================== ============================================ :class:`QuantumCircuit` method :mod:`qiskit.circuit.library` :class:`.Gate` =============================== ============================================ :meth:`dcx` :class:`~library.DCXGate` :meth:`ecr` :class:`~library.ECRGate` :meth:`h` :class:`~library.HGate` :meth:`id` :class:`~library.IGate` :meth:`iswap` :class:`~library.iSwapGate` :meth:`ms` :class:`~library.MSGate` :meth:`p` :class:`~library.PhaseGate` :meth:`pauli` :class:`~library.PauliGate` :meth:`prepare_state` :class:`~library.StatePreparation` :meth:`r` :class:`~library.RGate` :meth:`rcccx` :class:`~library.RC3XGate` :meth:`rccx` :class:`~library.RCCXGate` :meth:`rv` :class:`~library.RVGate` :meth:`rx` :class:`~library.RXGate` :meth:`rxx` :class:`~library.RXXGate` :meth:`ry` :class:`~library.RYGate` :meth:`ryy` :class:`~library.RYYGate` :meth:`rz` :class:`~library.RZGate` :meth:`rzx` :class:`~library.RZXGate` :meth:`rzz` :class:`~library.RZZGate` :meth:`s` :class:`~library.SGate` :meth:`sdg` :class:`~library.SdgGate` :meth:`swap` :class:`~library.SwapGate` :meth:`sx` :class:`~library.SXGate` :meth:`sxdg` :class:`~library.SXdgGate` :meth:`t` :class:`~library.TGate` :meth:`tdg` :class:`~library.TdgGate` :meth:`u` :class:`~library.UGate` :meth:`unitary` :class:`~library.UnitaryGate` :meth:`x` :class:`~library.XGate` :meth:`y` :class:`~library.YGate` :meth:`z` :class:`~library.ZGate` =============================== ============================================ The following methods apply :class:`Gate` instances that are also controlled gates, so are direct subclasses of :class:`ControlledGate`: =============================== ====================================================== :class:`QuantumCircuit` method :mod:`qiskit.circuit.library` :class:`.ControlledGate` =============================== ====================================================== :meth:`ccx` :class:`~library.CCXGate` :meth:`ccz` :class:`~library.CCZGate` :meth:`ch` :class:`~library.CHGate` :meth:`cp` :class:`~library.CPhaseGate` :meth:`crx` :class:`~library.CRXGate` :meth:`cry` :class:`~library.CRYGate` :meth:`crz` :class:`~library.CRZGate` :meth:`cs` :class:`~library.CSGate` :meth:`csdg` :class:`~library.CSdgGate` :meth:`cswap` :class:`~library.CSwapGate` :meth:`csx` :class:`~library.CSXGate` :meth:`cu` :class:`~library.CUGate` :meth:`cx` :class:`~library.CXGate` :meth:`cy` :class:`~library.CYGate` :meth:`cz` :class:`~library.CZGate` =============================== ====================================================== Finally, these methods apply particular generalized multiply controlled gates to the circuit, often with eager syntheses. They are listed in terms of the *base* gate they are controlling, since their exact output is often a synthesized version of a gate. =============================== ================================================= :class:`QuantumCircuit` method Base :mod:`qiskit.circuit.library` :class:`.Gate` =============================== ================================================= :meth:`mcp` :class:`~library.PhaseGate` :meth:`mcrx` :class:`~library.RXGate` :meth:`mcry` :class:`~library.RYGate` :meth:`mcrz` :class:`~library.RZGate` :meth:`mcx` :class:`~library.XGate` =============================== ================================================= The rest of this section is the API listing of all the individual methods; the tables above are summaries whose links will jump you to the correct place. .. automethod:: barrier .. automethod:: ccx .. automethod:: ccz .. automethod:: ch .. automethod:: cp .. automethod:: crx .. automethod:: cry .. automethod:: crz .. automethod:: cs .. automethod:: csdg .. automethod:: cswap .. automethod:: csx .. automethod:: cu .. automethod:: cx .. automethod:: cy .. automethod:: cz .. automethod:: dcx .. automethod:: delay .. automethod:: ecr .. automethod:: h .. automethod:: id .. automethod:: initialize .. automethod:: iswap .. automethod:: mcp .. automethod:: mcrx .. automethod:: mcry .. automethod:: mcrz .. automethod:: mcx .. automethod:: measure .. automethod:: ms .. automethod:: p .. automethod:: pauli .. automethod:: prepare_state .. automethod:: r .. automethod:: rcccx .. automethod:: rccx .. automethod:: reset .. automethod:: rv .. automethod:: rx .. automethod:: rxx .. automethod:: ry .. automethod:: ryy .. automethod:: rz .. automethod:: rzx .. automethod:: rzz .. automethod:: s .. automethod:: sdg .. automethod:: store .. automethod:: swap .. automethod:: sx .. automethod:: sxdg .. automethod:: t .. automethod:: tdg .. automethod:: u .. automethod:: unitary .. automethod:: x .. automethod:: y .. automethod:: z .. _circuit-control-flow-methods: Adding control flow to circuits ------------------------------- .. seealso:: :ref:`circuit-control-flow-repr` Discussion of how control-flow operations are represented in the whole :mod:`qiskit.circuit` context. ============================== ================================================================ :class:`QuantumCircuit` method Control-flow instruction ============================== ================================================================ :meth:`if_test` :class:`.IfElseOp` with only a ``True`` body :meth:`if_else` :class:`.IfElseOp` with both ``True`` and ``False`` bodies :meth:`while_loop` :class:`.WhileLoopOp` :meth:`switch` :class:`.SwitchCaseOp` :meth:`for_loop` :class:`.ForLoopOp` :meth:`box` :class:`.BoxOp` :meth:`break_loop` :class:`.BreakLoopOp` :meth:`continue_loop` :class:`.ContinueLoopOp` ============================== ================================================================ :class:`QuantumCircuit` has corresponding methods for all of the control-flow operations that are supported by Qiskit. These have two forms for calling them. The first is a very straightfowards convenience wrapper that takes in the block bodies of the instructions as :class:`QuantumCircuit` arguments, and simply constructs and appends the corresponding :class:`.ControlFlowOp`. The second form, which we strongly recommend you use for constructing control flow, is called *the builder interface*. Here, the methods take only the real-time discriminant of the operation, and return `context managers `__ that you enter using ``with``. You can then use regular :class:`QuantumCircuit` methods within those blocks to build up the control-flow bodies, and Qiskit will automatically track which of the data resources are needed for the inner blocks, building the complete :class:`.ControlFlowOp` as you leave the ``with`` statement. It is far simpler and less error-prone to build control flow programmatically this way. When using the control-flow builder interface, you may sometimes want a qubit to be included in a block, even though it has no operations defined. In this case, you can use the :meth:`noop` method. To check whether a circuit contains a :class:`.ControlFlowOp` you can use the helper method :meth:`.QuantumCircuit.has_control_flow_op`. .. TODO: expand the examples of the builder interface. .. automethod:: box .. automethod:: break_loop .. automethod:: continue_loop .. automethod:: for_loop .. automethod:: if_else .. automethod:: if_test .. automethod:: switch .. automethod:: while_loop .. automethod:: noop .. automethod:: has_control_flow_op Converting circuits to single objects ------------------------------------- As discussed in :ref:`circuit-append-compose`, you can convert a circuit to either an :class:`~.circuit.Instruction` or a :class:`.Gate` using two helper methods. .. automethod:: to_instruction .. automethod:: to_gate Helper mutation methods ----------------------- There are two higher-level methods on :class:`QuantumCircuit` for appending measurements to the end of a circuit. Note that by default, these also add an extra register. .. automethod:: measure_active .. automethod:: measure_all There are two "subtractive" methods on :class:`QuantumCircuit` as well. This is not a use-case that :class:`QuantumCircuit` is designed for; typically you should just look to use :meth:`copy_empty_like` in place of :meth:`clear`, and run :meth:`remove_final_measurements` as its transpiler-pass form :class:`.RemoveFinalMeasurements`. .. automethod:: clear .. automethod:: remove_final_measurements Circuit properties ================== Simple circuit metrics ---------------------- When constructing quantum circuits, there are several properties that help quantify the "size" of the circuits, and their ability to be run on a noisy quantum device. Some of these, like number of qubits, are straightforward to understand, while others like depth and number of tensor components require a bit more explanation. Here we will explain all of these properties, and, in preparation for understanding how circuits change when run on actual devices, highlight the conditions under which they change. Consider the following circuit: .. plot:: :alt: Circuit diagram output by the previous code. :include-source: from qiskit import QuantumCircuit qc = QuantumCircuit(12) for idx in range(5): qc.h(idx) qc.cx(idx, idx+5) qc.cx(1, 7) qc.x(8) qc.cx(1, 9) qc.x(7) qc.cx(1, 11) qc.swap(6, 11) qc.swap(6, 9) qc.swap(6, 10) qc.x(6) qc.draw('mpl') From the plot, it is easy to see that this circuit has 12 qubits, and a collection of Hadamard, CNOT, X, and SWAP gates. But how to quantify this programmatically? Because we can do single-qubit gates on all the qubits simultaneously, the number of qubits in this circuit is equal to the :meth:`width` of the circuit:: assert qc.width() == 12 We can also just get the number of qubits directly using :attr:`num_qubits`:: assert qc.num_qubits == 12 .. important:: For a quantum circuit composed from just qubits, the circuit width is equal to the number of qubits. This is the definition used in quantum computing. However, for more complicated circuits with classical registers, and classically controlled gates, this equivalence breaks down. As such, from now on we will not refer to the number of qubits in a quantum circuit as the width. It is also straightforward to get the number and type of the gates in a circuit using :meth:`count_ops`:: qc.count_ops() .. code-block:: text OrderedDict([('cx', 8), ('h', 5), ('x', 3), ('swap', 3)]) We can also get just the raw count of operations by computing the circuits :meth:`size`:: assert qc.size() == 19 .. automethod:: count_ops .. automethod:: depth .. automethod:: get_instructions .. automethod:: num_connected_components .. automethod:: num_nonlocal_gates .. automethod:: num_tensor_factors .. automethod:: num_unitary_factors .. automethod:: size .. automethod:: width Accessing scheduling information -------------------------------- If a :class:`QuantumCircuit` has been scheduled as part of a transpilation pipeline, the timing information for individual qubits can be accessed. The whole-circuit timing information is available through the :meth:`estimate_duration` method and :attr:`op_start_times` attribute. .. automethod:: estimate_duration .. automethod:: qubit_duration .. automethod:: qubit_start_time .. automethod:: qubit_stop_time .. _circuit-abstract-physical: Abstract and physical circuits ============================== Circuits are a fairly low-level abstraction of quantum algorithms. However, even within this, there are distinctions. Quantum programmers often want to use a wide arrange of gates and instructions, and work in a regime where all qubits and interact with all others. Quantum hardware, however, typically has a restrictive set of native gates, and only certain pairs of hardware qubits can interact. We term these two regimes "abstract circuits" and "physical circuits", respectively. Qiskit has two ways of distinguishing a circuit that is intended to be physical. This is a fuzzy check, for historical reasons; originally, Qiskit never made the distinction at all (which is why :func:`.transpile` is called that, and not called ``compile``!). The most explicit way is through the :attr:`layout` attribute of circuits; if this is set, the circuit is certainly intended to be physical. The older, more implicit, way is the metadata of the :class:`.Qubit` objects and :class:`.QuantumRegister` instances in the circuit. A circuit can only be considered (as judged by several transpiler passes) as physical if it contains exactly one quantum register, which is called ``q`` and owns all the circuit qubits in index order. Again for historical reasons, this is the default for the ``QuantumCircuit(int [, int])`` form of the default constructor. Normally, you create a :class:`QuantumCircuit` and build it in the abstract sense (regardless of the qubit metadata). You then call :func:`.transpile` to compile the circuit into a hardware-supported circuit. However, in cases where you want to write a hardware efficient circuit from the beginning, you can short-circuit the full compilation infrastructure using the :meth:`ensure_physical` method. This will ensure that, no matter how you defined the initial qubit metadata, all requirements for the circuit to be considered physical will be satisfied, with the qubit indices mapped to the hardware qubits. For more complete control over choosing a virtual-to-physical mapping and routing, see :ref:`the layout ` and `routing ` stages of the preset compilation pipelines. .. automethod:: ensure_physical Instruction-like methods ======================== .. These methods really shouldn't be on `QuantumCircuit` at all. They're generally more appropriate as `Instruction` or `Gate` methods. `reverse_ops` shouldn't be a method _full stop_---it was copying a `DAGCircuit` method from an implementation detail of the original `SabreLayout` pass in Qiskit. :class:`QuantumCircuit` also contains a small number of methods that are very :class:`~.circuit.Instruction`-like in detail. You may well find better integration and more API support if you first convert your circuit to an :class:`~.circuit.Instruction` (:meth:`to_instruction`) or :class:`.Gate` (:meth:`to_gate`) as appropriate, then call the corresponding method. .. automethod:: control .. automethod:: inverse .. automethod:: power .. automethod:: repeat .. automethod:: reverse_ops Visualization ============= Qiskit includes some drawing tools to give you a quick feel for what your circuit looks like. This tooling is primarily targeted at producing either a `Matplotlib `__- or text-based drawing. There is also a lesser-featured LaTeX backend for drawing, but this is only for simple circuits, and is not as actively maintained. .. seealso:: :mod:`qiskit.visualization` The primary documentation for all of Qiskit's visualization tooling. .. automethod:: draw In addition to the core :meth:`draw` driver, there are two visualization-related helper methods, which are mostly useful for quickly unwrapping some inner instructions or reversing the :ref:`qubit-labelling conventions ` in the drawing. For more general mutation, including basis-gate rewriting, you should use the transpiler (:mod:`qiskit.transpiler`). .. automethod:: decompose .. automethod:: reverse_bits rcircuitN)name global_phasemetadatainputscaptures declarationsc [SU55(ab[SU55nU(d6[ SUV s/sHn [ U 5R PM sn SUS35e[SU55nSUlU Uc&UR5UlUR5 O,[U[5(d [ S 5eXlXl UR5 [U5UlSUl/Ul['5Ul/UlUR,"U6 SUlX lUHn UR3U 5 M UHn UR5U 5 M [U[65(aUR95nUHupUR;X5 M SUlS UlUc0OUUl g![[4a SnGNf=fs sn f) a Default constructor of :class:`QuantumCircuit`. .. `QuantumCirucit` documents its `__init__` method explicitly, unlike most classes where it's implicitly appended to the class-level documentation, just because the class is so huge and has a lot of introductory material to its class docstring. Args: regs: The registers to be included in the circuit. * If a list of :class:`~.Register` objects, represents the :class:`.QuantumRegister` and/or :class:`.ClassicalRegister` objects to include in the circuit. For example: * ``QuantumCircuit(QuantumRegister(4))`` * ``QuantumCircuit(QuantumRegister(4), ClassicalRegister(3))`` * ``QuantumCircuit(QuantumRegister(4, 'qr0'), QuantumRegister(2, 'qr1'))`` * If a list of ``int``, the amount of qubits and/or classical bits to include in the circuit. It can either be a single int for just the number of quantum bits, or 2 ints for the number of quantum bits and classical bits, respectively. For example: * ``QuantumCircuit(4) # A QuantumCircuit with 4 qubits`` * ``QuantumCircuit(4, 3) # A QuantumCircuit with 4 qubits and 3 classical bits`` * If a list of python lists containing :class:`.Bit` objects, a collection of :class:`.Bit` s to be added to the circuit. name: the name of the quantum circuit. If not set, an automatically generated string will be assigned. global_phase: The global phase of the circuit in radians. metadata: Arbitrary key value metadata to associate with the circuit. This gets stored as free-form data in a dict in the :attr:`~qiskit.circuit.QuantumCircuit.metadata` attribute. It will not be directly used in the circuit. inputs: any variables to declare as ``input`` runtime variables for this circuit. These should already be existing :class:`.expr.Var` nodes that you build from somewhere else; if you need to create the inputs as well, use :meth:`QuantumCircuit.add_input`. The variables given in this argument will be passed directly to :meth:`add_input`. A circuit cannot have both ``inputs`` and ``captures``. captures: any variables that this circuit scope should capture from a containing scope. The variables given here will be passed directly to :meth:`add_capture`. A circuit cannot have both ``inputs`` and ``captures``. declarations: any variables that this circuit should declare and initialize immediately. You can order this input so that later declarations depend on earlier ones (including inputs or captures). If you need to depend on values that will be computed later at runtime, use :meth:`add_var` at an appropriate point in the circuit execution. This argument is intended for convenient circuit initialization when you already have a set of created variables. The variables used here will be directly passed to :meth:`add_var`, which you can use directly if this is the first time you are creating the variable. Raises: CircuitError: if the circuit name, if given, is not valid. CircuitError: if both ``inputs`` and ``captures`` are given. c3b# UH%n[U[[[45(+v M' g7fN) isinstancelistrr$.0regs W/home/james-whalen/.local/lib/python3.13/site-packages/qiskit/circuit/quantumcircuit.py *QuantumCircuit.__init__..hs(_Z^SV:cD/;L#MNNNZ^s-/c3<# UHo[U5:Hv M g7frZintr]s r`rarbls$ECH_sFz-Circuit args must be Registers or integers. (z 'z' was provided)c38# UHn[U5v M g7frZrdr]s r`rarbws2TcSTNzFThe circuit name should be a string (or None to auto-generate a name).dt)!anyall ValueError TypeErrorrtype__name__tuple _base_name _cls_prefix _name_updater[strrR_increment_instances_OuterCircuitScopeInterface _builder_api_op_start_times_control_flow_scopesr_data _ancillas add_register_layoutrS add_input add_capturer itemsadd_var _duration_unitrT)selfrRrSrTrUrVrWregsvalid_reg_sizer_input_capturevarinitials r`__init__QuantumCircuit.__init__sR _Z^_ _ _ '!$$E$E!E""C6:;dsS **d;>0+> )4););Y);L?Xe);FY)4););Y);L?Xe);FY   V $   V $    '    ' OOK ((ZYs7 E E  E'EcUR$)aReturn any associated layout information about the circuit. This attribute contains an optional :class:`~.TranspileLayout` object. This is typically set on the output from :func:`~.transpile` or :meth:`.PassManager.run` to retain information about the permutations caused on the input circuit by transpilation. There are two types of permutations caused by the :func:`~.transpile` function: an initial layout that permutes the qubits based on the selected physical qubits on the :class:`~.Target`, and a final layout, which is an output permutation caused by :class:`~.SwapGate`\ s inserted during routing. Example: .. plot:: :include-source: :nofigs: from qiskit import QuantumCircuit from qiskit.providers.fake_provider import GenericBackendV2 from qiskit.transpiler import generate_preset_pass_manager # Create circuit to test transpiler on qc = QuantumCircuit(3, 3) qc.h(0) qc.cx(0, 1) qc.swap(1, 2) qc.cx(0, 1) # Add measurements to the circuit qc.measure([0, 1, 2], [0, 1, 2]) # Specify the QPU to target backend = GenericBackendV2(3) # Transpile the circuit pass_manager = generate_preset_pass_manager( optimization_level=1, backend=backend ) transpiled = pass_manager.run(qc) # Print the layout after transpilation print(transpiled.layout.routing_permutation()) .. code-block:: text [0, 1, 2] )r|rs r`layoutQuantumCircuit.layout+sh||rc[U5$)aKThe circuit data (instructions and context). Example: .. plot:: :include-source: :nofigs: from qiskit import QuantumCircuit qc = QuantumCircuit(2, 2) qc.measure([0], [1]) print(qc.data) .. code-block:: text [CircuitInstruction(operation=Instruction(name='measure', num_qubits=1, num_clbits=1, params=[]), qubits=(Qubit(QuantumRegister(2, 'q'), 0),), clbits=(Clbit(ClassicalRegister(2, 'c'), 1),))] Returns: A list-like object containing the :class:`.CircuitInstruction` instances in the circuit. )rArs r`rQuantumCircuit.dataas2"$''rcj[U[5(aUR5nO [U5nURR 5 UR UlU(dg[US[5(aUHnURUSS9 M gUHup#nURX#USS9 M g)aHSets the circuit data from a list of instructions and context. Args: data_input (Iterable): A sequence of instructions with their execution contexts. The elements must either be instances of :class:`.CircuitInstruction` (preferred), or a 3-tuple of ``(instruction, qargs, cargs)`` (legacy). In the legacy format, ``instruction`` must be an :class:`~.circuit.Instruction`, while ``qargs`` and ``cargs`` must be iterables of :class:`~.circuit.Qubit` or :class:`.Clbit` specifiers (similar to the allowed forms in calls to :meth:`append`). NrFcopy) r[rrr\ryclearrSrBappend)r data_inputrqargscargss r`rr|s j+ . .#*Jj)J  --  jm%7 8 8)  Ke 4 *.8) E KE B.8rcJURc [S5eUR$)u# Return a list of operation start times. .. note:: This attribute computes the estimate starting time of the operations in the scheduled circuit and only works for simple circuits that have no control flow or other classical feed-forward operations. This attribute is enabled once one of scheduling analysis passes runs on the quantum circuit. Example: .. plot:: :include-source: :nofigs: from qiskit import QuantumCircuit from qiskit.providers.fake_provider import GenericBackendV2 from qiskit.transpiler import generate_preset_pass_manager qc = QuantumCircuit(2) qc.h(0) qc.cx(0, 1) qc.measure_all() # Print the original circuit print("Original circuit:") print(qc) # Transpile the circuit with a specific basis gates list and print the resulting circuit backend = GenericBackendV2(2, basis_gates=['u1', 'u2', 'u3', 'cx']) pm = generate_preset_pass_manager( optimization_level=1, backend=backend, scheduling_method="alap" ) transpiled_qc = pm.run(qc) print("Transpiled circuit with basis gates ['u1', 'u2', 'u3', 'cx']:") print(transpiled_qc) # Print the start times of each instruction in the transpiled circuit print("Start times of instructions in the transpiled circuit:") for instruction, start_time in zip(transpiled_qc.data, transpiled_qc.op_start_times): print(f"{instruction.operation.name}: {start_time}") .. code-block:: text Original circuit: ┌───┐ ░ ┌─┐ q_0: ┤ H ├──■───░─┤M├─── └───┘┌─┴─┐ ░ └╥┘┌─┐ q_1: ─────┤ X ├─░──╫─┤M├ └───┘ ░ ║ └╥┘ meas: 2/══════════════╩══╩═ 0 1 Transpiled circuit with basis gates ['u1', 'u2', 'u3', 'cx']: ┌─────────┐ ░ ┌─────────────────┐┌─┐ q_0 -> 0 ───┤ U2(0,π) ├──────■───░─┤ Delay(1255[dt]) ├┤M├ ┌──┴─────────┴───┐┌─┴─┐ ░ └───────┬─┬───────┘└╥┘ q_1 -> 1 ┤ Delay(196[dt]) ├┤ X ├─░─────────┤M├─────────╫─ └────────────────┘└───┘ ░ └╥┘ ║ meas: 2/═══════════════════════════════════╩══════════╩═ 1 0 Start times of instructions in the transpiled circuit: u2: 0 delay: 0 cx: 196 barrier: 2098 delay: 2098 measure: 3353 measure: 2098 Returns: List of integers representing instruction estimated start times. The index corresponds to the index of instruction in :attr:`QuantumCircuit.data`. Raises: AttributeError: When circuit is not scheduled. znThis circuit is not scheduled. To schedule it run the circuit through one of the transpiler scheduling passes.)rwAttributeErrorrs r`op_start_timesQuantumCircuit.op_start_timess2d    ' b ###rcUR$)aNThe user-provided metadata associated with the circuit. The metadata for the circuit is a user-provided ``dict`` of metadata for the circuit. It will not be used to influence the execution or operation of the circuit, but it is expected to be passed between all transforms of the circuit (i.e., transpilation) and that providers will associate any circuit metadata with the results it returns from execution of that circuit. Example: .. plot:: :include-source: :nofigs: from qiskit import QuantumRegister, ClassicalRegister, QuantumCircuit q = QuantumRegister(2) c = ClassicalRegister(2) qc = QuantumCircuit(q, c) qc.metadata = {'experiment_type': 'Bell state experiment'} print(qc.metadata) .. code-block:: text {'experiment_type': 'Bell state experiment'} ) _metadatars r`rTQuantumCircuit.metadatas>~~rcP[U[5(d [S5eXlg)zUpdate the circuit metadataz2Only a dictionary is accepted for circuit metadataN)r[dictrlr)rrTs r`rTrs"(D))PQ Q!rc2[URSS95$)Ntext)output)rsdrawrs r`__str__QuantumCircuit.__str__s499F9+,,rcX[U[5(dgSSKJn U"USS9U"USS9:H$)NFrcircuit_to_dagcopy_operations)r[rNqiskit.convertersr)rotherrs r`__eq__QuantumCircuit.__eq__s7%00 5dE:n 5?   rc URnURU5nURR5SS1- H1n[ X4[ R "URUU55 M3 [U5UlURRSS9Ul URR[ R "URRU5[ R "URRU5[ R "URRU5[ R "URRU5S9 U$)NryrvT)deepcopy)rrqregscregs) __class____new____dict__keyssetattr_copyrrurvryr replace_bitsrrrr)rmemorresultks r` __deepcopy__QuantumCircuit.__deepcopy__)snnS!##%.(AAA Fu~~dmmA.>E FB:&Azz5  !!>>$**"3"3T:>>$**"3"3T:..!1!148..!1!148 "  rc.U=RS- slgNr instancesrs r`rt#QuantumCircuit._increment_instancesBs  rcUR$)zMReturn the current number of instances of this class, useful for auto naming.rrs r`_cls_instancesQuantumCircuit._cls_instancesFs}}rcUR$)z)Return the prefix to use for auto naming.)prefixrs r`rqQuantumCircuit._cls_prefixLszzrc[R"5cSnO"S[R"5R3nURSUR 5U3Ulg)z-update name of instance using instance numberN-)multiprocessingparent_processcurrent_processpidrprrR)rpid_names r`rrQuantumCircuit._name_updateQsW  ) ) + 3H?::<@@ABH'q)<)<)>(?zJ rcSn[U[5(aXR;aSnU$[U[5(aXR;aSnU$)z Test if this circuit has the register r. Args: register (Register): a quantum or classical register. Returns: bool: True if the register is contained in this circuit. FT)r[rrr$r)rregisterhas_regs r` has_registerQuantumCircuit.has_registerYsN h 0 0X5KG"3 4 4ZZ9OGrrcURnUbX:a[SUSUS35eURbUUbX:wa [S5e[ US5nUR [ U5:wdURU/:wa [S5egU(a`S S KJ n UR R5nUb"X:aUR[ X- S 55 U"[[U555nOSnURRU5 UbIS S KJn U"UUR#5R5SUUR R5S 9Ulg)aPut this circuit into canonical physical form, with the given number of qubits, if it is not already. Several Qiskit transpiler passes only make sense when applied to circuits defined in terms of physical qubits. If you have manually constructed a circuit where the qubit indices correspond to physical qubits, use this function to ensure that the metadata of the circuit matches the canonical physical form. This means replacing the qubit data with a single owning register called ``"q"``, and (optionally) setting the :attr:`layout` field of the circuit to link these physical qubits with the original virtual ones. If the circuit does not already have a layout, this method (with ``apply_layout=True``) is equivalent to applying the full :ref:`trivial layout method ` of the preset compilation pipeline. If the circuit is already canonically physical, nothing happens to it. This method cannot change the number of qubits in the circuit if it already has a :attr:`layout` set. Args: num_qubits: if given, expand the circuit with ancillas up to this size. The ancillas will always be the highest qubit indices of the circuit. If not given (the default), the circuit stays the same width. This option cannot be set if the circuit already as a :attr:`layout`. apply_layout: if true (the default), set the :attr:`layout` attribute of the circuit appropriately so that the circuit appears to have been laid out with the "trivial" layout, including ancilla expansion, for a backend of width ``num_qubits``. This has no effect if the circuit already had a :attr:`layout`. Returns: whether the circuit was modified in order to make it physical. Raises: ValueError: if ``num_qubits`` is too small for the circuit. CircuitError: if ``num_qubits`` is set to attempt to expand the circuit, but the circuit already has a layout set. Nz#cannot have fewer physical qubits (z) than virtual ()z5cannot expand a circuit that already has a set layoutqzThis circuit has a set layout, but its qubits are not in the canonical physical form. This might indicate a faulty layout transpilation stage has been used.Fr)LayoutancillarF)initial_layoutinput_qubit_mapping final_layout_input_qubit_count_output_qubit_listT) num_qubitsrkr|rrrr\rqiskit.transpilerr rextendr enumeratery make_physicalrGget_virtual_bits) rrroriginal_num_qubitsexpectedr virtualsr rGs r`rQuantumCircuit.ensure_physicaljsTH#oo  !j&F5j\B""5!6a9  << #%**K"#Z[[&':C@H{{d8n, xj0H#"   0{{'')H%**J 0PR[ \]#D8)<$=>N!N   ,  % 9*-$2$C$C$E$J$J$L!#6#';;#3#3#5 DLrc*URURS-5n[UR5H9nUR UR UR R5S95 M; URUlURUl U$)u+Reverse the circuit by reversing the order of instructions. This is done by recursively reversing all instructions. It does not invert (adjoint) any gate. Returns: QuantumCircuit: the reversed circuit. Examples: input: .. code-block:: text ┌───┐ q_0: ┤ H ├─────■────── └───┘┌────┴─────┐ q_1: ─────┤ RX(1.57) ├ └──────────┘ output: .. code-block:: text ┌───┐ q_0: ─────■──────┤ H ├ ┌────┴─────┐└───┘ q_1: ┤ RX(1.57) ├───── └──────────┘ _reverse operation) copy_empty_likerRreversedrrreplacer reverse_opsrr)r reverse_circrs r`r!QuantumCircuit.reverse_opss{>++DII ,BC #DII.K  !4!4{?T?T?`?`?b!4!c d/"& !ZZ rc4[[[UR55[[UR55UR UR S9nURSSS2nURSSS2n[UR5H[n[U5Vs/sH oRURU5RPM" nnUR[XdR S95 M] [UR5H[n[U5Vs/sH osURU5RPM" nnUR[XdR S95 M] URHnURVs/sH oRURU5RPM" n nURVs/sH osURU5RPM" n nURUR!XS95 M U$s snfs snfs snfs snf)upReturn a circuit with the opposite order of wires. The circuit is "vertically" flipped. If a circuit is defined over multiple registers, the resulting circuit will have the same registers but with their order flipped. This method is useful for converting a circuit written in little-endian convention to the big-endian equivalent, and vice versa. Returns: QuantumCircuit: the circuit with reversed bit order. Examples: input: .. code-block:: text ┌───┐ a_0: ┤ H ├──■───────────────── └───┘┌─┴─┐ a_1: ─────┤ X ├──■──────────── └───┘┌─┴─┐ a_2: ──────────┤ X ├──■─────── └───┘┌─┴─┐ b_0: ───────────────┤ X ├──■── └───┘┌─┴─┐ b_1: ────────────────────┤ X ├ └───┘ output: .. code-block:: text ┌───┐ b_0: ────────────────────┤ X ├ ┌───┐└─┬─┘ b_1: ───────────────┤ X ├──■── ┌───┐└─┬─┘ a_0: ──────────┤ X ├──■─────── ┌───┐└─┬─┘ a_1: ─────┤ X ├──■──────────── ┌───┐└─┬─┘ a_2: ┤ H ├──■───────────────── └───┘ rRrSN)bitsrRrr)rNr\rrrrRrSrfind_bitindexr{rrr$rrr ) rcirc new_qubit_map new_clbit_mapr_rr'rrrrs r` reverse_bitsQuantumCircuit.reverse_bitss^ $++& ' $++& '**    DbD)  DbD) DJJ'CKSTW=Y=%$--"6"<"<==DY   o4hhG H(DJJ'CKSTW=Y=%$--"6"<"<==DY   /TI J( 99KMXM_M_`M_EDMM%$8$>$>?M_F`MXM_M_`M_EDMM%$8$>$>?M_F` LL,,F,J K% ZZa`s"'H'H 'H9'Hc N[URUR/URQURQ7UR S-UR *S.6n[UR5H8nURURURRUS9S95 M: U$)uInvert (take adjoint of) this circuit. This is done by recursively inverting all gates. Args: annotated: indicates whether the inverse gate can be implemented as an annotated gate. Returns: QuantumCircuit: the inverted circuit Raises: CircuitError: if the circuit cannot be inverted. Examples: input: .. code-block:: text ┌───┐ q_0: ┤ H ├─────■────── └───┘┌────┴─────┐ q_1: ─────┤ RX(1.57) ├ └──────────┘ output: .. code-block:: text ┌───┐ q_0: ──────■──────┤ H ├ ┌─────┴─────┐└───┘ q_1: ┤ RX(-1.57) ├───── └───────────┘ _dgr% annotatedr) rNrrrrrRrSrryrr rinverse)rr3 inverse_circrs r`r4QuantumCircuit.inverse$sJ& KK KK ZZ ZZ  U"+++  $DJJ/K  ##k.C.C.K.KV_.K.`#a 0r)insert_barriersc[URUR/URQURQ7SUR SU3-06nUS:alUR 5n[U5HLnURX@RUR5 U(dM2XQS- :wdM<UR5 MN U$![a UR5nNyf=f)aRepeat this circuit ``reps`` times. Args: reps (int): How often this circuit should be repeated. insert_barriers (bool): Whether to include barriers between circuit repetitions. Returns: QuantumCircuit: A circuit containing ``reps`` repetitions of this circuit. rRz**rr) rNrrrrrRto_gaterto_instructionrangerbarrier)rrepsr7 repeated_circinstis r`repeatQuantumCircuit.repeatXs' KK '+zz 48JJ EIYYSUVZU[Q\E\ !8 -$(LLN4[%%dKKE"?q1H}!))+!  -**, -sB??CCc,US:aD[U[[R45(aU(dU(dUR U5$UR S:a[ SUR35eUR5n[URUR/URQURQ76nURUR!XS9[#[%UR&555 U$![an[ S5UeSnAff=f)aRaise this circuit to the power of ``power``. If ``power`` is a positive integer and both ``matrix_power`` and ``annotated`` are ``False``, this implementation defaults to calling ``repeat``. Otherwise, the circuit is converted into a gate, and a new circuit, containing this gate raised to the given power, is returned. The gate raised to the given power is implemented either as a unitary gate if ``annotated`` is ``False`` or as an annotated operation if ``annotated`` is ``True``. Args: power (float): The power to raise this circuit to. matrix_power (bool): indicates whether the inner power gate can be implemented as a unitary gate. annotated (bool): indicates whether the inner power gate can be implemented as an annotated operation. Raises: CircuitError: If the circuit needs to be converted to a unitary gate, but is not unitary. Returns: QuantumCircuit: A circuit implementing this circuit raised to the power of ``power``. rzoCannot raise a parameterized circuit to a non-positive power or matrix-power, please bind the free parameters: zThe circuit contains non-unitary operations and cannot be raised to a power. Note that no qiskit.circuit.Instruction objects may be in the circuit for this operation.Nr2)r[renpintegerrAnum_parametersr parametersr9rrNrrrrrpowerr\r;r)rrH matrix_powerr3gateex power_circuits r`rHQuantumCircuit.powerts6 QJ53 "344 ;;u% %    "E??#%   <<>D't{{DKKZ$**ZtzzZ TZZZCT%PTP_P_J`Eab D   s4C88 D DDc4UR5nURXX45n[ U5n[ XR /URQ7SSUR306n U RXyR 5 U $![an[S5UeSnAff=f)ajControl this circuit on ``num_ctrl_qubits`` qubits. Args: num_ctrl_qubits (int): The number of control qubits. label (str): An optional label to give the controlled operation for visualization. ctrl_state (str or int): The control state in decimal or as a bitstring (e.g. '111'). If None, use ``2**num_ctrl_qubits - 1``. annotated: indicates whether the controlled gate should be implemented as an annotated gate. Returns: QuantumCircuit: The controlled version of this circuit. Raises: CircuitError: If the circuit contains a non-unitary operation and cannot be controlled. zThe circuit contains non-unitary operations and cannot be controlled. Note that no qiskit.circuit.Instruction objects may be in the circuit for this operation.NrRc_) r9rrcontrolrrNrrrRr) rnum_ctrl_qubitslabel ctrl_stater3rJrKcontrolled_gate control_qregcontrolled_circs r`rPQuantumCircuit.controls. <<>D,,zU&7 ( ++ (,  ;=dii[9I  0F0FG 8   sA<< B BB)r var_remapinline_capturesc  ^^^^U(a#U(aUR(a [S5eU(dUR(a [S5eU(aUOUR5n Tc0OTmSU4Sjjm[U[5(a}UR (dlUR (a[U R(a [S5eU R UR 5 URHn U RU 5 M U(aV[U[5(aA[SUR55(aUR5OUR5n[U[5(dUcURSURnUcUR SURnU(aUU R RTS9n U R#5 U R%XUTS9 U Hn U R'U 5 M OU R%XUTS 9 U(aS$U $URU R:dURU R:a [S 5e0nUc<U RnUR)[+URU R55 OU R-U5n[/U5UR:wa%[S [/U5S URS 35e[/[1U55[/U5:wa[SUS35eUR)[+URU55 Uc<U R nUR)[+UR U R 55 OU R3U5n[/U5UR:wa%[S[/U5SURS 35e[/[1U55[/U5:wa[SUS35eUR)[+UR U R3U555 SU lSU lU =R8UR8- slURnSUUU4SjjmSnU(a)U R RTS9nU R#5 T"UU U0U UUS9 U(aU R;5R=U5 U(aS$U $)u5Apply the instructions from one circuit onto specified qubits and/or clbits on another. .. note:: By default, this creates a new circuit object, leaving ``self`` untouched. For most uses of this function, it is far more efficient to set ``inplace=True`` and modify the base circuit in-place. When dealing with realtime variables (:class:`.expr.Var` and :class:`.expr.Stretch` instances), there are two principal strategies for using :meth:`compose`: 1. The ``other`` circuit is treated as entirely additive, including its variables. The variables in ``other`` must be entirely distinct from those in ``self`` (use ``var_remap`` to help with this), and all variables in ``other`` will be declared anew in the output with matching input/capture/local scoping to how they are in ``other``. This is generally what you want if you're joining two unrelated circuits. 2. The ``other`` circuit was created as an exact extension to ``self`` to be inlined onto it, including acting on the existing variables in their states at the end of ``self``. In this case, ``other`` should be created with all these variables to be inlined declared as "captures", and then you can use ``inline_captures=True`` in this method to link them. This is generally what you want if you're building up a circuit by defining layers on-the-fly, or rebuilding a circuit using layers taken from itself. You might find the ``vars_mode="captures"`` argument to :meth:`copy_empty_like` useful to create each layer's base, in this case. Args: other (qiskit.circuit.Instruction or QuantumCircuit): (sub)circuit or instruction to compose onto self. If not a :obj:`.QuantumCircuit`, this can be anything that :obj:`.append` will accept. qubits (list[Qubit|int]): qubits of self to compose onto. clbits (list[Clbit|int]): clbits of self to compose onto. front (bool): If ``True``, front composition will be performed. This is not possible within control-flow builder context managers. inplace (bool): If ``True``, modify the object. Otherwise, return composed circuit. copy (bool): If ``True`` (the default), then the input is treated as shared, and any contained instructions will be copied, if they might need to be mutated in the future. You can set this to ``False`` if the input should be considered owned by the base circuit, in order to avoid unnecessary copies; in this case, it is not valid to use ``other`` afterward, and some instructions may have been mutated in place. var_remap (Mapping): mapping to use to rewrite :class:`.expr.Var` and :class:`.expr.Stretch` nodes in ``other`` as they are inlined into ``self``. This can be used to avoid naming conflicts. Both keys and values can be given as strings or direct identifier instances. If a key is a string, it matches any :class:`~.expr.Var` or :class:`~.expr.Stretch` with the same name. If a value is a string, whenever a new key matches it, a new :class:`~.expr.Var` or :class:`~.expr.Stretch` is created with the correct type. If a value is a :class:`~.expr.Var`, its :class:`~.expr.Expr.type` must exactly match that of the variable it is replacing. inline_captures (bool): if ``True``, then all "captured" identifier nodes in the ``other`` :class:`.QuantumCircuit` are assumed to refer to identifiers already declared in ``self`` (as any input/capture/local type), and the uses in ``other`` will apply to the existing identifiers. If you want to build up a layer for an existing circuit to use with :meth:`compose`, you might find the ``vars_mode="captures"`` argument to :meth:`copy_empty_like` useful. Any remapping in ``vars_remap`` occurs before evaluating this variable inlining. If this is ``False`` (the default), then all identifiers in ``other`` will be required to be distinct from those in ``self``, and new declarations will be made for them. wrap (bool): If True, wraps the other circuit into a gate (or instruction, depending on whether it contains only unitary instructions) before composing it onto self. Rather than using this option, it is almost always better to manually control this yourself by using :meth:`to_instruction` or :meth:`to_gate`, and then call :meth:`append`. Returns: QuantumCircuit: the composed circuit (returns None if inplace==True). Raises: CircuitError: if no correct wire mapping can be made between the two circuits, such as if ``other`` is wider than ``self``. CircuitError: if trying to emit a new circuit while ``self`` has a partially built control-flow context active, such as the context-manager forms of :meth:`if_test`, :meth:`for_loop` and :meth:`while_loop`. CircuitError: if trying to compose to the front of a circuit when a control-flow builder block is active; there is no clear meaning to this action. Examples: .. code-block:: python >>> lhs.compose(rhs, qubits=[3, 2], inplace=True) .. code-block:: text ┌───┐ ┌─────┐ ┌───┐ lqr_1_0: ───┤ H ├─── rqr_0: ──■──┤ Tdg ├ lqr_1_0: ───┤ H ├─────────────── ├───┤ ┌─┴─┐└─────┘ ├───┤ lqr_1_1: ───┤ X ├─── rqr_1: ┤ X ├─────── lqr_1_1: ───┤ X ├─────────────── ┌──┴───┴──┐ └───┘ ┌──┴───┴──┐┌───┐ lqr_1_2: ┤ U1(0.1) ├ + = lqr_1_2: ┤ U1(0.1) ├┤ X ├─────── └─────────┘ └─────────┘└─┬─┘┌─────┐ lqr_2_0: ─────■───── lqr_2_0: ─────■───────■──┤ Tdg ├ ┌─┴─┐ ┌─┴─┐ └─────┘ lqr_2_1: ───┤ X ├─── lqr_2_1: ───┤ X ├─────────────── └───┘ └───┘ lcr_0: 0 ═══════════ lcr_0: 0 ═══════════════════════ lcr_1: 0 ═══════════ lcr_1: 0 ═══════════════════════ zPCannot compose to the front of a circuit while a control-flow context is active.zJCannot emit a new composed circuit while a control-flow context is active.Nc B>URU5=n(aU$TRU5=n(d#TRUR5=n(GaB[U[R5(a[U[R 5(a[ SUSUS35e[U[5(a)[RRX0R5nURUR:wa3[ SURSURSURS35eOh[U[R5(a[ SUSUS35e[U[5(a[R RU5nOUnX1U'U$)Nz-mismatched identifier kinds in replacement: 'z' cannot become ''z%mismatched types in replacement for 'z': 'z,mismatched identifier kind in replacement: ') getrRr[r9VarStretchrrsnewrm)rcacher replacementrXs r` replace_var+QuantumCircuit.compose..replace_varcs{ iin$s$ (}}S11 1immTWT\T\F]7]{7]c488,,!+t||<<*!!$%6{m1F"+s33&*hhll;&I "''3883*CCHH:N!!$ *;Kcannot implicitly add clbits while within a control-flow scopec3V# UHn[UR[5v M! g7frZ)r[rr)r^inss r`ra)QuantumCircuit.compose..sM*3z#--66*s')copy_instructionsr)rrrzHTrying to compose with another QuantumCircuit which has more 'in' edges.z%Number of items in qubits parameter (z2) does not match number of qubits in the circuit (z).z4Duplicate qubits referenced in 'qubits' parameter: 'r\z%Number of items in clbits parameter (z2) does not match number of clbits in the circuit (z4Duplicate clbits referenced in 'clbits' parameter: 'rhc>^^^ ^ UR5HnURT"UT55 M U(acUR5HNnT"UT5nURT"UT55(aM+XxLa[ SUS35e[ SUSUS35e O/UR5HnUR T"UT55 M UR 5HnURT"UT55 M UR5Hn URT"U T55 M UUU4Sjm [R"URTTURS9m UU U 4Sjn URRTS 9n U R!XVS 9 U R#U 5 UR%5R'U 5 g) Nz Variable 'zt' to be inlined is not in the base circuit. If you wanted it to be automatically added, use `inline_captures=False`.z Replacement 'z' for variable 'z:' is not in the base circuit. Is the replacement correct?c8>URSS9nT"XTTSS9 U$)Ndrop vars_modeF)rY)r)block new_blockbit_mapcopy_with_remappingvar_maps r` recurse_blockJQuantumCircuit.compose..copy_with_remapping..recurse_blocks/ "11F1C $EgwX]^  r)r{c>Un[U[5(aURU4SjUR55n[U[[ 45(a!TR UR5UlO[U[5(a TRUR5Ul O[U[5(a?[TRUR5TRUR55nOU[U[ 5(a@UR"S:Xa0UR%5nTRUR&5UlXLaT(aUR%5$U$)Nc34># UH nT"U5v M g7frZrQ)r^rorts r`raXQuantumCircuit.compose..copy_with_remapping..map_vars.. s.]Q\}U/C/CQ\sr9)r[r'replace_blocksblocksr3r7 map_condition _condition conditionr5 map_targettargetrDmap_exprlvaluervaluerCrrr)opn_oprrtvariable_mappers r`map_varsEQuantumCircuit.compose..copy_with_remapping..map_vars s dM22...]QUQ\Q\.]]D!$;(?@@)8)F)Ft)W#D,77&5&@&@&M e,, '00=?W?WX\XcXc?dD e,,f1D99;D$3$<$.copy_with_remappings --/{3890!//1C"-c7";K..{3/HII-".",SE2<!<# ++K=8HNJJ2"//1C$$[g%>?2002**;sG+DE3!99;  Wg!>?< !6DD GW4;L;LO D""<<,,t,DL  % %Z % K  , ,X 6    ! ( ( 6r)rqrsrYrr)rUnion[expr.Var, expr.Stretch]razMapping[expr.Var, expr.Var]returnzUnion[expr.Var | expr.Stretch]NN)rxrrr[rNrrrr{rjrr9r:rr num_clbitsryrrrrzip_qbit_argument_conversionlenr_cbit_argument_conversionrrrSrr)rrrrfrontinplacewraprrXrYrr_old_dataredge_map mapped_qubits mapped_clbits_append_existingrrrcs `` @@r`composeQuantumCircuit.composeshl u!:!:b 444\ tDIIK#+B ! .! 7R!  +! J e^ , ,;;5<<,,&X ell+ ;;C%%c*' Jun55M%**MMM ))+  %00~%7u'7'78~%7u'7'78::??T?B  E6 =#+KLL-$, EvD I"4 , ,   doo -1A1ADOO1SZ 8: > KKM OOC dkk: ; ::6BM=!U%5%55";C PPRT3}%&#m*<<"J=/YZ[ OOC m< = > KKM OOC dkk: ; ::6BM=!U%5%55";C PPRT3}%&#m*<<"J=/YZ[ OOC d.L.LV.TU V   U/// JJZ^A 7A 7F "jjoooEO JJL  +$$      ! ( ( 9t(D(rcURUR-nURUR-n[UR5[UR5s=:XaS:XaaO O^URSRURSRs=:XaS:Xa#O O US:a [ X45nGO-[ U5nGO [UR 5[UR 5s=:XaS:XaO OUR SRUR SRs=:XaS:XaJO OG[URUR-S5n[ /URQURQUP76nOe[ URURURUR/URQURQUR QUR Q76nURU[UR5[UR5SS9 URU[URU5[URU5SS9 U(a&URRUR5 gU$)uTensor ``self`` with ``other``. Remember that in the little-endian convention the leftmost operation will be at the bottom of the circuit. See also `the docs `__ for more information. .. code-block:: text ┌────────┐ ┌─────┐ ┌─────┐ q_0: ┤ bottom ├ ⊗ q_0: ┤ top ├ = q_0: ─┤ top ├── └────────┘ └─────┘ ┌┴─────┴─┐ q_1: ┤ bottom ├ └────────┘ Args: other (QuantumCircuit): The other circuit to tensor this circuit with. inplace (bool): If ``True``, modify the object. Otherwise return composed circuit. Examples: .. plot:: :alt: Circuit diagram output by the previous code. :include-source: from qiskit import QuantumCircuit top = QuantumCircuit(1) top.x(0); bottom = QuantumCircuit(2) bottom.cry(0.2, 0, 1); tensored = bottom.tensor(top) tensored.draw('mpl') Returns: QuantumCircuit: The tensored circuit (returns ``None`` if ``inplace=True``). rrrmeasTrN)rrrrrRrNrr$rrrr;rr)rrrrrrcrs r`tensorQuantumCircuit.tensor2 sJ__u'7'77 __u'7'77   Os5;;/ 41 4 1 ""ekk!n&9&9@S@A~%j=%j1  Os5;;/ 41 4 1 ""ekk!n&9&9CVC"4??U5E5E#EvNB!@5;;@@R@D"          D UE%"2"23U5;K;K5LVZ [  %""J / %""J /    MM  / rc.URR$)zDict mapping Clbit instances to an object comprised of `.index` the corresponding index in circuit. and `.registers` a list of Register-int pairs for each Register containing the Bit and its index within that register.)ry_clbit_indicesrs r`rQuantumCircuit._clbit_indices  zz(((rc.URR$)zDict mapping Qubit instances to an object comprised of `.index` the corresponding index in circuit. and `.registers` a list of Register-int pairs for each Register containing the Bit and its index within that register.)ry_qubit_indicesrs r`rQuantumCircuit._qubit_indices rrc.URR$z[A list of :class:`Qubit`\ s in the order that they were added. You should not mutate this.)ryrrs r`rQuantumCircuit.qubits szz   rc.URR$)aA list of :class:`Clbit`\ s in the order that they were added. You should not mutate this. Example: .. plot:: :include-source: :nofigs: :context: reset from qiskit import QuantumRegister, ClassicalRegister, QuantumCircuit qr1 = QuantumRegister(2) qr2 = QuantumRegister(1) cr1 = ClassicalRegister(2) cr2 = ClassicalRegister(1) qc = QuantumCircuit(qr1, qr2, cr1, cr2) print("List the qubits in this circuit:", qc.qubits) print("List the classical bits in this circuit:", qc.clbits) .. code-block:: text List the qubits in this circuit: [Qubit(QuantumRegister(2, 'q0'), 0), Qubit(QuantumRegister(2, 'q0'), 1), Qubit(QuantumRegister(1, 'q1'), 0)] List the classical bits in this circuit: [Clbit(ClassicalRegister(2, 'c0'), 0), Clbit(ClassicalRegister(2, 'c0'), 1), Clbit(ClassicalRegister(1, 'c1'), 0)] )ryrrs r`rQuantumCircuit.clbits s<zz   rc.URR$rryrrs r`rQuantumCircuit.qregs zzrc$XRlgrZrrrs r`rr  rc.URR$)z[A list of :class:`Clbit`\ s in the order that they were added. You should not mutate this.ryrrs r`rQuantumCircuit.cregs rrc$XRlgrZrrs r`rr rrcUR$)zbA list of :class:`AncillaQubit`\ s in the order that they were added. You should not mutate this.)rzrs r`ancillasQuantumCircuit.ancillas s~~rcNURUR-UR-$)zrThe number of real-time classical variables in the circuit. This is the length of the :meth:`iter_vars` iterable.)num_input_varsnum_captured_varsnum_declared_varsrs r`num_varsQuantumCircuit.num_vars s& ""T%;%;;d>T>TTTrc4URUR-$)zcThe number of stretches in the circuit. This is the length of the :meth:`iter_stretches` iterable.)num_captured_stretchesnum_declared_stretchesrs r` num_stretchesQuantumCircuit.num_stretches s **T-H-HHHrc4URUR-$)zThe number of real-time classical variables and stretches in the circuit. This is equal to :meth:`num_vars` + :meth:`num_stretches`. )rrrs r`num_identifiersQuantumCircuit.num_identifiers s}}t1111rc.URR$)zThe number of real-time classical variables in the circuit marked as circuit inputs. This is the length of the :meth:`iter_input_vars` iterable. If this is non-zero, :attr:`num_captured_vars` must be zero.)ryrrs r`rQuantumCircuit.num_input_vars rrc.URR$)zThe number of real-time classical variables in the circuit marked as captured from an enclosing scope. This is the length of the :meth:`iter_captured_vars` iterable. If this is non-zero, :attr:`num_input_vars` must be zero.)ryrrs r`r QuantumCircuit.num_captured_vars szz+++rc.URR$)zThe number of stretches in the circuit marked as captured from an enclosing scope. This is the length of the :meth:`iter_captured_stretches` iterable. If this is non-zero, :attr:`num_input_vars` must be zero.)ryrrs r`r%QuantumCircuit.num_captured_stretches szz000rc.URR$)zThe number of real-time classical variables in the circuit that are declared by this circuit scope, excluding inputs or captures. This is the length of the :meth:`iter_declared_vars` iterable.)ryrrs r`r QuantumCircuit.num_declared_vars s zz+++rc.URR$)zThe number of stretches in the circuit that are declared by this circuit scope, excluding captures. This is the length of the :meth:`iter_declared_stretches` iterable.)ryrrs r`r%QuantumCircuit.num_declared_stretches s zz000rchUR(aBURSn[R"UR5UR 55$[R"UR R 5UR R5UR R55$)aGet an iterable over all real-time classical variables in scope within this circuit. This method will iterate over all variables in scope. For more fine-grained iterators, see :meth:`iter_declared_vars`, :meth:`iter_input_vars` and :meth:`iter_captured_vars`.r&) rx itertoolschainiter_captured_varsiter_local_varsryget_input_varsget_captured_varsget_declared_varsrbuilders r` iter_varsQuantumCircuit.iter_vars s  $ $//3G??7#=#=#?AXAXAZ[ [ JJ % % ' JJ ( ( * JJ ( ( *  rc6UR(aBURSn[R"UR5UR 55$[R"UR R 5UR R55$)zGet an iterable over all stretches in scope within this circuit. This method will iterate over all stretches in scope. For more fine-grained iterators, see :meth:`iter_declared_stretches` and :meth:`iter_captured_stretches`.r&)rxrriter_captured_stretchesiter_local_stretchesryget_captured_stretchesget_declared_stretchesrs r`iter_stretchesQuantumCircuit.iter_stretches, sw  $ $//3G??//173O3O3Q  JJ - - /1R1R1T  rcUR(aURSR5$URR5$)zGet an iterable over all real-time classical variables that are declared with automatic storage duration in this scope. This excludes input variables (see :meth:`iter_input_vars`) and captured variables (see :meth:`iter_captured_vars`).r&)rxrryrrs r`r!QuantumCircuit.iter_declared_vars: s:  $ $,,R0@@B Bzz++--rcUR(aURSR5$URR5$)zGet an iterable over all stretches that are declared in this scope. This excludes captured stretches (see :meth:`iter_captured_stretches`).r&)rxrryrrs r`r&QuantumCircuit.iter_declared_stretchesB s:  $ $,,R0EEG Gzz0022rcZUR(agURR5$)zGet an iterable over all real-time classical variables that are declared as inputs to this circuit scope. This excludes locally declared variables (see :meth:`iter_declared_vars`) and captured variables (see :meth:`iter_captured_vars`).rQ)rxryrrs r`rQuantumCircuit.iter_input_varsI s#  $ $zz((**rcLUR(aM[R"URSR5URSR 55$[R"UR R 5UR R55$)aGet an iterable over all identifiers are captured by this circuit scope from a containing scope. This excludes input variables (see :meth:`iter_input_vars`) and locally declared variables and stretches (see :meth:`iter_declared_vars` and :meth:`iter_declared_stretches`).r&)rxrrrrryrrrs r`rQuantumCircuit.iter_capturesQ sy  $ $??))"-@@B))"-EEG tzz;;=tzz?`?`?bccrcUR(aURSR5$URR5$)zGet an iterable over all real-time classical variables that are captured by this circuit scope from a containing scope. This excludes input variables (see :meth:`iter_input_vars`) and locally declared variables (see :meth:`iter_declared_vars`).r&)rxrryrrs r`r!QuantumCircuit.iter_captured_vars] s:  $ $,,R0CCE Ezz++--rcUR(aURSR5$URR5$)zGet an iterable over stretches that are captured by this circuit scope from a containing scope. This excludes locally declared stretches (see :meth:`iter_declared_stretches`).r&)rxrryrrs r`r&QuantumCircuit.iter_captured_stretchese s:  $ $,,R0HHJ Jzz0022rc$URU5$)z%Overload & to implement self.compose.rrrhss r`__and__QuantumCircuit.__and__m s||C  rc&URUSS9 U$)z/Overload &= to implement self.compose in place.Trrrs r`__iand__QuantumCircuit.__iand__q s S$ ' rc$URU5$)z$Overload ^ to implement self.tensor.rrtops r`__xor__QuantumCircuit.__xor__v s{{3rc&URUSS9 U$)z.Overload ^= to implement self.tensor in place.Trr r s r`__ixor__QuantumCircuit.__ixor__z s C & rc,[UR5$)z'Return number of operations in circuit.)rryrs r`__len__QuantumCircuit.__len__ s4::rcgrZrQritems r` __getitem__QuantumCircuit.__getitem__ sFKP;TV;W;488>;WE  # #B .&9a9ab //BGGD   T ",::2VYK  T B  ! !-"<"]`a>a b H XsC;rc|[U[5(a%URnURnURnOUn[U[ 5(dm[ US5(a1UR5n[U[ 5(d [S5eO+[U[ 5(a [S5e[S5eUR5n[USS5=n(atSnUHHn U=(d [U [5n[U [R5(dM=[Xi5n MJ U(aU(a[ R""U5n[U[$5(aUR&S:Xa%UR(S :Xa[XeR*5 [,R.R1S UR255V s1sHn UR5U 5(aMU iM sn =n (a[S U S 35eU=(d /V s/sHoR7U 5PM n n U=(d /Vs/sHoR9U5PM nn[;UR<S 9n[U[>5(aURAX5O[>R@"X]U5n[USS5nUHhupURCU 5 UREXS9nURGU5 URIURJ[MURJ5S- 5 Mj U$s sn fs sn fs snf)aAppend one or more instructions to the end of the circuit, modifying the circuit in place. The ``qargs`` and ``cargs`` will be expanded and broadcast according to the rules of the given :class:`~.circuit.Instruction`, and any non-:class:`.Bit` specifiers (such as integer indices) will be resolved into the relevant instances. If a :class:`.CircuitInstruction` is given, it will be unwrapped, verified in the context of this circuit, and a new object will be appended to the circuit. In this case, you may not pass ``qargs`` or ``cargs`` separately. Args: instruction: :class:`~.circuit.Instruction` instance to append, or a :class:`.CircuitInstruction` with all its context. qargs: specifiers of the :class:`~.circuit.Qubit`\ s to attach instruction to. cargs: specifiers of the :class:`.Clbit`\ s to attach instruction to. copy: if ``True`` (the default), then the incoming ``instruction`` is copied before adding it to the circuit if it contains symbolic parameters, so it can be safely mutated without affecting other circuits the same instruction might be in. If you are sure this instruction will not be in other circuits, you can set this ``False`` for a small speedup. Returns: qiskit.circuit.InstructionSet: a handle to the :class:`.CircuitInstruction`\ s that were actually added to the circuit. Raises: CircuitError: if the operation passed is not an instance of :class:`~.circuit.Instruction` . r:z/operation.to_instruction() is not an Operation.zTObject is a subclass of Operation, please add () to pass an instance of this object.zHObject to append must be an Operation or have a to_instruction() method.r6rQFboxr9c3@# UHoR5v M g7frZ)r)r^ros r`ra(QuantumCircuit.append.. s97Ge''))7Gsz%Control-flow op attempts to capture 'z' which are not in this circuitr+r(r)'r[rBrrrr@hasattrr:r issubclassrgetattrr;r9Expr_validate_exprrrr'rRrrrr from_iterablerzrrrr?r1rr2r3r rr5rr)rrrrrrr7r6 is_parameterr:r bad_capturesr8r9cargexpanded_cargsrbroadcast_iterbase_instructions r`rQuantumCircuit.append sJ k#5 6 6#--I&&E&&E#I)Y//y"233%446 !)Y77&'XYY8i33&; #^++- Y"5 56 5 L+Uz%AT/U eTYY//*=@E  !NN95 i / /~~&9>>V+C}.@.@A %??8897@7G7G9 C**3/  |#;L>J55 LQ;TV;W;488>;WKP;TV;W;488>;W%9a9ab )[11  ) ). I00N[  .iR@(JD   T "*22$2LK   -  ! !-"<"]`a>a b ) 9 XWsL/1L/L4L9cgrZrQrrr/s r`rQuantumCircuit._append4 s!rcgrZrQ)rrrrs r`rrP: s rr.c NU(a+URRU5 SUlSUlU$[ U[ 5(+nU(a [ XU5nURRU5 SUlSUlU(a UR$U$![ a [URR5VVs/sH/upg[ U[[45(dM"XgR4PM1 Os snnfnnnURRX5 Nf=f)a^Append an instruction to the end of the circuit, modifying the circuit in place. .. warning:: This is an internal fast-path function, and it is the responsibility of the caller to ensure that all the arguments are valid; there is no error checking here. In particular: * all the qubits and clbits must already exist in the circuit and there can be no duplicates in the list. * any control-flow operations instructions must act only on variables present in the circuit. * the circuit must not be within a control-flow builder context. .. note:: This function may be used by callers other than :obj:`.QuantumCircuit` when the caller is sure that all error-checking, broadcasting and scoping has already been performed, and the only reference to the circuit the instructions are being appended to is within that same function. In particular, it is not safe to call :meth:`QuantumCircuit._append` on a circuit that is received by a function argument. This is because :meth:`.QuantumCircuit._append` will not recognize the scoping constructs of the control-flow builder interface. Args: instruction: A complete well-formed :class:`.CircuitInstruction` of the operation and its context to be added. In the legacy compatibility form, this can be a bare :class:`.Operation`, in which case ``qargs`` and ``cargs`` must be explicitly given. qargs: Legacy argument for qubits to attach the bare :class:`.Operation` to. Ignored if the first argument is in the preferential :class:`.CircuitInstruction` form. cargs: Legacy argument for clbits to attach the bare :class:`.Operation` to. Ignored if the first argument is in the preferential :class:`.CircuitInstruction` form. Returns: CircuitInstruction: a handle to the instruction that was just added. :meta public: Nrh)ryrrrr[rB RuntimeErrorrrr6r;rNrGappend_manual_params) rrrrr/ old_styleidxr:r6s r`rrPB sR  JJ  k *!DNDJ ";0BCC ,[GK  A JJ  k * (1{$$B{B A#,K,A,A,H,H"I"IJCe&9>%JK(&&'"IF JJ + +K @  As$B,D$!C=+C=<%D$#D$cgrZrQrrRdefaults r` get_parameterQuantumCircuit.get_parameter sKNr.cgrZrQrXs r`rZr[ sORrcvURRU5=ncU[La[SUS35eU$U$)aRetrieve a compile-time parameter that is accessible in this circuit scope by name. Args: name: the name of the parameter to retrieve. default: if given, this value will be returned if the parameter is not present. If it is not given, a :exc:`KeyError` is raised instead. Returns: The corresponding parameter. Raises: KeyError: if no default is given, but the parameter does not exist in the circuit. Examples: Retrieve a parameter by name from a circuit:: from qiskit.circuit import QuantumCircuit, Parameter my_param = Parameter("my_param") # Create a parametrized circuit. qc = QuantumCircuit(1) qc.rx(my_param, 0) # We can use 'my_param' as a parameter, but let's say we've lost the Python object # and need to retrieve it. my_param_again = qc.get_parameter("my_param") assert my_param is my_param_again Get a variable from a circuit by name, returning some default if it is not present:: assert qc.get_parameter("my_param", None) is my_param assert qc.get_parameter("unknown_param", None) is None See also: :meth:`get_var` A similar method, but for :class:`.expr.Var` run-time variables instead of :class:`.Parameter` compile-time parameters. zno parameter named ' ' is present)ryget_parameter_by_nameEllipsisKeyError)rrRrY parameters r`rZr[ sGR99$? ?I H("!5dV<HIINrc[U[5(aURUS5SL$[U[5=(a URURS5U:H$)aCheck whether a parameter object exists in this circuit. Args: name_or_param: the parameter, or name of a parameter to check. If this is a :class:`.Parameter` node, the parameter must be exactly the given one for this function to return ``True``. Returns: whether a matching parameter is assignable in this circuit. See also: :meth:`QuantumCircuit.get_parameter` Retrieve the :class:`.Parameter` instance from this circuit by name. :meth:`QuantumCircuit.has_var` A similar method to this, but for run-time :class:`.expr.Var` variables instead of compile-time :class:`.Parameter`\ s. N)r[rsrZrrR)r name_or_params r` has_parameterQuantumCircuit.has_parameter sY$ mS ) )%%mT:$F F }i 0 N""=#5#5t< M rcgrZrQrXs r`get_varQuantumCircuit.get_var rrcgrZrQrXs r`rhri sHKrc~UR5RU5=nbU$U[La[SUS35eU$)aRetrieve a variable that is accessible in this circuit scope by name. Args: name: the name of the variable to retrieve. default: if given, this value will be returned if the variable is not present. If it is not given, a :exc:`KeyError` is raised instead. Returns: The corresponding variable. Raises: KeyError: if no default is given, but the variable does not exist. Examples: Retrieve a variable by name from a circuit:: from qiskit.circuit import QuantumCircuit # Create a circuit and create a variable in it. qc = QuantumCircuit() my_var = qc.add_var("my_var", False) # We can use 'my_var' as a variable, but let's say we've lost the Python object and # need to retrieve it. my_var_again = qc.get_var("my_var") assert my_var is my_var_again Get a variable from a circuit by name, returning some default if it is not present:: assert qc.get_var("my_var", None) is my_var assert qc.get_var("unknown_variable", None) is None See also: :meth:`get_parameter` A similar method, but for :class:`.Parameter` compile-time parameters instead of :class:`.expr.Var` run-time variables. zno variable named 'r^)rrhr`rarrRrYrs r`rhri sKN&&(006 6C CJ h 0lCD Drc[U[5(aURUS5SL$URURS5U:H$)ahCheck whether a variable is accessible in this scope. Args: name_or_var: the variable, or name of a variable to check. If this is a :class:`.expr.Var` node, the variable must be exactly the given one for this function to return ``True``. Returns: whether a matching variable is accessible. See also: :meth:`QuantumCircuit.get_var` Retrieve the :class:`.expr.Var` instance from this circuit by name. :meth:`QuantumCircuit.has_parameter` A similar method to this, but for compile-time :class:`.Parameter`\ s instead of run-time :class:`.expr.Var` variables. N)r[rsrhrR)r name_or_vars r`has_varQuantumCircuit.has_var sC$ k3 ' '<< T2$> >||K,,d3{BBrcgrZrQrXs r` get_stretchQuantumCircuit.get_stretch# sLOrcgrZrQrXs r`rrrs' sPSrc~UR5RU5=nbU$U[La[SUS35eU$)aARetrieve a stretch that is accessible in this circuit scope by name. Args: name: the name of the stretch to retrieve. default: if given, this value will be returned if the variable is not present. If it is not given, a :exc:`KeyError` is raised instead. Returns: The corresponding stretch. Raises: KeyError: if no default is given, but the variable does not exist. Examples: Retrieve a stretch by name from a circuit:: from qiskit.circuit import QuantumCircuit # Create a circuit and create a variable in it. qc = QuantumCircuit() my_stretch = qc.add_stretch("my_stretch") # We can use 'my_stretch' as a variable, but let's say we've lost the Python object and # need to retrieve it. my_stretch_again = qc.get_stretch("my_stretch") assert my_stretch is my_stretch_again Get a variable from a circuit by name, returning some default if it is not present:: assert qc.get_stretch("my_stretch", None) is my_stretch assert qc.get_stretch("unknown_stretch", None) is None zno stretch named 'r^)rrrr`rarls r`rrrs* sKD&&(44T: :C GJ h /v\BC Crc[U[5(aURUS5SL$URURS5U:H$)aCheck whether a stretch is accessible in this scope. Args: name_or_stretch: the stretch, or name of a stretch to check. If this is a :class:`.expr.Stretch` node, the stretch must be exactly the given one for this function to return ``True``. Returns: whether a matching stretch is accessible. See also: :meth:`QuantumCircuit.get_stretch` Retrieve the :class:`.expr.Stretch` instance from this circuit by name. N)r[rsrrrR)rname_or_stretchs r` has_stretchQuantumCircuit.has_stretchR sG os + +##OT:$F F 4 4d;NNrcgrZrQrXs r`get_identifierQuantumCircuit.get_identifiere sZ]rcgrZrQrXs r`r{r|i s),rcUR5RU5=nbU$UR5RU5=nbU$U[La[ SUS35eU$)aGRetrieve an identifier that is accessible in this circuit scope by name. This currently includes both real-time classical variables and stretches. Args: name: the name of the identifier to retrieve. default: if given, this value will be returned if the variable is not present. If it is not given, a :exc:`KeyError` is raised instead. Returns: The corresponding variable. Raises: KeyError: if no default is given, but the identifier does not exist. See also: :meth:`get_var` Gets an identifier known to be a :class:`.expr.Var` instance. :meth:`get_stretch` Gets an identifier known to be a :class:`.expr.Stretch` instance. :meth:`get_parameter` A similar method, but for :class:`.Parameter` compile-time parameters instead of :class:`.expr.Var` run-time variables. zno identifier named 'r^)rrhrrr`rarls r`r{r|o sn2&&(006 6C CJ&&(44T: :C GJ h 24& EF Frc[U[5(aURUS5SL$URURS5U:H$)aCheck whether an identifier is accessible in this scope. Args: name_or_ident: the instance, or name of the identifier to check. If this is a :class:`.expr.Var` or :class:`.expr.Stretch` node, the matched instance must be exactly the given one for this function to return ``True``. Returns: whether a matching identifier is accessible. See also: :meth:`QuantumCircuit.get_identifier` Retrieve the :class:`.expr.Var` or :class:`.expr.Stretch` instance from this circuit by name. :meth:`QuantumCircuit.has_var` The same as this method, but ignoring anything that isn't a run-time :class:`expr.Var` variable. :meth:`QuantumCircuit.has_stretch` The same as this method, but ignoring anything that isn't a run-time :class:`expr.Stretch` variable. :meth:`QuantumCircuit.has_parameter` A similar method to this, but for compile-time :class:`.Parameter`\ s instead of run-time :class:`.expr.Var` variables. N)r[rsr{rR)r name_or_idents r`rQuantumCircuit.has_identifier sG2 mS ) )&&}d;4G G""=#5#5t< MMrcN[U[5(a.Uc [S5e[RR X5nOUnUR (d [S5eURURSS9=nb&XC:Xa[SUS35e[SUSUS35eU$) aThe common logic for preparing and validating a new :class:`~.expr.Var` for the circuit. The given ``type_`` can be ``None`` if the variable specifier is already a :class:`.Var`, and must be a :class:`~.types.Type` if it is a string. The argument is ignored if the given first argument is a :class:`.Var` already. Returns the validated variable, which is guaranteed to be safe to add to the circuit.Nz:the type must be known when creating a 'Var' from a stringzycannot add variables that wrap `Clbit` or `ClassicalRegister` instances. Use `add_bits` or `add_register` as appropriate.rYr\#' is already present in the circuit cannot add '$' as its name shadows the existing ') r[rsrr9r^r` standaloner{rR)rrnr rpreviouss r`_prepare_new_varQuantumCircuit._prepare_new_var s k3 ' '}"#_``((,,{2CC>>"H++CHHd+C CH P"Qse+N#OPPcU2VW_V``abc c rc[U[5(a [RR U5nOUnUR UR SS9=nb&X2:Xa[SUS35e[SUSUS35eU$)zThe common logic for preparing and validating a new :class:`~.expr.Stretch` for the circuit. Returns the validated stretch, which is guaranteed to be safe to add to the circuit.Nrr\rrr)r[rsr9r_r`r{rRr)rrwrrs r`_prepare_new_stretch#QuantumCircuit._prepare_new_stretch s os + +ll&&7G%G++GLL$+G GH T""Qwi/R#STTwi'KH:UVW rc[U[5(a [RR U5nOUnUR 5R U5 U$)a5Declares a new stretch scoped to this circuit. Args: name_or_stretch: either a string of the stretch name, or an existing instance of :class:`~.expr.Stretch` to re-use. Stretches cannot shadow names that are already in use within the circuit. Returns: The created stretch. If a :class:`~.expr.Stretch` instance was given, the exact same object will be returned. Raises: CircuitError: if the stretch cannot be created due to shadowing an existing identifier. Examples: Define and use a new stretch given just a name:: from qiskit.circuit import QuantumCircuit, Duration from qiskit.circuit.classical import expr qc = QuantumCircuit(2) my_stretch = qc.add_stretch("my_stretch") qc.delay(expr.add(Duration.dt(200), my_stretch), 1) )r[rsr9r_r`rr)rrwrs r`rQuantumCircuit.add_stretch sF6 os + +ll&&7G%G ))'2rcUR5n[U[R5(a^URR [ RLa7[U[5(a"[U[5(d URnOSn[U[R"X$55n[U[5(a*[RRXR5nOUR(d [S5eUn[!XR5nUR#U5 UR%['USS55 U$)a Add a classical variable with automatic storage and scope to this circuit. The variable is considered to have been "declared" at the beginning of the circuit, but it only becomes initialized at the point of the circuit that you call this method, so it can depend on variables defined before it. Args: name_or_var: either a string of the variable name, or an existing instance of :class:`~.expr.Var` to re-use. Variables cannot shadow names that are already in use within the circuit. initial: the value to initialize this variable with. If the first argument was given as a string name, the type of the resulting variable is inferred from the initial expression; to control this more manually, either use :meth:`.Var.new` to manually construct a new variable with the desired type, or use :func:`.expr.cast` to cast the initializer to the desired type. This must be either a :class:`~.expr.Expr` node, or a value that can be lifted to one using :class:`.expr.lift`. Returns: The created variable. If a :class:`~.expr.Var` instance was given, the exact same object will be returned. Raises: CircuitError: if the variable cannot be created due to shadowing an existing identifier. Examples: Define a new variable given just a name and an initializer expression:: from qiskit.circuit import QuantumCircuit qc = QuantumCircuit(2) my_var = qc.add_var("my_var", False) Reuse a variable that may have been taken from a related circuit, or otherwise constructed manually, and initialize it to some more complicated expression:: from qiskit.circuit import QuantumCircuit, QuantumRegister, ClassicalRegister from qiskit.circuit.classical import expr, types my_var = expr.Var.new("my_var", types.Uint(8)) cr1 = ClassicalRegister(8, "cr1") cr2 = ClassicalRegister(8, "cr2") qc = QuantumCircuit(QuantumRegister(8), cr1, cr2) # Get some measurement results into each register. qc.h(0) for i in range(1, 8): qc.cx(0, i) qc.measure(range(8), cr1) qc.reset(range(8)) qc.h(0) for i in range(1, 8): qc.cx(0, i) qc.measure(range(8), cr2) # Now when we add the variable, it is initialized using the real-time state of the # two classical registers we measured into above. qc.add_var(my_var, expr.bit_and(cr1, cr2)) NzHcannot add variables that wrap `Clbit` or `ClassicalRegister` instances.rQ)rr[r9r^rmkindr:UintreboolrEliftrsr`rrrDrrrB)rrnrr7 coerce_typerstores r`rQuantumCircuit.add_var sB++-  {DHH - -  %%37C((w--%**KK  '0OP k3 ' '((,,{LL9C''Z Cc#++C0/r2>? rcUR(a [S5eUR(d [S5eURR U5 g)ayAdd a variable with no initializer. In most cases, you should use :meth:`add_var` to initialize the variable. To use this function, you must already hold a :class:`~.expr.Var` instance, as the use of the function typically only makes sense in copying contexts. .. warning:: Qiskit makes no assertions about what an uninitialized variable will evaluate to at runtime, and some hardware may reject this as an error. You should treat this function with caution, and as a low-level primitive that is useful only in special cases of programmatically rebuilding two like circuits. Args: var: the variable to add. z ))"-55c:  :: $ $^  c4<< ( ( JJ + +D,E,Ec,J K JJ ' '(=(=c4(H IrcgrZrQrrnr s r`r}QuantumCircuit.add_input sMPrcgrZrQrs r`r}r sSVrcrUR(a [S5eURR(dURR(a [S5e[ U[ R5(aUb [S5eURX5nURRU5 U$)agRegister a variable as an input to the circuit. Args: name_or_var: either a string name, or an existing :class:`~.expr.Var` node to use as the input variable. type_: if the name is given as a string, then this must be a :class:`~.types.Type` to use for the variable. If the variable is given as an existing :class:`~.expr.Var`, then this must not be given, and will instead be read from the object itself. Returns: the variable created, or the same variable as was passed in. Raises: CircuitError: if the variable cannot be created due to shadowing an existing variable. z4cannot add an input variable in a control-flow scopezAcircuits to be enclosed with captures cannot have input variablesz1cannot give an explicit type with an existing Var) rxrryrrr[r9r^rkr add_input_var)rrnr rs r`r}r s$  $ $UV V :: ' '4::+L+Lbc c k488 , ,1BPQ Q##K7   % rc^U(dg[SU55(a[U5S:Xa5[US[5(aUSS:XaSnO[ USS54nOs[U5S:XaT[ SU55(a=USS:XaSnO[ USS54nUSS:XaSnO[ USS 54nX#-nO[S U4S 35eUGHgm[T[5(aJ[U4S jURUR-55(a[S TRS35e[T[5(a5TH/nX@R;dMURRU5 M1 [T[5(aA[!USS5b["R$"SSS9 UR&R)T5 GM[T[ 5(aUR&R+T5 GM6[T[,5(aUR/T5 GM_[S5e g)zAdd registers. .. warning:: If the quantum circuit has an existing :attr:`layout` attribute, adding a :class:`.QuantumRegister` will only increase the number of qubits. It will not update the layout. Nc3B# UHn[U[5v M g7frZr[rer]s r`ra.QuantumCircuit.add_register.. s4tz#s##trrrQrc3B# UHn[U[5v M g7frZrr]s r`rar s'M 3(<(<rczwQuantumCircuit parameters can be Registers or Integers. If Integers, up to 2 arguments. QuantumCircuit was called with .c3V># UHnTRUR:Hv M g7frZr)r^r_rs r`rar s"65Lc )5Ls&)zregister name "z" already existsrzATrying to add QuantumRegister to a QuantumCircuit having a layout stacklevelzexpected a register)rirr[rerrjr$rr%rrrRr!rrzrrCwarningswarnryadd_qregadd_cregr\r)rrrrbitrs @r`r{QuantumCircuit.add_register s  4t4 4 44yA~*T!Wc":":7a<D+DGS9;DTaC'M'M$M$M7a<9;E,T!Wc:E}""WIQ( H(H--#659ZZ$**5L633#_X]]OCS#TUU(O44#C"5"55--c2$(O44440<MM[#$ ##H-H&788 ##H-Hd++ h'"#8993rc4UVs1sH%o"UR;dX R;dM#UiM' nnU(a[SU35eUHn[U[5(aUR R U5 [U[5(a@[USS5b[R"SSS9 URRU5 M[U[5(aURRU5 M[SU35e gs snf)zAdd Bits to the circuit. .. warning:: If the quantum circuit has an existing :attr:`layout` attribute, adding a :class:`.Qubit` will only increase the number of qubits. It will not update the layout. z0Attempted to add bits found already in circuit: rNz6Trying to add bits to a QuantumCircuit having a layoutrrzFExpected an instance of Qubit, Clbit, or AncillaQubit, but was passed )rrrr[r"rzrr rCrrry add_qubitr# add_clbit)rr'rduplicate_bitss r`rQuantumCircuit.add_bitss  C$*=*=#=H[H[A[C4   !QR`Qabc cC#|,,%%c*#u%%440<MMP#$ $$S)C'' $$S)"4475:  s "DDc.[U[5(aURRU$[U[5(aURR U$[ S[U535e![an[ SUS35UeSnAff=f)a7Find locations in the circuit which can be used to reference a given :obj:`~Bit`. In particular, this function can find the integer index of a qubit, which corresponds to its hardware index for a transpiled circuit. .. note:: The circuit index of a :class:`.AncillaQubit` will be its index in :attr:`qubits`, not :attr:`ancillas`. Args: bit (Bit): The bit to locate. Returns: namedtuple(int, List[Tuple(Register, int)]): A 2-tuple. The first element (``index``) contains the index at which the ``Bit`` can be found (in either :obj:`~QuantumCircuit.qubits`, :obj:`~QuantumCircuit.clbits`, depending on its type). The second element (``registers``) is a list of ``(register, index)`` pairs with an entry for each :obj:`~Register` in the circuit which contains the :obj:`~Bit` (and the index in the :obj:`~Register` at which it can be found). Raises: CircuitError: If the supplied :obj:`~Bit` was of an unknown type. CircuitError: If the supplied :obj:`~Bit` could not be found on the circuit. Examples: Loop through a circuit, getting the qubit and clbit indices of each operation:: from qiskit.circuit import QuantumCircuit, Qubit qc = QuantumCircuit(3, 3) qc.h(0) qc.cx(0, 1) qc.cx(1, 2) qc.measure([0, 1, 2], [0, 1, 2]) # The `.qubits` and `.clbits` fields are not integers. assert isinstance(qc.data[0].qubits[0], Qubit) # ... but we can use `find_bit` to retrieve them. assert qc.find_bit(qc.data[0].qubits[0]).index == 0 simple = [ ( instruction.operation.name, [qc.find_bit(bit).index for bit in instruction.qubits], [qc.find_bit(bit).index for bit in instruction.clbits], ) for instruction in qc.data ] z&Could not locate bit of unknown type: zCould not locate provided bit: z*. Has it been added to the QuantumCircuit?N) r[r ryrr#rrrmra)rrerrs r`r)QuantumCircuit.find_bit0sf #u%%zz0055C''zz0055"%KDQTI;#WXX 1#6`a  s"-A5-A5A55 B?BBc0[R"U5 g)z6Raise exception if list of qubits contains duplicates.N)rr3rrs r`r3QuantumCircuit._check_dupsos'rcSSKJn U"XUS9$)a*Create an :class:`~.circuit.Instruction` out of this circuit. .. seealso:: :func:`circuit_to_instruction` The underlying driver of this method. Args: parameter_map: For parameterized circuits, a mapping from parameters in the circuit to parameters to be used in the instruction. If None, existing circuit parameters will also parameterize the instruction. label: Optional gate label. Returns: qiskit.circuit.Instruction: a composite instruction encapsulating this circuit (can be decomposed back). r)circuit_to_instructionr-)(qiskit.converters.circuit_to_instructionr)r parameter_maprRrs r`r:QuantumCircuit.to_instructionss. T%dGGrcSSKJn U"XUS9$)a)Create a :class:`.Gate` out of this circuit. The circuit must act only on qubits and contain only unitary operations. .. seealso:: :func:`circuit_to_gate` The underlying driver of this method. Args: parameter_map: For parameterized circuits, a mapping from parameters in the circuit to parameters to be used in the gate. If ``None``, existing circuit parameters will also parameterize the gate. label : Optional gate label. Returns: Gate: a composite gate encapsulating this circuit (can be decomposed back). r)circuit_to_gater-)!qiskit.converters.circuit_to_gater)rrrRrs r`r9QuantumCircuit.to_gates, Ft%@@rcSSKJn SSKJn SSKJn U"USS9nU"USS9n[ U5HnURU5nM U"USS9$) aCall a decomposition pass on this circuit, to decompose one level (shallow decompose). Args: gates_to_decompose: Optional subset of gates to decompose. Can be a gate type, such as ``HGate``, or a gate name, such as "h", or a gate label, such as "My H Gate", or a list of any combination of these. If a gate name is entered, it will decompose all gates with that name, whether the gates have labels or not. Defaults to all gates in the circuit. reps: Optional number of times the circuit should be decomposed. For instance, ``reps=2`` equals calling ``circuit.decompose().decompose()``. Returns: QuantumCircuit: a circuit one level decomposed r) Decomposer)dag_to_circuitTr)apply_synthesisF)(qiskit.transpiler.passes.basis.decomposer qiskit.converters.circuit_to_dagr qiskit.converters.dag_to_circuitrr;run) rgates_to_decomposer=rrrdagpass_rs r` decomposeQuantumCircuit.decomposesQ, GCCT48,dCtA))C.Cc599rcSSKJn U"U40SU_SU_SU_SU_SU_SU_S U_S U_S U _S U _S U _SU _SU _SU_SU_SU_SU_SU_6$)aDraw the quantum circuit. Use the output parameter to choose the drawing format: **text**: ASCII art TextDrawing that can be printed in the console. **mpl**: images with color rendered purely in Python using matplotlib. **latex**: high-quality images compiled via latex. **latex_source**: raw uncompiled latex output. .. warning:: Support for :class:`~.expr.Expr` nodes in conditions and :attr:`.SwitchCaseOp.target` fields is preliminary and incomplete. The ``text`` and ``mpl`` drawers will make a best-effort attempt to show data dependencies, but the LaTeX-based drawers will skip these completely. Args: output: Select the output method to use for drawing the circuit. Valid choices are ``text``, ``mpl``, ``latex``, ``latex_source``. By default, the ``text`` drawer is used unless the user config file (usually ``~/.qiskit/settings.conf``) has an alternative backend set as the default. For example, ``circuit_drawer = latex``. If the output kwarg is set, that backend will always be used over the default in the user config file. scale: Scale of image to draw (shrink if ``< 1.0``). Only used by the ``mpl``, ``latex`` and ``latex_source`` outputs. Defaults to ``1.0``. filename: File path to save image to. Defaults to ``None`` (result not saved in a file). style: Style name, file name of style JSON file, or a dictionary specifying the style. * The supported style names are ``"iqp"`` (default), ``"iqp-dark"``, ``"clifford"``, ``"textbook"`` and ``"bw"``. * If given a JSON file, e.g. ``my_style.json`` or ``my_style`` (the ``.json`` extension may be omitted), this function attempts to load the style dictionary from that location. Note, that the JSON file must completely specify the visualization specifications. The file is searched for in ``qiskit/visualization/circuit/styles``, the current working directory, and the location specified in ``~/.qiskit/settings.conf``. * If a dictionary, every entry overrides the default configuration. If the ``"name"`` key is given, the default configuration is given by that style. For example, ``{"name": "textbook", "subfontsize": 5}`` loads the ``"texbook"`` style and sets the subfontsize (e.g. the gate angles) to ``5``. * If ``None`` the default style ``"iqp"`` is used or, if given, the default style specified in ``~/.qiskit/settings.conf``. interactive: When set to ``True``, show the circuit in a new window (for ``mpl`` this depends on the matplotlib backend being used supporting this). Note when used with either the `text` or the ``latex_source`` output type this has no effect and will be silently ignored. Defaults to ``False``. reverse_bits: When set to ``True``, reverse the bit order inside registers for the output visualization. Defaults to ``False`` unless the user config file (usually ``~/.qiskit/settings.conf``) has an alternative value set. For example, ``circuit_reverse_bits = True``. plot_barriers: Enable/disable drawing barriers in the output circuit. Defaults to ``True``. justify: Options are ``"left"``, ``"right"`` or ``"none"`` (str). If anything else is supplied, left justified will be used instead. It refers to where gates should be placed in the output circuit if there is an option. ``none`` results in each gate being placed in its own column. Defaults to ``left``. vertical_compression: ``high``, ``medium`` or ``low``. It merges the lines generated by the `text` output so the drawing will take less vertical room. Default is ``medium``. Only used by the ``text`` output, will be silently ignored otherwise. idle_wires: Include (or not) idle wires (wires with no circuit elements) in output visualization. The string ``"auto"`` is also possible, in which case idle wires are show except that the circuit has a layout attached. Default is ``"auto"`` unless the user config file (usually ``~/.qiskit/settings.conf``) has an alternative value set. For example, ``circuit_idle_wires = False``. with_layout: Include layout information, with labels on the physical layout. Default is ``True``. fold: Sets pagination. It can be disabled using -1. In ``text``, sets the length of the lines. This is useful when the drawing does not fit in the console. If None (default), it will try to guess the console width using ``shutil.get_terminal_size()``. However, if running in jupyter, the default line length is set to 80 characters. In ``mpl``, it is the number of (visual) layers before folding. Default is 25. ax: Only used by the `mpl` backend. An optional ``matplotlib.axes.Axes`` object to be used for the visualization output. If none is specified, a new matplotlib Figure will be created and used. Additionally, if specified there will be no returned Figure since it is redundant. initial_state: Adds :math:`|0\rangle` in the beginning of the qubit wires and :math:`0` to classical wires. Default is ``False``. cregbundle: If set to ``True``, bundle classical registers. Default is ``True``, except for when ``output`` is set to ``"text"``. wire_order: A list of integers used to reorder the display of the bits. The list must have an entry for every bit with the bits in the range 0 to (``num_qubits`` + ``num_clbits``). expr_len: The number of characters to display if an :class:`~.expr.Expr` is used for the condition in a :class:`.ControlFlowOp`. If this number is exceeded, the string will be truncated at that number and '...' added to the end. measure_arrows: If True, draw an arrow from each measure box down the the classical bit or register where the measure value is placed. If False, do not draw arrow, but instead place the name of the bit or register in the measure box. Default is ``True`` unless the user config file (usually ``~/.qiskit/settings.conf``) has an alternative value set. For example, ``circuit_measure_arrows = False``. Returns: :class:`.TextDrawing` or :class:`matplotlib.figure` or :class:`PIL.Image` or :class:`str`: * ``TextDrawing`` (if ``output='text'``) A drawing that can be printed as ascii art. * ``matplotlib.figure.Figure`` (if ``output='mpl'``) A matplotlib figure object for the circuit diagram. * ``PIL.Image`` (if ``output='latex``') An in-memory representation of the image of the circuit diagram. * ``str`` (if ``output='latex_source'``) The LaTeX source code for visualizing the circuit diagram. Raises: VisualizationError: when an invalid output method is selected ImportError: when the output methods requires non-installed libraries. Example: .. plot:: :alt: Circuit diagram output by the previous code. :include-source: from qiskit import QuantumRegister, ClassicalRegister, QuantumCircuit qc = QuantumCircuit(1, 1) qc.h(0) qc.measure(0, 0) qc.draw(output='mpl', style={'backgroundcolor': '#EEEEEE'}) r)circuit_drawerscalefilenamestyler interactive plot_barriersr.justifyvertical_compression idle_wires with_layoutfoldax initial_state cregbundle wire_orderexpr_lenmeasure_arrows)qiskit.visualizationr)rrrrrrrr.rrrrrrrrrrrrs r`rQuantumCircuit.drawst 8        $  ( &  "6 " $   ( "! ""# $% &*'  rc:[URSS5(+$N _directiveFrCrxs r`QuantumCircuit.sG KKu= 9 rc>[[XR55$)aTReturns total number of instructions in circuit. Args: filter_function (callable): a function to filter out some instructions. Should take as input a tuple of (Instruction, list(Qubit), list(Clbit)). By default, filters out "directives", such as barrier or snapshot. Returns: int: Total number of gate operations. )summapry)rfilter_functions r`sizeQuantumCircuit.size}s 3 344rc:[URSS5(+$rrrs r`rrsg KKuO K rcX^URURUR54VVs0sHo"Ho3S_M M snnmSnURGHn[ [ R "URUR55n[URSS5=nbUR[R"U5R5 [U[R5(a U"X&5 OUR[R"U5R5 O[UR[5(a2U"U[R "URR"55 OW[UR[$5(a8U"X%RR&5 U"X%RR(5 [+U4SjU5SS9nU"U5(aUS- nUHnUTU'M GM [+TR-5SS9$s snnf)aReturn 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. Args: filter_function: A function to decide which instructions count to increase depth. Should take as a single positional input a :class:`CircuitInstruction`. Instructions for which the function returns ``False`` are ignored in the computation of the circuit depth. By default, filters out "directives", such as :class:`.Barrier`. Returns: int: Depth of circuit. Examples: Simple calculation of total circuit depth:: from qiskit.circuit import QuantumCircuit qc = QuantumCircuit(4) qc.h(0) qc.cx(0, 1) qc.h(2) qc.cx(2, 3) assert qc.depth() == 2 Modifying the previous example to only calculate the depth of multi-qubit gates:: assert qc.depth(lambda instr: len(instr.qubits) > 1) == 1 rc[R"U5HVnUR(aURU5 M'UR [ R "U5R5 MX grZ)r9rraddrr(node_resourcesr)objectsnoders r`update_from_expr.QuantumCircuit.depth..update_from_exprsE~~d+>>KK$NN>#@#@#E#L#LM ,rr|Nc3.># UH nTUv M g7frZrQ)r^obj obj_depthss r`ra'QuantumCircuit.depth..s@Z_srr)rrrryrrrrCrrr(condition_resourcesr[r9rDr5rrrDrrmaxvalues) rrrr rrr} new_depthr s @r`depthQuantumCircuit.depthsZ$(;; T^^=M"N "NwZaSVFZaC"N  N ::K)//+*<*P>PQRG$[%:%:L$OO \~AA)LSSTi33$W8NN>#E#Ei#P#W#WXK11<@@ $))K4I4I4P4P*QRK11599 *?*?*F*FG *?*?*F*FG @@!LI{++Q "+ 3)&,:$$&22C sH&c6URR5$)zVReturn number of qubits plus clbits in circuit. Returns: int: Width of circuit. )rywidthrs r`rQuantumCircuit.widthszz!!rc.URR$)zReturn number of qubits.)ryrrs r`rQuantumCircuit.num_qubitsszz$$$rc,[UR5$)a;Return the number of ancilla qubits. Example: .. plot:: :include-source: :nofigs: from qiskit import QuantumCircuit, QuantumRegister, AncillaRegister # Create a 2-qubit quantum circuit reg = QuantumRegister(2) qc = QuantumCircuit(reg) # Create an ancilla register with 1 qubit anc = AncillaRegister(1) qc.add_register(anc) # Add the ancilla register to the circuit print("Number of ancilla qubits:", qc.num_ancillas) .. code-block:: text Number of ancilla qubits: 1 )rrrs r` num_ancillasQuantumCircuit.num_ancillass44==!!rc.URR$)arReturn number of classical bits. Example: .. plot:: :include-source: :nofigs: from qiskit import QuantumCircuit # Create a new circuit with two qubits and one classical bit qc = QuantumCircuit(2, 1) print("Number of classical bits:", qc.num_clbits) .. code-block:: text Number of classical bits: 1 )ryrrs r`rQuantumCircuit.num_clbitss,zz$$$rcLURR5n[U5$)zCount each operation kind in the circuit. Returns: OrderedDict: a breakdown of how many operations of each kind, sorted by amount. )ry count_opsr)rops_dicts r`rQuantumCircuit.count_ops#s! ::'')8$$rc6URR5$)zlReturn number of non-local gates (i.e. involving 2+ qubits). Conditional nonlocal gates are also included. )rynum_nonlocal_gatesrs r`r!!QuantumCircuit.num_nonlocal_gates,s zz,,..rc|URVs/sH o"RRU:XdMUPM" sn$s snf)zGet instructions matching name. Args: name (str): The name of instruction to. Returns: list(tuple): list of (instruction, qargs, cargs). )ryrrR)rrRmatchs r`get_instructionsQuantumCircuit.get_instructions3s/$(::N:%1E1E1M:NNNs99cU(a UROURUR-n[U5VVs0sHup4XC_M nnn[[ U55Vs/sHoD/PM nn[ U5nUR GHCnU(aURn [ U 5n O$URUR-n [ U 5n U S:a[ URSS5(d/n Sn U H<n X]n[U5H&nXU;dM X;dMU RU5 M: M> [[U 55n [ U 5n U S:af/nU HnURXc5 M /n[U5HnX;;dM URXc5 M URU5 UnX|S- -nUS:XdGMC U$ U$s snnfs snf)zHow many non-entangled subcircuits can the circuit be factored to. Args: unitary_only (bool): Compute only unitary part of graph. Returns: int: Number of connected components in circuit. rrFrr) rrrr;rryrCrrr\rr)r unitary_onlyr'rVr bit_indices sub_graphsnum_sub_graphsrargs num_qargsgraphs_touched num_touchedrreg_intr connections _sub_graphss r`num_connected_components'QuantumCircuit.num_connected_components>s+t{{t{{1JJSTX/0Z/hc/ 0Z(-S-='>?'>e'> ?Z ::K"))I "))K,>,>>I A~gk.C.C\SX&Y&Y!# !D)/G">2"m3 6 . 5 5a 8 % 3!"&c.&9!:!.1 ?"$K-#**:?; ."$K$^44'..z? 5 &&{3!,J"Ao5N"S&Re1[@s G" Gc URSS9$)zYComputes the number of tensor factors in the unitary (quantum) part of the circuit only. T)r()r3rs r`num_unitary_factors"QuantumCircuit.num_unitary_factors}s,,$,??rc"UR5$)zComputes the number of tensor factors in the unitary (quantum) part of the circuit only. Notes: This is here for backwards compatibility, and will be removed in a future release of Qiskit. You should call `num_unitary_factors` instead. )r6rs r`num_tensor_factors!QuantumCircuit.num_tensor_factorss''))rcdURUSS9nURR5UlU$)zCopy the circuit. Args: name (str): name to be given to the copied circuit. If None, then the name stays the same. Returns: QuantumCircuit: a deepcopy of the current circuit, with the specified name rlrm)rryr)rrRcpys r`rQuantumCircuit.copys0""46":JJOO%  ralikermcUb$[U[5(d[SUS35e[R"U5n[ X5 UR RUS9UlU(aXlU$)aReturn a copy of self with the same structure but empty. That structure includes: * name and other metadata * global phase * all the qubits and clbits, including the registers * the realtime variables defined in the circuit, handled according to the ``vars`` keyword argument. .. warning:: If the circuit contains any local variable declarations (those added by the ``declarations`` argument to the circuit constructor, or using :meth:`add_var`), they may be **uninitialized** in the output circuit. You will need to manually add store instructions for them (see :class:`.Store` and :meth:`.QuantumCircuit.store`) to initialize them. Args: name: Name for the copied circuit. If None, then the name stays the same. vars_mode: The mode to handle realtime variables in. alike The variables in the output circuit will have the same declaration semantics as in the original circuit. For example, ``input`` variables in the source will be ``input`` variables in the output circuit. Note that this causes the local variables to be uninitialised, because the stores are not copied. This can leave the circuit in a potentially dangerous state for users if they don't re-add initializer stores. captures All variables will be converted to captured variables. This is useful when you are building a new layer for an existing circuit that you will want to :meth:`compose` onto the base, since :meth:`compose` can inline captures onto the base circuit (but not other variables). drop The output circuit will have no variables defined. Returns: QuantumCircuit: An empty copy of self. zinvalid name for a circuit: 'z''. The name must be a string or 'None'.rm) r[rsrlrr_copy_metadataryrrR)rrRrnr<s r`rQuantumCircuit.copy_empty_likesn` 4 5 5/v5\] jjt!JJ...C H rcZURR5 URUlg)a*Clear all instructions in self. Clearing the circuits will keep the metadata. .. seealso:: :meth:`copy_empty_like` A method to produce a new circuit with no instructions and all the same tracking of quantum and classical typed data, but without mutating the original circuit. N)ryrrSrs r`rQuantumCircuit.clears"  --rcX RVs/sHo3RPM sn;a[R"X5nU$[X5nU$s snf)zCCreates a creg, checking if ClassicalRegister with same name exists)rrRr$_new_with_prefix)rlengthrRcregnew_cregs r` _create_cregQuantumCircuit._create_cregsJ **5*$II*5 5(99&GH)6H 6AcX RVs/sHo3RPM sn;a[R"X5nU$[X5nU$s snf)zACreates a qreg, checking if QuantumRegister with same name exists)rrRrrE)rrFrRqregnew_qregs r` _create_qregQuantumCircuit._create_qregsJ **5*$II*5 5&77EH'v4H 6rKc>SSKJn URU"5U//SS9$)zReset the quantum bit(s) to their default state. Args: qubit: qubit(s) to reset. Returns: qiskit.circuit.InstructionSet: handle to the added instruction. r)ResetFr)resetrRr)rrrRs r`rSQuantumCircuit.resets" !{{57UGRe{<D KKdjj$** 53 K?KVs GG: GGcpSSKJn URUURURUR SS9$)aGRead an OpenQASM 2.0 program from a file and convert to an instance of :class:`.QuantumCircuit`. Args: path (str): Path to the file for an OpenQASM 2 program Return: QuantumCircuit: The QuantumCircuit object for the input OpenQASM 2. See also: :func:`.qasm2.load`: the complete interface to the OpenQASM 2 importer. rqasm2F include_pathcustom_instructionscustom_classicalstrict)qiskitrtloadLEGACY_INCLUDE_PATHLEGACY_CUSTOM_INSTRUCTIONSLEGACY_CUSTOM_CLASSICAL)pathrts r`from_qasm_fileQuantumCircuit.from_qasm_file%s> !zz 22 % @ @"::   rcpSSKJn URUURURUR SS9$)a>Convert a string containing an OpenQASM 2.0 program to a :class:`.QuantumCircuit`. Args: qasm_str (str): A string containing an OpenQASM 2.0 program. Return: QuantumCircuit: The QuantumCircuit object for the input OpenQASM 2 See also: :func:`.qasm2.loads`: the complete interface to the OpenQASM 2 importer. rrsFru)rzrtloadsr|r}r~)qasm_strrts r` from_qasm_strQuantumCircuit.from_qasm_str>s> !{{ 22 % @ @"::   rcUR(aURSR$URR$)aFThe global phase of the current circuit scope in radians. Example: .. plot:: :include-source: :nofigs: :context: reset from qiskit import QuantumCircuit circuit = QuantumCircuit(2) circuit.h(0) circuit.cx(0, 1) print(circuit.global_phase) .. code-block:: text 0.0 .. plot:: :include-source: :nofigs: :context: from numpy import pi circuit.global_phase = pi/4 print(circuit.global_phase) .. code-block:: text 0.7853981633974483 r&rxrSryrs r`rSQuantumCircuit.global_phaseUs5J  $ $,,R0== =zz&&&rcnUR(aXRSlgXRlg)zcSet the phase of the current circuit scope. Args: angle (float, ParameterExpression): radians r&Nr)rangles r`rSr~s(  $ $9> % %b ) 6&+JJ #rc@[URR5$)u The parameters defined in the circuit. This attribute returns the :class:`.Parameter` objects in the circuit sorted alphabetically. Note that parameters instantiated with a :class:`.ParameterVector` are still sorted numerically. Examples: The snippet below shows that insertion order of parameters does not matter. .. plot:: :include-source: :nofigs: >>> from qiskit.circuit import QuantumCircuit, Parameter >>> a, b, elephant = Parameter("a"), Parameter("b"), Parameter("elephant") >>> circuit = QuantumCircuit(1) >>> circuit.rx(b, 0) >>> circuit.rz(elephant, 0) >>> circuit.ry(a, 0) >>> circuit.parameters # sorted alphabetically! ParameterView([Parameter(a), Parameter(b), Parameter(elephant)]) Bear in mind that alphabetical sorting might be unintuitive when it comes to numbers. The literal "10" comes before "2" in strict alphabetical sorting. .. plot:: :include-source: :nofigs: >>> from qiskit.circuit import QuantumCircuit, Parameter >>> angles = [Parameter("angle_1"), Parameter("angle_2"), Parameter("angle_10")] >>> circuit = QuantumCircuit(1) >>> circuit.u(*angles, 0) >>> circuit.draw() ┌─────────────────────────────┐ q: ┤ U(angle_1,angle_2,angle_10) ├ └─────────────────────────────┘ >>> circuit.parameters ParameterView([Parameter(angle_1), Parameter(angle_10), Parameter(angle_2)]) To respect numerical sorting, a :class:`.ParameterVector` can be used. .. plot:: :include-source: :nofigs: >>> from qiskit.circuit import QuantumCircuit, Parameter, ParameterVector >>> x = ParameterVector("x", 12) >>> circuit = QuantumCircuit(1) >>> for x_i in x: ... circuit.rx(x_i, 0) >>> circuit.parameters ParameterView([ ParameterVectorElement(x[0]), ParameterVectorElement(x[1]), ParameterVectorElement(x[2]), ParameterVectorElement(x[3]), ..., ParameterVectorElement(x[11]) ]) Returns: The sorted :class:`.Parameter` objects in the circuit. )r=ryrGrs r`rGQuantumCircuit.parameterssDTZZ2233rc6URR5$)z/The number of parameter objects in the circuit.)ryrFrs r`rFQuantumCircuit.num_parametersszz((**rc6URR5$)a6Efficiently get all parameters in the circuit, without any sorting overhead. .. warning:: The returned object may directly view onto the ``ParameterTable`` internals, and so should not be mutated. This is an internal performance detail. Code outside of this package should not use this method. )ryunsorted_parametersrs r`_unsorted_parameters#QuantumCircuit._unsorted_parametersszz--//r) flat_inputrycgrZrQrrGrrrys r`assign_parameters QuantumCircuit.assign_parameterssrcgrZrQrs r`rrsrcU(aUnO[[U[5(dURRnUR 5nUR 5 UR 5 [U[RR5(aU(aUOURX5nU(aVUVs/sHoRU5(aMUPM sn=n (a%[SSRSU 55S35eURRU5 OURRU5 U(aS$U$s snf)aO Assign parameters to new parameters or values. If ``parameters`` is passed as a dictionary, the keys should be :class:`.Parameter` instances in the current circuit. The values of the dictionary can either be numeric values or new parameter objects. If ``parameters`` is passed as a list or array, the elements are assigned to the current parameters in the order of :attr:`parameters` which is sorted alphabetically (while respecting the ordering in :class:`.ParameterVector` objects). The values can be assigned to the current circuit object or to a copy of it. .. note:: When ``parameters`` is given as a mapping, it is permissible to have keys that are strings of the parameter names; these will be looked up using :meth:`get_parameter`. You can also have keys that are :class:`.ParameterVector` instances, and in this case, the dictionary value should be a sequence of values of the same length as the vector. If you use either of these cases, you must leave the setting ``flat_input=False``; changing this to ``True`` enables the fast path, where all keys must be :class:`.Parameter` instances. Args: parameters: Either a dictionary or iterable specifying the new parameter values. inplace: If False, a copy of the circuit with the bound parameters is returned. If True the circuit instance itself is modified. flat_input: If ``True`` and ``parameters`` is a mapping type, it is assumed to be exactly a mapping of ``{parameter: value}``. By default (``False``), the mapping may also contain :class:`.ParameterVector` keys that point to a corresponding sequence of values, and these will be unrolled during the mapping, or string keys, which will be converted to :class:`.Parameter` instances using :meth:`get_parameter`. strict: If ``False``, any parameters given in the mapping that are not used in the circuit will be ignored. If ``True`` (the default), an error will be raised indicating a logic error. Raises: CircuitError: If parameters is a dict and contains parameters not present in the circuit. ValueError: If parameters is a list/array and the length mismatches the number of free parameters in the circuit. Returns: A copy of the circuit with bound parameters if ``inplace`` is False, otherwise None. Examples: 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 circuit = QuantumCircuit(2) params = [Parameter('A'), Parameter('B'), Parameter('C')] circuit.ry(params[0], 0) circuit.crx(params[1], 0, 1) circuit.draw('mpl') circuit.assign_parameters({params[0]: params[2]}, inplace=True) circuit.draw('mpl') 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 circuit = QuantumCircuit(2) params = ParameterVector('P', 2) circuit.ry(params[0], 0) circuit.crx(params[1], 0, 1) bound_circuit = circuit.assign_parameters([1, 2]) bound_circuit.draw('mpl') circuit.draw('mpl') zCannot bind parameters (z, c38# UHn[U5v M g7frZ)rs)r^rs r`ra3QuantumCircuit.assign_parameters..bs8PAQrgz) not present in the circuit.N)r[rryrGrrtrr collectionsabcr _unroll_param_dictrerjoinassign_parameters_mappingassign_parameters_iterable) rrGrrryrr raw_mappingrbextrass r`rrst Fj$//JJ))YY[F  ' ' )    ! j+//"9"9 : :(2*8O8OPZ8cK/:/:)BTBTU^B_I{#.tyy8P8P/P.QR$$ LL 2 2; ? LL 3 3J ?t*F*s 4EEc6URR5$)zeChecks whether the circuit has an instance of :class:`.ControlFlowOp` present amongst its operations.)ryhas_control_flow_oprs r`r"QuantumCircuit.has_control_flow_oplszz--//rc 0nUR5HupE[U[5(ae[U5[U5:wa1[ SUR S[U5S[U5S35eUR [XE55 M[U[5(aPU(aXSURU5'U(d-URU5(aXSURU5'MMMXSU'M U$)NzParameter vector 'z ' has length z, but was assigned to z values.) rr[r>rrrRrrrsrZre)rparameter_bindsryrrbrs r`r!QuantumCircuit._unroll_param_dictqs / 5 5 7 I)_55y>SZ/&,Y^^,**956$"4"4Y"?"?9>**956#@v"'I!8 rr-c SSKJn U(a_[UVVs0sHo@RU5HoUS_M M snn5nUR [ U"[ U5US9US5SS9$URR5nUR5R [ U"[ U5US9US55$s snnf)a2Apply :class:`~.library.Barrier`. If ``qargs`` is empty, applies to all qubits in the circuit. Args: qargs (QubitSpecifier): Specification for one or more qubit arguments. label (str): The string label of the barrier. Returns: qiskit.circuit.InstructionSet: handle to the added instructions. r)BarrierNr-rQFr) r<rrorrrBrrrr)rrRrrr8rrs r`r<QuantumCircuit.barriers % %*YUT4R4RSW4XqD4XUYF;;"73v;e#DfbQX] [[%%'F&&(//"73v;e#DfbQ Zs$B? cTUc URnUR[XS9U//SS9$)aBApply :class:`~.circuit.Delay`. If qarg is ``None``, applies to all qubits. When applying to multiple qubits, delays with the same duration will be created. Args: duration (Object): duration of the delay. If this is an :class:`~.expr.Expr`, it must be a constant expression of type :class:`~.types.Duration`. qarg (Object): qubit argument to apply this delay. unit (str | None): unit of the duration, unless ``duration`` is an :class:`~.expr.Expr` in which case it must not be specified. Supported units: ``'s'``, ``'ms'``, ``'us'``, ``'ns'``, ``'ps'``, and ``'dt'``. Default is ``'dt'``, i.e. integer time unit depending on the target backend. Returns: qiskit.circuit.InstructionSet: handle to the added instructions. Raises: CircuitError: if arguments have bad format. )rFr)rrrC)rrr8rs r`delayQuantumCircuit.delays02 <;;D{{55vr{NNrcFUR[RU/S5$)zApply :class:`~qiskit.circuit.library.HGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: qubit: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. rQ)r;rHrrs r`hQuantumCircuit.h)),..5'2FFrcUbUS;a!UR[RX/SUS9$SSKJn UR U"X4S9X//SS9$) aApply :class:`~qiskit.circuit.library.CHGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: control_qubit: The qubit(s) used as the control. target_qubit: The qubit(s) targeted by the gate. label: The string label of the gate in the circuit. ctrl_state: The control state in decimal, or as a bitstring (e.g. '1'). Defaults to controlling on the '1' state. Returns: A handle to the instructions created. 1rrQr-r)CHGaterRrSFr)r;rCHlibrary.standard_gates.hrr)r control_qubit target_qubitrRrSrs r`chQuantumCircuit.chh.  x!7---!>%.  5{{  6  )    rcFUR[RU/S5$)zApply :class:`~qiskit.circuit.library.IGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: qubit: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. rQ)r;rIrs r`idQuantumCircuit.idrrcPSSKJn URU"[U5U5USS9$)a Apply :class:`~qiskit.circuit.library.MSGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: theta: The angle of the rotation. qubits: The qubits to apply the gate to. Returns: A handle to the instructions created. r)MSGateFr)library.generalized_gates.gmsrrr)rthetarrs r`msQuantumCircuit.mss' :{{6#f+u5vE{JJrcHUR[RU/U45$)aApply :class:`~qiskit.circuit.library.PhaseGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: theta: THe angle of the rotation. qubit: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. )r;rPhase)rrrs r`pQuantumCircuit.ps#)),*<*':Q'> ? #$(99" 7? O GGEAIx (>"a'q)84^$)*N1,=xH'.8;KK+C,?@ S&$ 7 GGUFQJ )>"a'q)84^$)*N1,=xH'.8;KK+C,?@ S&$ 7 [ n%Cax"1% $3q"a1q>&:; #" $3-5M!$^!4$3  UN^$CT R MdVSTUV Vrc>SSKJnJn SSKJn UR U5nUR U5n [ U 5S:wa [S5eX-n U Sn URU 5 [ U5n U S:Xa}U(aZURSSUS- U 5 URUSU 5 URSSU*S- U 5 URUSU 5 g URU"U5X/-5 g U"U"U5[ U5US9n URXU /-SS 9 g ) z Apply Multiple-Controlled Z rotation gate Args: lam: The angle of the rotation. q_controls: The qubits used as the controls. q_target: The qubit targeted by the gate. use_basis_gates: use p, u, cx basis gates. r)CRZGateRZGater)rz-The mcrz gate needs a single qubit as target.rrTrN) library.standard_gates.rzrrrrrrrr3urrr) rrrrrrrrrrrrrs r`mcrzQuantumCircuit.mcrzs" ?J77 C55h? |  !MN N#2 #A  $.! !8q!S1Wl3q)<8q!cTAX|4q)<8 GCL.>*IJ(s  0 /E LL, ?L NrcHUR[RU/X/5$)aIApply :class:`~qiskit.circuit.library.RGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: theta: The angle of the rotation. phi: The angle of the axis of rotation in the x-y plane. qubit: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. )r;rR)rrphirs r`rQuantumCircuit.r2s!)),..5'E<PPrcBSSKJn URU"XU5U//SS9$)aApply :class:`~qiskit.circuit.library.RVGate`. For the full matrix form of this gate, see the underlying gate documentation. Rotation around an arbitrary rotation axis :math:`v`, where :math:`|v|` is the angle of rotation in radians. Args: vx: x-component of the rotation axis. vy: y-component of the rotation axis. vz: z-component of the rotation axis. qubit: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. r)RVGateFr)library.generalized_gates.rvrr)rvxvyvzrrs r`rvQuantumCircuit.rvCs'. 9{{6""-w{GGrcHUR[RXU/S5$)aiApply :class:`~qiskit.circuit.library.RCCXGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: control_qubit1: The qubit(s) used as the first control. control_qubit2: The qubit(s) used as the second control. target_qubit: The qubit(s) targeted by the gate. Returns: A handle to the instructions created. rQ)r;rRCCX)rcontrol_qubit1control_qubit2rs r`rccxQuantumCircuit.rccx^s)$))    Mr  rcHUR[RXX4/S5$)aApply :class:`~qiskit.circuit.library.RC3XGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: control_qubit1: The qubit(s) used as the first control. control_qubit2: The qubit(s) used as the second control. control_qubit3: The qubit(s) used as the third control. target_qubit: The qubit(s) targeted by the gate. Returns: A handle to the instructions created. rQ)r;rRC3X)rrrcontrol_qubit3rs r`rcccxQuantumCircuit.rcccxts+())    ^ J   rcFUR[RU/U/US9$)aJApply :class:`~qiskit.circuit.library.RXGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: theta: The rotation angle of the gate. qubit: The qubit(s) to apply the gate to. label: The string label of the gate in the circuit. Returns: A handle to the instructions created. r-)r;rRXrrrrRs r`rxQuantumCircuit.rx')),//E7UGSX)YYrcUbUS;a"UR[RX#/U/US9$SSKJn UR U"XUS9X#//SS9$)a Apply :class:`~qiskit.circuit.library.CRXGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: theta: The angle of the rotation. control_qubit: The qubit(s) used as the control. target_qubit: The qubit(s) targeted by the gate. label: The string label of the gate in the circuit. ctrl_state: The control state in decimal, or as a bitstring (e.g. '1'). Defaults to controlling on the '1' state. Returns: A handle to the instructions created. rr-r)CRXGaterFr)r;rCRXrr)r)rrrrrRrSr)s r`crxQuantumCircuit.crxo2  x!7--  ="?%PU.  7{{ E: >  )    rcHUR[RX#/U/5$)a>Apply :class:`~qiskit.circuit.library.RXXGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: theta: The angle of the rotation. qubit1: The qubit(s) to apply the gate to. qubit2: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. )r;rRXXrrqubit1qubit2s r`rxxQuantumCircuit.rxx$)),*:*:VNPRSSrcUbUS;a"UR[RXU/SUS9$SSKJn UR U"XES9XU//SS9$) a$Apply :class:`~qiskit.circuit.library.CSwapGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: control_qubit: The qubit(s) used as the control. target_qubit1: The qubit(s) targeted by the gate. target_qubit2: The qubit(s) targeted by the gate. label: The string label of the gate in the circuit. ctrl_state: The control state in decimal, or as a bitstring (e.g. ``'1'``). Defaults to controlling on the ``'1'`` state. Returns: A handle to the instructions created. rrQr-r) CSwapGaterFr)r;rCSwaplibrary.standard_gates.swaprsr)rr target_qubit1 target_qubit2rRrSrss r`cswapQuantumCircuit.cswapsq2  x!7--""}= .  ;{{ E 9 = 9    rcFUR[RU/S5$)zApply :class:`~qiskit.circuit.library.SXGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: qubit: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. rQ)r;rSXrs r`sxQuantumCircuit.sx0s)),//E7BGGrcFUR[RU/S5$)zApply :class:`~qiskit.circuit.library.SXdgGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: qubit: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. rQ)r;rSXdgrs r`sxdgQuantumCircuit.sxdg=s!)),*;*;eWbIIrcUbUS;a!UR[RX/SUS9$SSKJn UR U"X4S9X//SS9$) aApply :class:`~qiskit.circuit.library.CSXGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: control_qubit: The qubit(s) used as the control. target_qubit: The qubit(s) targeted by the gate. label: The string label of the gate in the circuit. ctrl_state: The control state in decimal, or as a bitstring (e.g. '1'). Defaults to controlling on the '1' state. Returns: A handle to the instructions created. rrQr-r)CSXGaterFr)r;rCSXlibrary.standard_gates.sxrr)rrrrRrSrs r`csxQuantumCircuit.csxJsj.  x!7--  ="?5.  7{{ % 7  )    rcFUR[RU/S5$)zApply :class:`~qiskit.circuit.library.TGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: qubit: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. rQ)r;rrKrs r`tQuantumCircuit.torrcFUR[RU/S5$)zApply :class:`~qiskit.circuit.library.TdgGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: qubit: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. rQ)r;rTdgrs r`tdgQuantumCircuit.tdg|r^rcJUR[RU/XU/5$)aApply :class:`~qiskit.circuit.library.UGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: theta: The :math:`\theta` rotation angle of the gate. phi: The :math:`\phi` rotation angle of the gate. lam: The :math:`\lambda` rotation angle of the gate. qubit: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. )r;rU)rrr rrs r`rQuantumCircuit.us%()),..5'EPSCTUUrc UbUS;a#UR[RXV/XX4/US9$SSKJn UR U "XX4XxS9XV//SS9$)aApply :class:`~qiskit.circuit.library.CUGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: theta: The :math:`\theta` rotation angle of the gate. phi: The :math:`\phi` rotation angle of the gate. lam: The :math:`\lambda` rotation angle of the gate. gamma: The global phase applied of the U gate, if applied. control_qubit: The qubit(s) used as the control. target_qubit: The qubit(s) targeted by the gate. label: The string label of the gate in the circuit. ctrl_state: The control state in decimal, or as a bitstring (e.g. '1'). Defaults to controlling on the '1' state. Returns: A handle to the instructions created. rr-r)CUGaterFr)r;rCUlibrary.standard_gates.urr) rrr rgammarrrRrSrs r`cuQuantumCircuit.cust>  x!7---S( .  5{{ 5s N  )    rcDUR[RU/SUS9$)aApply :class:`~qiskit.circuit.library.XGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: qubit: The qubit(s) to apply the gate to. label: The string label of the gate in the circuit. Returns: A handle to the instructions created. rQr-)r;rX)rrrRs r`rQuantumCircuit.xs$)),..5'2U)SSrcUbUS;a!UR[RX/SUS9$SSKJn UR U"X4S9X//SS9$) aApply :class:`~qiskit.circuit.library.CXGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: control_qubit: The qubit(s) used as the control. target_qubit: The qubit(s) targeted by the gate. label: The string label of the gate in the circuit. ctrl_state: The control state in decimal, or as a bitstring (e.g. '1'). Defaults to controlling on the '1' state. Returns: A handle to the instructions created. rrQr-r)CXGaterFr)r;rCXlibrary.standard_gates.xrr)rrrrRrSrs r`rQuantumCircuit.cxk.  x!7--- .  5{{  6  )    rcFUR[RX/S5$)aApply :class:`~qiskit.circuit.library.DCXGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: qubit1: The qubit(s) to apply the gate to. qubit2: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. rQ)r;rDCXrTs r`dcxQuantumCircuit.dcxs")),*:*:V  6{{ z * \ :    rz2.1zInstead, add a generic MCXGate to the circuit and specify the synthesis method via the ``hls_config`` in the transpilation. Alternatively, specific decompositions are available at https://qisk.it/mcx.)rRradditional_msgcSSKJnJnJn [ U5n 1Skn U(aUR U5n UcU"XS9n OYXJ;aCUS:XaU"XS9n OGUS;aU"XS9n O:US;a U"U S US9n O+US ;a U"U S US 9n O[ S 5e[ SUSU 35eUb[U S5(d/nO[R"5 [R"S[SS9 U Rn SSS5 W S:aXUc[SU S35e[US5(dU/n[ U5U :a[ U5n[ SU SUS35eUSU nO/nURXSSU/-USS-/5$!,(df  N=f)aApply :class:`~qiskit.circuit.library.MCXGate`. The multi-cX gate can be implemented using different techniques, which use different numbers of ancilla qubits and have varying circuit depth. These modes are: - ``'noancilla'``: Requires 0 ancilla qubits. - ``'recursion'``: Requires 1 ancilla qubit if more than 4 controls are used, otherwise 0. - ``'v-chain'``: Requires 2 less ancillas than the number of control qubits. - ``'v-chain-dirty'``: Same as for the clean ancillas (but the circuit will be longer). For the full matrix form of this gate, see the underlying gate documentation. Args: control_qubits: The qubits used as the controls. target_qubit: The qubit(s) targeted by the gate. ancilla_qubits: The qubits used as the ancillae, if the mode requires them. mode: The choice of mode, explained further above. ctrl_state: The control state in decimal, or as a bitstring (e.g. '1'). Defaults to controlling on the '1' state. Returns: A handle to the instructions created. Raises: ValueError: if the given mode is not known, or if too few ancilla qubits are passed. AttributeError: if no ancilla qubits are passed, but some are needed. r)MCXGate MCXRecursive MCXVChain>radvancedr recursionv-chain v-chain-dirtybasic-dirty-ancillaNrr)rr)rrF)rrT)dirty_ancillasrSz unreachable.zUnsupported mode (z) selected, choose one of num_ancilla_qubitsignorerz)categorymodulerzNo ancillas provided, but z are needed!rz At least z ancillas required, but z given.)rrrrrrrkrArcatch_warningsfilterwarningsDeprecationWarningrrr)rrrancilla_qubitsrrSrrrrQavailable_implementationsrrJrequiredactuallys r`rQuantumCircuit.mcx:sZ ONn-% ! ..~>A <?BD  .{"F22#OK-- %JOAA R\] 00$TF*DE^D_`  2H$#H:-EhZwW"0 !:!#{{4!2l^!CnUVFW!WY[\\-+*s 'E// E=cFUR[RU/S5$)zApply :class:`~qiskit.circuit.library.YGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: qubit: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. rQ)r;rYrs r`yQuantumCircuit.yrrcUbUS;a!UR[RX/SUS9$SSKJn UR U"X4S9X//SS9$) aApply :class:`~qiskit.circuit.library.CYGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: control_qubit: The qubit(s) used as the controls. target_qubit: The qubit(s) targeted by the gate. label: The string label of the gate in the circuit. ctrl_state: The control state in decimal, or as a bitstring (e.g. '1'). Defaults to controlling on the '1' state. Returns: A handle to the instructions created. rrQr-r)CYGaterFr)r;rCYlibrary.standard_gates.yrr)rrrrRrSrs r`cyQuantumCircuit.cyrrcFUR[RU/S5$)zApply :class:`~qiskit.circuit.library.ZGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: qubit: The qubit(s) to apply the gate to. Returns: A handle to the instructions created. rQ)r;rZrs r`zQuantumCircuit.zrrcUbUS;a!UR[RX/SUS9$SSKJn UR U"X4S9X//SS9$) aApply :class:`~qiskit.circuit.library.CZGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: control_qubit: The qubit(s) used as the controls. target_qubit: The qubit(s) targeted by the gate. label: The string label of the gate in the circuit. ctrl_state: The control state in decimal, or as a bitstring (e.g. '1'). Defaults to controlling on the '1' state. Returns: A handle to the instructions created. rrQr-r)CZGaterFr)r;rCZlibrary.standard_gates.zrr)rrrrRrSrs r`czQuantumCircuit.czrrcUbUS;a"UR[RXU/SUS9$SSKJn UR U"XES9XU//SS9$) a)Apply :class:`~qiskit.circuit.library.CCZGate`. For the full matrix form of this gate, see the underlying gate documentation. Args: control_qubit1: The qubit(s) used as the first control. control_qubit2: The qubit(s) used as the second control. target_qubit: The qubit(s) targeted by the gate. label: The string label of the gate in the circuit. ctrl_state: The control state in decimal, or as a bitstring (e.g. '10'). Defaults to controlling on the '11' state. Returns: A handle to the instructions created. rrQr-r)CCZGaterFr)r;rCCZrrr)rrrrrRrSrs r`cczQuantumCircuit.cczsq2  y!8--  > .  6{{ % 7 \ :    rc>SSKJn URU"U5U/SS9$)zApply :class:`~qiskit.circuit.library.PauliGate`. Args: pauli_string: A string representing the Pauli operator to apply, e.g. 'XX'. qubits: The qubits to apply this gate to. Returns: A handle to the instructions created. r) PauliGateFr).qiskit.circuit.library.generalized_gates.paulirr)r pauli_stringrrs r`pauliQuantumCircuit.pauli8s$ M{{9\2FBU{KKrc SSKJn Uc URnO2[U[[ R [[45(aU/n[U[5(a [U5OSnURU"XX4S9USS9$)u Prepare qubits in a specific state. This class implements a state preparing unitary. Unlike :meth:`.initialize` it does not reset the qubits first. Args: state: The state to initialize to, can be either of the following. * Statevector or vector of complex amplitudes to initialize to. * Labels of basis states of the Pauli eigenstates Z, X, Y. See :meth:`.Statevector.from_label`. Notice the order of the labels is reversed with respect to the qubit index to be applied to. Example label '01' initializes the qubit zero to :math:`|1\rangle` and the qubit one to :math:`|0\rangle`. * An integer that is used as a bitmap indicating which qubits to initialize to :math:`|1\rangle`. Example: setting params to 5 would initialize qubit 0 and qubit 2 to :math:`|1\rangle` and qubit 1 to :math:`|0\rangle`. qubits: Qubits to initialize. If ``None`` the initialization is applied to all qubits in the circuit. label: An optional label for the gate normalize: Whether to normalize an input array to a unit vector. Returns: A handle to the instruction that was just initialized Examples: Prepare a qubit in the state :math:`(|0\rangle - |1\rangle) / \sqrt{2}`. .. plot:: :include-source: :nofigs: import numpy as np from qiskit import QuantumCircuit circuit = QuantumCircuit(1) circuit.prepare_state([1/np.sqrt(2), -1/np.sqrt(2)], 0) circuit.draw() output: .. code-block:: text ┌─────────────────────────────────────┐ q_0: ┤ State Preparation(0.70711,-0.70711) ├ └─────────────────────────────────────┘ Prepare from a string two qubits in the state :math:`|10\rangle`. The order of the labels is reversed with respect to qubit index. More information about labels for basis states are in :meth:`.Statevector.from_label`. .. plot:: :include-source: :nofigs: import numpy as np from qiskit import QuantumCircuit circuit = QuantumCircuit(2) circuit.prepare_state('01', circuit.qubits) circuit.draw() output: .. code-block:: text ┌─────────────────────────┐ q_0: ┤0 ├ │ State Preparation(0,1) │ q_1: ┤1 ├ └─────────────────────────┘ Initialize two qubits from an array of complex amplitudes .. plot:: :include-source: :nofigs: import numpy as np from qiskit import QuantumCircuit circuit = QuantumCircuit(2) circuit.prepare_state([0, 1/np.sqrt(2), -1.j/np.sqrt(2), 0], circuit.qubits) circuit.draw() output: .. code-block:: text ┌───────────────────────────────────────────┐ q_0: ┤0 ├ │ State Preparation(0,0.70711,-0.70711j,0) │ q_1: ┤1 ├ └───────────────────────────────────────────┘ r)StatePreparationN)rR normalizeFr) 'qiskit.circuit.library.data_preparationrrr[rerDrEslicer rr)rstaterrRrrrs r` prepare_stateQuantumCircuit.prepare_stateJsuT M >[[F bjj% ? @ @XF$.uc$:$:S[ {{ Ue Q   rcSSKJn Uc URnO2[U[[ R [[45(aU/n[U[5(a [U5OSnURU"XU5USS9$)u Initialize qubits in a specific state. Qubit initialization is done by first resetting the qubits to :math:`|0\rangle` followed by calling :class:`~qiskit.circuit.library.StatePreparation` class to prepare the qubits in a specified state. Both these steps are included in the :class:`~qiskit.circuit.library.Initialize` instruction. Args: params: The state to initialize to, can be either of the following. * Statevector or vector of complex amplitudes to initialize to. * Labels of basis states of the Pauli eigenstates Z, X, Y. See :meth:`.Statevector.from_label`. Notice the order of the labels is reversed with respect to the qubit index to be applied to. Example label ``'01'`` initializes the qubit zero to :math:`|1\rangle` and the qubit one to :math:`|0\rangle`. * An integer that is used as a bitmap indicating which qubits to initialize to :math:`|1\rangle`. Example: setting params to 5 would initialize qubit 0 and qubit 2 to :math:`|1\rangle` and qubit 1 to :math:`|0\rangle`. qubits: Qubits to initialize. If ``None`` the initialization is applied to all qubits in the circuit. normalize: Whether to normalize an input array to a unit vector. Returns: A handle to the instructions created. Examples: Prepare a qubit in the state :math:`(|0\rangle - |1\rangle) / \sqrt{2}`. .. plot:: :include-source: :nofigs: import numpy as np from qiskit import QuantumCircuit circuit = QuantumCircuit(1) circuit.initialize([1/np.sqrt(2), -1/np.sqrt(2)], 0) circuit.draw() output: .. code-block:: text ┌──────────────────────────────┐ q_0: ┤ Initialize(0.70711,-0.70711) ├ └──────────────────────────────┘ Initialize from a string two qubits in the state :math:`|10\rangle`. The order of the labels is reversed with respect to qubit index. More information about labels for basis states are in :meth:`.Statevector.from_label`. .. plot:: :include-source: :nofigs: import numpy as np from qiskit import QuantumCircuit circuit = QuantumCircuit(2) circuit.initialize('01', circuit.qubits) circuit.draw() output: .. code-block:: text ┌──────────────────┐ q_0: ┤0 ├ │ Initialize(0,1) │ q_1: ┤1 ├ └──────────────────┘ Initialize two qubits from an array of complex amplitudes. .. plot:: :include-source: :nofigs: import numpy as np from qiskit import QuantumCircuit circuit = QuantumCircuit(2) circuit.initialize([0, 1/np.sqrt(2), -1.j/np.sqrt(2), 0], circuit.qubits) circuit.draw() output: .. code-block:: text ┌────────────────────────────────────┐ q_0: ┤0 ├ │ Initialize(0,0.70711,-0.70711j,0) │ q_1: ┤1 ├ └────────────────────────────────────┘ r) InitializeNFr) $library.data_preparation.initializerrrr[rerDrErr rr)rr6rrrrs r` initializeQuantumCircuit.initializeslT E >[[F bjj% ? @ @XF$.vs$;$;S[ {{:f)DfSX{YYrcSSKJn U"XS9nURS:Xa-[U[[ 45(d[ U5S:aU/nURXR/SS9$)awApply unitary gate specified by ``obj`` to ``qubits``. Args: obj: Unitary operator. qubits: The circuit qubits to apply the transformation to. label: Unitary name for backend [Default: None]. Returns: QuantumCircuit: The quantum circuit. Example: Apply a gate specified by a unitary matrix to a quantum circuit .. plot:: :include-source: :nofigs: from qiskit import QuantumCircuit matrix = [[0, 0, 0, 1], [0, 0, 1, 0], [1, 0, 0, 0], [0, 1, 0, 0]] circuit = QuantumCircuit(2) circuit.unitary(matrix, [0, 1]) r) UnitaryGater-Fr)!library.generalized_gates.unitaryrrr[rer rr)rr rrRrrJs r`unitaryQuantumCircuit.unitary8sXB C3, ??a &3,//3v;? {{4%{88rcUR5nUH,nURU5HnURU5 M M. g)aMark the given qubit(s) as used within the current scope, without adding an operation. This has no effect (other than raising an exception on invalid input) when called in the top scope of a :class:`QuantumCircuit`. Within a control-flow builder, this causes the qubit to be "used" by the control-flow block, if it wouldn't already be used, without adding any additional operations on it. For example:: from qiskit.circuit import QuantumCircuit qc = QuantumCircuit(3) with qc.box(): # This control-flow block will only use qubits 0 and 1. qc.cx(0, 1) with qc.box(): # This control-flow block will contain only the same operation as the previous # block, but it will also mark qubit 2 as "used" by the box. qc.cx(0, 1) qc.noop(2) Args: *qargs: variadic list of valid qubit specifiers. Anything that can be passed as a qubit or collection of qubits is valid for each argument here. Raises: CircuitError: if any requested qubit is not valid for the circuit. N)rr use_qubit)rrscoper8rs r`noopQuantumCircuit.noopes?:##%D77=&>rcZUR(aURS$UR$)Nr&)rxrvrs r`rQuantumCircuit._current_scopes(  $ $,,R0 0   rc nURR[UUUR5UUUS95 g)aAdd a scope for collecting instructions into this circuit. This should only be done by the control-flow context managers, which will handle cleaning up after themselves at the end as well. Args: qubits: Any qubits that this scope should automatically use. clbits: Any clbits that this scope should automatically use. allow_jumps: Whether this scope allows jumps to be used within it. forbidden_message: If given, all attempts to add instructions to this scope will raise a :exc:`.CircuitError` with this message. )parent registers allow_jumpsforbidden_messageN)rxrr*r)rrrrrrs r` _push_scopeQuantumCircuit._push_scopes;( !!(( #**,#'"3   rc6URR5$)zFinish a scope used in the control-flow builder interface, and return it to the caller. This should only be done by the control-flow context managers, since they naturally synchronize the creation and deletion of stack elements.)rxpoprs r` _pop_scopeQuantumCircuit._pop_scopes ((,,..rcUR(aURSR5$UR(d [S5eURS$)aReturn the instruction 3-tuple of the most recent instruction in the current scope, even if that scope is currently under construction. This function is only intended for use by the control-flow ``if``-statement builders, which may need to modify a previous instruction.r&&This circuit contains no instructions.)rxpeekryrrs r`#_peek_previous_instruction_in_scope2QuantumCircuit._peek_previous_instruction_in_scopesH  $ $,,R0557 7zzGH Hzz"~rcUR(aURSR5$UR(d [S5eURR5nU$)a=Return the instruction 3-tuple of the most recent instruction in the current scope, even if that scope is currently under construction, and remove it from that scope. This function is only intended for use by the control-flow ``if``-statement builders, which may need to replace a previous instruction with another. r&r)rxrryr)rrs r`"_pop_previous_instruction_in_scope1QuantumCircuit._pop_previous_instruction_in_scopesP  $ $,,R0446 6zzGH Hjjnn& r)rRrrrc [U[5(a9UnUbUc [S5eU[La/nUR [ XXdUS9UUSS9$USLa USLaSOUnOUSLa [ S5eUnUcUb [S5e[XXdUS9$) a Create a ``box`` of operations on this circuit that are treated atomically in the greater context. A "box" is a control-flow construct that is entered unconditionally. The contents of the box behave somewhat as if the start and end of the box were barriers (see :meth:`barrier`), except it is permissible to commute operations "all the way" through the box. The box is also an explicit scope for the purposes of variables, stretches and compiler passes. There are two forms for calling this function: * Pass a :class:`QuantumCircuit` positionally, and the ``qubits`` and ``clbits`` it acts on. In this form, a :class:`.BoxOp` is immediately created and appended using the circuit as the body. * Use in a ``with`` statement with no ``body``, ``qubits`` or ``clbits``. This is the "builder-interface form", where you then use other :class:`QuantumCircuit` methods within the Python ``with`` scope to add instructions to the ``box``. This is the preferred form, and much less error prone. Examples: Using the builder interface to add two boxes in sequence. The two boxes in this circuit can execute concurrently, and the second explicitly inserts a data-flow dependency on qubit 8 for the duration of the box, even though the qubit is idle. .. code-block:: python from qiskit.circuit import QuantumCircuit, Annotation class MyAnnotation(Annotation): namespace = "my.namespace" qc = QuantumCircuit(9) with qc.box(): qc.cz(0, 1) qc.cz(2, 3) with qc.box([MyAnnotation()]): qc.cz(4, 5) qc.cz(6, 7) qc.noop(8) Using the explicit construction of box. This creates the same circuit as above, and should give an indication why the previous form is preferred for interactive use. .. code-block:: python from qiskit.circuit import QuantumCircuit, BoxOp body_0 = QuantumCircuit(4) body_0.cz(0, 1) body_0.cz(2, 3) # Note that the qubit indices inside a body related only to the body. The # association with qubits in the containing circuit is made by the ``qubits`` # argument to `QuantumCircuit.box`. body_1 = QuantumCircuit(5) body_1.cz(0, 1) body_1.cz(2, 3) qc = QuantumCircuit(9) qc.box(body_0, [0, 1, 2, 3], []) qc.box(body_1, [4, 5, 6, 7, 8], []) Args: body_or_annotations: the first positional argument is unnamed. If a :class:`QuantumCircuit` is passed positionally, it is immediately used as the body of the box, and ``qubits`` and ``clbits`` must also be specified. If not given, or if given an iterable of :class:`.Annotation` objects, the context-manager form of this method is triggered. qubits: the qubits to apply the :class:`.BoxOp` to, in the explicit form. clbits: the qubits to apply the :class:`.BoxOp` to, in the explicit form. label: an optional string label for the instruction. duration: an optional explicit duration for the :class:`.BoxOp`. Scheduling passes are constrained to schedule the contained scope to match a given duration, including delay insertion if required. unit: the unit of the ``duration``. annotations: any :class:`.Annotation` objects the box should have. When this method is used in context-manager form, this argument can instead be passed as the only positional argument. z>When using 'box' with a body, you must pass qubits and clbits.)rrrRrFr.rQzCQuantumCircuit.box() got multiple values for argument 'annotations'zHWhen using 'box' as a context manager, you cannot pass qubits or clbits.)r[rNrr`rr-rlr.) rbody_or_annotationsrrrRrrrbodys r`r>QuantumCircuit.boxsx )> : :&D~"#cddh& ;;dDS^_   # % +s 2" K  #ab b-K  !3Z $WbccrcgrZrQrr}rrrrRs r` while_loopQuantumCircuit.while_loopDsrcgrZrQrs r`rrOrc>UR5n[U[R5(a [ Xa5nOUR US5US4nUcUcUb [ S5e[XUS9$UbUc [ S5eUR[XU5X4SS9$)aCreate a ``while`` loop on this circuit. There are two forms for calling this function. If called with all its arguments (with the possible exception of ``label``), it will create a :obj:`~qiskit.circuit.controlflow.WhileLoopOp` with the given ``body``. If ``body`` (and ``qubits`` and ``clbits``) are *not* passed, then this acts as a context manager, which will automatically build a :obj:`~qiskit.circuit.controlflow.WhileLoopOp` when the scope finishes. In this form, you do not need to keep track of the qubits or clbits you are using, because the scope will handle it for you. Example usage:: from qiskit.circuit import QuantumCircuit, Clbit, Qubit bits = [Qubit(), Qubit(), Clbit()] qc = QuantumCircuit(bits) with qc.while_loop((bits[2], 0)): qc.h(0) qc.cx(0, 1) qc.measure(0, 0) Args: condition (Tuple[Union[ClassicalRegister, Clbit], int]): An equality condition to be checked prior to executing ``body``. The left-hand side of the condition must be a :obj:`~ClassicalRegister` or a :obj:`~Clbit`, and the right-hand side must be an integer or boolean. body (Optional[QuantumCircuit]): The loop body to be repeatedly executed. Omit this to use the context-manager mode. qubits (Optional[Sequence[Qubit]]): The circuit qubits over which the loop body should be run. Omit this to use the context-manager mode. clbits (Optional[Sequence[Clbit]]): The circuit clbits over which the loop body should be run. Omit this to use the context-manager mode. label (Optional[str]): The string label of the instruction in the circuit. Returns: InstructionSet or WhileLoopContext: If used in context-manager mode, then this should be used as a ``with`` resource, which will infer the block content and operands on exit. If the full form is used, then this returns a handle to the instructions created. Raises: CircuitError: if an incorrect calling convention is used. rrzOWhen using 'while_loop' as a context manager, you cannot pass qubits or clbits.r-zEWhen using 'while_loop' with a body, you must pass qubits and clbits.Fr) rr[r9rDrEr1rr8rr7)rr}rrrrRr7s r`rrZsV++- i + +&}@I&AA)A,OQZ[\Q]^I <!V%7"9$D5A A ^v~W {{;y>UZ{[[rcgrZrQrindexsetloop_parameterrrrrRs r`for_loopQuantumCircuit.for_looprcgrZrQrs r`rrr rcUcUcUb [S5e[XX&S9$UbUc [S5eUR[XX65XESS9$)a Create a ``for`` loop on this circuit. There are two forms for calling this function. If called with all its arguments (with the possible exception of ``label``), it will create a :class:`~qiskit.circuit.ForLoopOp` with the given ``body``. If ``body`` (and ``qubits`` and ``clbits``) are *not* passed, then this acts as a context manager, which, when entered, provides a loop variable (unless one is given, in which case it will be reused) and will automatically build a :class:`~qiskit.circuit.ForLoopOp` when the scope finishes. In this form, you do not need to keep track of the qubits or clbits you are using, because the scope will handle it for you. For example:: from qiskit import QuantumCircuit qc = QuantumCircuit(2, 1) with qc.for_loop(range(5)) as i: qc.h(0) qc.cx(0, 1) qc.measure(0, 0) with qc.if_test((0, True)): qc.break_loop() Args: indexset (Iterable[int]): A collection of integers to loop over. Always necessary. loop_parameter (Optional[Parameter]): The parameter used within ``body`` to which the values from ``indexset`` will be assigned. In the context-manager form, if this argument is not supplied, then a loop parameter will be allocated for you and returned as the value of the ``with`` statement. This will only be bound into the circuit if it is used within the body. If this argument is ``None`` in the manual form of this method, ``body`` will be repeated once for each of the items in ``indexset`` but their values will be ignored. body (Optional[QuantumCircuit]): The loop body to be repeatedly executed. Omit this to use the context-manager mode. qubits (Optional[Sequence[QubitSpecifier]]): The circuit qubits over which the loop body should be run. Omit this to use the context-manager mode. clbits (Optional[Sequence[ClbitSpecifier]]): The circuit clbits over which the loop body should be run. Omit this to use the context-manager mode. label (Optional[str]): The string label of the instruction in the circuit. Returns: InstructionSet or ForLoopContext: depending on the call signature, either a context manager for creating the for loop (it will automatically be added to the circuit at the end of the block), or an :obj:`~InstructionSet` handle to the appended loop operation. Raises: CircuitError: if an incorrect calling convention is used. zMWhen using 'for_loop' as a context manager, you cannot pass qubits or clbits.r-zCWhen using 'for_loop' with a body, you must pass qubits and clbits.Fr)rr2rr1rs r`rrstj <!V%7"c"$.N N ^v~U {{ h V^ab b{{<UCVZ_{``rc*UR(a?[5nUR5nURXRUR SS9$UR[ URUR5URUR SS9$)apApply :class:`~qiskit.circuit.BreakLoopOp`. .. warning:: If you are using the context-manager "builder" forms of :meth:`.if_test`, :meth:`.for_loop` or :meth:`.while_loop`, you can only call this method if you are within a loop context, because otherwise the "resource width" of the operation cannot be determined. This would quickly lead to invalid circuits, and so if you are trying to construct a reusable loop body (without the context managers), you must also use the non-context-manager form of :meth:`.if_test` and :meth:`.if_else`. Take care that the :obj:`.BreakLoopOp` instruction must span all the resources of its containing loop, not just the immediate scope. Returns: A handle to the instruction created. Raises: CircuitError: if this method was called within a builder context, but not contained within a loop. Fr) rxr,placeholder_resourcesrrrr+rrrr resourcess r` break_loopQuantumCircuit.break_loops|*  $ $,.I!779I;;y*:*:IURH-n[UR[5(aM$[ S5e gUVs/sH)n[U[ 5(aURUOUPM+ nnUVs0sHo3S_M nnUVs0sHo3S_M nnURHnUHdnX2R;dM[UR[5(a-XS(d"XC==URR- ss'M^M`SXS'Mf [U5[UR5Vs/sH of(dM UPM sn5:XdM[SUR555s $ gs snfs snfs snfs snf)aReturn the start time of the first instruction, excluding delays, over the supplied qubits. Its time unit is ``self.unit``. Return 0 if there are no instructions over qubits Args: *qubits: Qubits within ``self`` to include. Integers are allowed for qubits, indicating indices of ``self.qubits``. Returns: Return the start time of the first instruction, excluding delays, over the qubits Raises: CircuitError: if ``self`` is a not-yet scheduled circuit. z.\s>oU5o) rryr[rrCrrerrrrmin)rrrrstartsdonesdones r`rAQuantumCircuit.qubit_start_time6sW >> !#zz !+"7"7??&V * GMNv!Jq#$6$6$++a.A=vN &'1Q$'#)*6aE6*::K***!+"7"7??$x"I)>)>)G)GGI ($( 6{cELLN"KNDd4N"KLL>fmmo>>>&O'*#Ls0F F  F F F cURc>URH-n[UR[5(aM$[ S5e gUVs/sH)n[U[ 5(aURUOUPM+ nnUVs0sHo3UR_M nnUVs0sHo3S_M nn[UR5HnUHdnX2R;dM[UR[5(a-XS(d"XC==URR-ss'M^M`SXS'Mf [U5[UR5Vs/sH of(dM UPM sn5:XdM[SUR555s $ [U5S:a[UR55$gs snfs snfs snfs snf)aReturn the stop time of the last instruction, excluding delays, over the supplied qubits. Its time unit is ``self.unit``. Return 0 if there are no instructions over qubits Args: *qubits: Qubits within ``self`` to include. Integers are allowed for qubits, indicating indices of ``self.qubits``. Returns: Return the stop time of the last instruction, excluding delays, over the qubits Raises: CircuitError: if ``self`` is a not-yet scheduled circuit. z;qubit_stop_time undefined. Circuit must be scheduled first.rFTc3$# UHov M g7frZrQ)r^stops r`ra1QuantumCircuit.qubit_stop_time..s;ND4NrH) rryr[rrCrrerrrrrr )rrrrstopsrKrLs r`r@QuantumCircuit.qubit_stop_time`s} >> !#zz !+"7"7??&U * GMNv!Jq#$6$6$++a.A=vN,23FqDNN"F3#)*6aE6*#DJJ/K***!+"7"7??$x!H (=(=(F(FFH ($( 6{cELLN"KNDd4N"KLL;ELLN;;;0 u:>u||~& &%O3*#Ls0GG" G  G !G c SSKJn [U"U5U5nUS:XaU$US:XaSSKJn U"XAR 5$SSSS S S S S S SSS. nX&;a[ SUS35eXFU- $)uEstimate the duration of a scheduled circuit This method computes the estimate of the circuit duration by finding the longest duration path in the circuit based on the durations provided by a given target. This method only works for simple circuits that have no control flow or other classical feed-forward operations. Args: target (Target): The :class:`.Target` instance that contains durations for the instructions if the target is missing duration data for any of the instructions in the circuit an :class:`.QiskitError` will be raised. This should be the same target object used as the target for transpilation. unit: The unit to return the duration in. This defaults to "s" for seconds but this can be a supported SI prefix for seconds returns. For example setting this to "n" will return in unit of nanoseconds. Supported values of this type are "f", "p", "n", "u", "µ", "m", "k", "M", "G", "T", and "P". Additionally, a value of "dt" is also accepted to output an integer in units of "dt". For this to function "dt" must be specified in the ``target``. Returns: The estimated duration for the execution of a single shot of the circuit in the specified unit. Raises: QiskitError: If the circuit is not scheduled or contains other details that prevent computing an estimated duration from (such as parameterized delay). rrrXrh)duration_in_dtgV瞯gư>gMbP?g@@g.AgeAgmBg4&k C) frnrµmrMGrKPzSpecified unit: z1 is not a valid/supported SI prefix, 's', or 'dt')rrrqiskit.circuit.durationrUrhr)rrrrdurrU prefix_dicts r`estimate_duration QuantumCircuit.estimate_durations< 5()=vF 3;J 4< >!#yy1 1    ""4&(YZ &&&r) rzrprvrxryrr|rrwrrSrTrR)rRegister | int | Sequence[Bit]rR str | NonerSr<rT dict | NonerUzIterable[expr.Var]rVz!Iterable[expr.Var | expr.Stretch]rWzCMapping[expr.Var, expr.Expr] | Iterable[Tuple[expr.Var, expr.Expr]])rzint | float | None)FN)rrrrrRrcr typing.Self)rzIterable[CircuitInstruction | tuple[qiskit.circuit.Instruction] | tuple[qiskit.circuit.Instruction, Iterable[Qubit]] | tuple[qiskit.circuit.Instruction, Iterable[Qubit], Iterable[Clbit]]]rIterable[Qubit]rIterable[Clbit]rRrcrSr<rTrdr'QuantumCircuit')rzOptional[TranspileLayout])rrA)rr )rz list[int])rr)rTr)rrs)rrrZ)rre)rNone)rr%rr)r int | Nonerrrr)rrh)F)r3rrrh)r=rer7rrrh)FF)rHfloatrIrr3rrrh)rNNF) rQrerRrcrSstr | int | Noner3rrrh)NNFFF)rz$Union['QuantumCircuit', Instruction]r0QubitSpecifier | Sequence[QubitSpecifier] | Nonerz0ClbitSpecifier | Sequence[ClbitSpecifier] | NonerrrrrrrrrXzLMapping[str | expr.Var | expr.Stretch, str | expr.Var | expr.Stretch] | NonerYrrOptional['QuantumCircuit'])rrhrrrrn)rzdict[Clbit, BitLocations])rzdict[Qubit, BitLocations])r list[Qubit])r list[Clbit])rlist[QuantumRegister])rrq)rlist[ClassicalRegister])rrr)rzlist[AncillaQubit])rztyping.Iterable[expr.Var])rztyping.Iterable[expr.Stretch])rz5typing.Iterable[typing.Union[expr.Var, expr.Stretch]])rrhrrh)rrhrrh)rrerrB)rrrlist[CircuitInstruction])rrJr zCallable[..., T]rz Union[S, T])r$QubitSpecifierrro)r(ClbitSpecifierrrp)rQrQN) rrrSequence[QubitSpecifier]r6zSequence[ParameterValueType]rRrcrr?r) rzOperation | CircuitInstructionrSequence[QubitSpecifier] | NonerSequence[ClbitSpecifier] | Nonerrrr?)rrBr/rrrB)rr@rSequence[Qubit]rzSequence[Clbit]rr@)rQrQr/r)rRrsrYrKrzUnion[Parameter, T]).)rRrsrY type(...)rr)rRrsrY typing.Anyrr)rdzstr | Parameterrr)rRrsrYrKrzUnion[expr.Var, T])rRrsrYr{rexpr.Var)rRrsrYr|)rnstr | expr.Varrr)rRrsrYrKrzUnion[expr.Stretch, T])rRrsrYr{r expr.Stretch)rwstr | expr.Stretchrr)rRrsrYrKrz!Union[expr.Var | expr.Stretch, T])rRrsrYr{rr)rzstr | expr.Var | expr.Stretchrr)rnr~r ztypes.Type | Nonerr})rwrrr)rr|rnr~rr})rr})rr)rnrsr z types.Typerr})rnr}r rirr})rrbrri)r'z Iterable[Bit]rri)rrrr)rryrri)r*dict[Parameter, ParameterValueType] | NonerRrcrr)rrrRrcrrr)rzBstr | Type[Instruction] | Sequence[str | Type[Instruction]] | Noner=rerre)NNNNFTNNmediumNTNNFNNN)$rrcrz float | Nonerrcrzdict | str | Nonerrrrr. bool | Nonerrcrrcrzbool | str | Nonerrrrjrz Any | Nonerrrrrzlist[int] | Nonerrerr)rzCallable[..., int]rre)rz$Callable[[CircuitInstruction], bool]rre)rz'OrderedDict[Instruction, int]')rRrsrrs)r(rrre)rRrcrre)rRrcrnz$Literal['alike', 'captures', 'drop']rre)rFrerRrsrr$)rFrerRrsrr)rrtrr?)rr|rr|rr?)rrtr[rurr?)T)rrrrn)TT)rrrrrrn)rrsrrh)rrsrrh)rr<)rr<)rr=)rzset[Parameter]) rGKUnion[Mapping[Parameter, ParameterValueType], Iterable[ParameterValueType]]rzLiteral[False]rrryrrrh) rGrrz Literal[True]rrryrrri) rGrrrrrryrrrn)r&Mapping[Parameter, ParameterValueType]ryrrr)rrtrr?)rz$Union[ParameterValueType, expr.Expr]r8zQubitSpecifier | Nonerrcrr?) rrtrrtrRrcrSrlrr?)rr<rrvrr?)rr<rrtrr?) rr<rrtrrtrRrcrSrlrr?) rr<rrvrrtrSrlrr?)rr<rrvrrtrr)NNF) rr<rrvrrtrrmrrcrr)rr<rrvrrtrr)rr<r r<rrtrr?) rr<rr<rr<rrtrr?)rrtrrtrrtrr?) rrtrrtrrtrrtrr?)rr<rrtrRrcrr?)rr<r1rtr2rtrr?)r r<rrtrr?)r1rtr2rtrr?) rrtrvrtrwrtrRrcrSrlrr?) rr<r r<rr<rrtrr?)rr<r r<rr<rr<rrtrrtrRrcrSrlrr?)rrtrRrcrr?) rrtrrtrrtrSrlrr?)NNN) rrvrrtrrmrrcrSrlrr?) rrtrrtrrtrRrcrSrlrr?)rrsrrvrr?) r+Statevector | Sequence[complex] | str | intrrwrRrcrrrr?)NF)r6rrrwrr)r z np.ndarray | Gate | BaseOperatorrrvrRrc)rrt)rr))rQrQrQTN) rrfrrgrzIterable[Register]rrr Optional[str])rr*)rrB).NN)rrwrrxrz,QuantumCircuit | typing.Iterable[Annotation]rRrcrrirz9Literal['dt', 's', 'ms', 'us', 'ns', 'ps', 'expr'] | Nonerztyping.Iterable[Annotation]) r}1tuple[ClassicalRegister | Clbit, int] | expr.ExprrrirrirrirRrcrr8) r}rrrhrrvrSequence[ClbitSpecifier]rRrcrr?)r Iterable[int]rzParameter | NonerrirrirrirRrcrr2)rrrzUnion[Parameter, None]rrhrrvrrrRrcrr?)NNNN)r}%tuple[ClassicalRegister | Clbit, int]rr4) r}rr'rhrrvrrrRrcrr?)r}zFtuple[ClassicalRegister, int] | tuple[Clbit, int] | tuple[Clbit, bool]r'rhr,rhrrvrrrRrcrr?) r(Union[ClbitSpecifier, ClassicalRegister]r1rirrirrirRrrr6) rrr1z+Iterable[Tuple[typing.Any, QuantumCircuit]]rrvrrrRrrr?)rr?)rzUnion[Qubit, int]rrk)rX)rrsrz int | float)rn __module__ __qualname____firstlineno____doc__rrrpropertyrrsetterr classmethodr staticmethodrrrrrTrrrrtrrqrrrrr!r.r4rArHrPrrrrrrrrrrrrrrrrrrrrrrrrrrr rrrtypingrrr!rrr;rrrZrerhrorrrxr{rrrrrrr~r}r{rr)r3r:r9rrrrrrrrrr!r%r3r6r9rrrrIrOrSrrZr_rbrprrrSrGrFrrrrr<rrrrrrrrrrrr rrr r%r+r3rr<r@rDrHrLrPrUrXr\rcrhrlrprxr|rrrrrrrrrrrrrrrrrrrrrrrrrr r r>rrr$r-r2r:r=rBrAr@r`__static_attributes__rQrr`rNrNs0XtI F  +, $%'68\^u -u u ) u  u # u 4u Zu n'4ESWXY __'4ESWXY [[PT/3CM #%"$+, $2 2 2 22)22 22h33j((4 [[CC:V$V$p@__"" -  2 K"LUYLL\&PBH22h   \\!!   \\!! UU II 22)),,11,,11    .3+ d.3!    __?? __GG  J J +-/1  (-     82615 i  i3i/i/ i  i iX __!-!BF! !!  __   DCQVDCDCL __NN __RR--^ 2 __GG __KK++ZC, __OO __SS&&PO& __]] __.1,,"+, &,, BN:)2C <" D\|5B __-- __55&JP __PP __VVGK)2C :?:BB=~( EI HAHH  H:EI AAAA  A<  !: O!:  !:  !:J""##'!"$("+3(, #"&'+&*+p p p  p ! p  p p "p p )p &p p p !p "#p $ %p &%'p ()p *$+p h/ 5+5 5(A M3=M3 M3^"%%""6%%4%/ O==~@ *$ <;B <<8 <  <| . =F>ZCx@6:++.2+ #+ZUUn  0  ,&'&'P , ,A4A4F++ 0#&  _      "%  _     v+ ! v+_v+v+  v+  v+ $v+p0 W[EOS /*59<'+ O6O$O O  O: G"!'+ # %# %#  # % #  # J GK" Q&!'+ % !% &% % %  % % %  % X(,   1 %  %    J!& <O!<O-<O! <O  <OFHL %bW!bW-bW! bW E bW  bWbWR!& +O +O-+O! +O  +OZQ'Q.@QIWQ Q"H H H  H  H  H6 & ' %    , & ' '  %    6UYZ'Z0>ZGQZ Z,!'+ % !% &% % %  % % %  % NW'W1?WIWW W$UYZ'Z0>ZGQZ Z,!'+ % !% &% % %  % % %  % NW'W1?WIWW W" K&!'+ % !% &% % %  % % %  % NW'W1?WIWW W"W'W1?WIWW W" R G I"!'+ # %# %#  # % #  # R!'+ # %# %#  # % #  # J " T$!'+ ( %( &( & (  ( % (  ( T H J"!'+ # %# %#  # % #  # J G IV!V V V  V  V<!'+. !.  .  . " . & . %. . %.  . ` T T$!'+ & %& %&  & % &  & P R&(, % &% '% % % % %  % N  4 LP'+ b]0b]%b]I b]  b] % b] b]b]H G"!'+ & %& %&  & % &  & P G"!'+ # %# %#  # % #  # T!'+ ( &( '( % (  ( % (  ( TLL)L  L*37  w :w 0w  w  w  w x37 sZ;sZ0sZ sZr! +9 -+9)+9 +9Z"'H!#%"$(* +/     &    )  >/   MP2626 td!JN36td0 td 0 tdItdtdtdHtd1tdl __D     __D)  )  =\RV=\~ __  )           __  /   )  )     MQB [_B H __YY __!8$)  )   VdVd~!7 Y7 $7 % 7 ) 7 ) 7 7  7 r __8     __8;)  )  CaDCaJ : < N(T+Z9'9'rrNc~\rSrSrSrSSjr\S5rSS.SSjjrSSjr S r S r S r S r S rSrSrSrSrg)ruirPcXlgrZr)rrPs r`r$_OuterCircuitScopeInterface.__init__s rc.URR$rZ)rPryrs r`r(_OuterCircuitScopeInterface.instructionss||!!!rFr.c4URRXS9$)Nr.)rPrrOs r`r"_OuterCircuitScopeInterface.appends||##K#OOrcURRRU5 SURlSURlg)Nrh)rPryrrr)rrs r`r"_OuterCircuitScopeInterface.extends2 !!$' $   rc[U[5(a*XRR;a[ SUS35eU$[U[ 5(a*XRR ;a[ SUS35eU$[U[5(a$URRRU$[ SUS35e![a [ SUS35Sef=f)NzClbit z is not present in this circuit.z Register zClassical bit index z is out-of-range.z'Unknown classical resource specifier: 'z'.) r[r#rPrrr$rreryr IndexError)r specifiers r`r16_OuterCircuitScopeInterface.resolve_classical_resources i ' ' ; ;;"VI;6V#WXX  i!2 3 3  2 22"Yyk9Y#Z[[  i % % b||))00;;DYKrRSS b"%9)DU#VW]aa bs "CC"cURRUS5nURRRU5 grZ)rPrryadd_declared_varrs r`r1_OuterCircuitScopeInterface.add_uninitialized_vars0ll++C6 ++C0rcURRU5nURRRU5 grZ)rPrryadd_declared_stretchrs r`r'_OuterCircuitScopeInterface.add_stretchs.,,33G< //8rcLURRRU5$rZ)rPryrhrrRs r`rh#_OuterCircuitScopeInterface.get_vars||!!))$//rcLURRRU5$rZ)rPryrrrs r`rr'_OuterCircuitScopeInterface.get_stretchs||!!--d33rc`URUR5U:wa[SUS35egNr\z ' is not present in this circuit)rhrRrrs r`r#_OuterCircuitScopeInterface.use_vars1 << !S (3%'GHI I )rc`URUR5U:wa[SUS35egr)rrrRrrs r`r'_OuterCircuitScopeInterface.use_stretchs3   GLL )W 47)+KLM M 5rcgrZrQrs r`r%_OuterCircuitScopeInterface.use_qubit s rN)rPrNrz)rr)rnrrr __slots__rrrrrr1rrrhrrrrrrrQrr`rurus^I""=BP! T.1904JN rruc4[[R"U55Htn[U[R5(aUR U5 M5UR (aURU5 MYURUR5 Mv U$rZ) rr9iter_identifiersr[r_rrrr1r)r7ridents r`rErEsm T**401 eT\\ * *  % %e ,%%e,88C2 Krc[U5UlURR5Ul[R "UR 5UlgrZ)rurvrzrrrr)originalr<s r`r@r@"s;237C&&++-CMNN8#5#56CMr)r7r)r expr.Exprrr)~r __future__rrcollections.abcrrrrrrrrrrrr r r r r rrrmathrnumpyrDqiskit._accelerate.circuitrrr#qiskit._accelerate.circuit_durationrqiskit.exceptionsrqiskit.circuit.instructionrqiskit.circuit.gaterqiskit.circuit.parameterrqiskit.circuit.exceptionsr qiskit.utilsrrrrrr r!r"r#r$r%r& controlflowr'r(controlflow.builderr)r*controlflow.break_loopr+r,controlflow.boxr-r.controlflow.continue_loopr/r0controlflow.for_loopr1r2controlflow.if_elser3r4controlflow.switch_caser5r6controlflow.while_loopr7r8 classicalr9r:parameterexpressionr;r<parametertabler=parametervectorr>instructionsetr?rr@quantumcircuitdatarArBrrCrrD TYPE_CHECKINGrzqiskit.circuitrEqiskit.transpiler.layoutrG+qiskit.quantum_info.operators.base_operatorrH&qiskit.quantum_info.states.statevectorrIrJrKrerrtrurLrNrurEr@rQrr`rsj" #    233J)2$.26   &6OE.N;4@A"H),* F )8HB CL CL   U5#:  !   U5#:  ! )UE *Eu'Eu'PjE "7E P"7r