Prepare 0.17.0 release

qiskit/circuit/library/__init__.py

@@ -55,6 +55,7 @@
    RCCXGate
    RC3XGate
    Reset
+   RGate
    RXGate
    RXXGate
    RYGate
@@ -135,6 +136,7 @@
    PolynomialPauliRotations
    PiecewiseLinearPauliRotations
    PiecewisePolynomialPauliRotations
+   PiecewiseChebyshev
 
 Adders
 ++++++
@@ -273,6 +275,44 @@
    templates.nct.template_nct_9d_9
    templates.nct.template_nct_9d_10
 
+Clifford template circuits
+==========================
+
+.. autosummary::
+   :toctree: ../stubs/
+
+   clifford_2_1
+   clifford_2_2
+   clifford_2_3
+   clifford_2_4
+   clifford_3_1
+   clifford_4_1
+   clifford_4_2
+   clifford_4_3
+   clifford_4_4
+   clifford_5_1
+   clifford_6_1
+   clifford_6_2
+   clifford_6_3
+   clifford_6_4
+   clifford_6_5
+   clifford_8_1
+   clifford_8_2
+   clifford_8_3
+
+RZXGate template circuits
+=========================
+
+.. autosummary::
+   :toctree: ../stubs/
+
+   rzx_yz
+   rzx_xz
+   rzx_cy
+   rzx_zz1
+   rzx_zz2
+   rzx_zz3
+
 """
 
 from .standard_gates import *
@@ -311,6 +351,7 @@
     WeightedAdder,
     QuadraticForm,
     LinearAmplitudeFunction,
+    PiecewiseChebyshev,
 )
 from .n_local import (
     NLocal,

qiskit/circuit/library/arithmetic/__init__.py

@@ -21,3 +21,4 @@
 from .weighted_adder import WeightedAdder
 from .quadratic_form import QuadraticForm
 from .linear_amplitude_function import LinearAmplitudeFunction
+from .piecewise_chebyshev import PiecewiseChebyshev

qiskit/circuit/library/arithmetic/piecewise_chebyshev.py

@@ -45,7 +45,7 @@ class PiecewiseChebyshev(BlueprintCircuit):
             qc = QuantumCircuit(pw_approximation.num_qubits)
             qc.h(list(range(num_state_qubits)))
             qc.append(pw_approximation.to_instruction(), qc.qubits)
-            print(qc.draw(output='mpl'))
+            qc.draw(output='mpl')
 
     References:
 

qiskit/circuit/library/templates/__init__.py

@@ -75,9 +75,12 @@
 from .clifford.clifford_2_1 import clifford_2_1
 from .clifford.clifford_2_2 import clifford_2_2
 from .clifford.clifford_2_3 import clifford_2_3
+from .clifford.clifford_2_4 import clifford_2_4
 from .clifford.clifford_3_1 import clifford_3_1
 from .clifford.clifford_4_1 import clifford_4_1
 from .clifford.clifford_4_2 import clifford_4_2
+from .clifford.clifford_4_3 import clifford_4_3
+from .clifford.clifford_4_4 import clifford_4_4
 from .clifford.clifford_5_1 import clifford_5_1
 from .clifford.clifford_6_1 import clifford_6_1
 from .clifford.clifford_6_2 import clifford_6_2
@@ -86,3 +89,4 @@
 from .clifford.clifford_6_5 import clifford_6_5
 from .clifford.clifford_8_1 import clifford_8_1
 from .clifford.clifford_8_2 import clifford_8_2
+from .clifford.clifford_8_3 import clifford_8_3

qiskit/quantum_info/__init__.py

@@ -103,6 +103,7 @@
 .. autosummary::
    :toctree: ../stubs/
 
+   hellinger_distance
    hellinger_fidelity
 
 Synthesis
@@ -115,6 +116,7 @@
    TwoQubitBasisDecomposer
    two_qubit_cnot_decompose
    Quaternion
+   decompose_clifford
 """
 
 from .operators import (Operator, ScalarOp, Pauli, Clifford, SparsePauliOp)
@@ -139,6 +141,7 @@
                      random_cnotdihedral)
 
 from .synthesis import (OneQubitEulerDecomposer, TwoQubitBasisDecomposer,
-                        two_qubit_cnot_decompose, Quaternion)
+                        two_qubit_cnot_decompose, Quaternion,
+                        decompose_clifford)
 
-from .analysis import hellinger_fidelity
+from .analysis import hellinger_distance, hellinger_fidelity

qiskit/quantum_info/analysis/__init__.py

@@ -12,4 +12,4 @@
 
 """Module for functions for post processing results."""
 from .average import average_data
-from.distance import hellinger_fidelity
+from .distance import hellinger_fidelity, hellinger_distance

qiskit/quantum_info/synthesis/__init__.py

@@ -15,3 +15,4 @@
 from .two_qubit_decompose import TwoQubitBasisDecomposer, two_qubit_cnot_decompose
 from .one_qubit_decompose import OneQubitEulerDecomposer
 from .quaternion import Quaternion
+from .clifford_decompose import decompose_clifford

qiskit/transpiler/__init__.py

@@ -395,6 +395,15 @@
    FencedDAGCircuit
    FencedPropertySet
 
+Abstract Passes
+---------------
+
+.. autosummary::
+   :toctree: ../stubs/
+
+   TransformationPass
+   AnalysisPass
+
 Exceptions
 ----------
 

qiskit/transpiler/passes/__init__.py

@@ -83,6 +83,7 @@
 
    ALAPSchedule
    ASAPSchedule
+   RZXCalibrationBuilder
 
 Circuit Analysis
 ================
@@ -180,6 +181,7 @@
 from .scheduling import ALAPSchedule
 from .scheduling import ASAPSchedule
 from .scheduling import TimeUnitAnalysis
+from .scheduling import RZXCalibrationBuilder
 
 # additional utility passes
 from .utils import CheckMap

qiskit/transpiler/passes/scheduling/calibration_creators.py

@@ -110,7 +110,8 @@ def rescale_cr_inst(instruction: Play, theta: float, sample_mult: int = 16) -> P
             sample_mult: All pulses must be a multiple of sample_mult.
 
         Returns:
-            Play: The play instruction with the stretched compressed GaussianSquare pulse.
+            qiskit.pulse.Play: The play instruction with the stretched compressed
+                GaussianSquare pulse.
 
         Raises:
             QiskitError: if the pulses are not GaussianSquare.

releasenotes/notes/ParameterVectors-aren't-unrolled-by-execute-c8bd393818e926b0.yaml → releasenotes/notes/0.17/ParameterVectors-aren't-unrolled-by-execute-c8bd393818e926b0.yaml

@@ -3,7 +3,7 @@ fixes:
   - |
     Fixed issue where circuit.execute would raise exception when 
     ParameterVectors were passed in the parameter_bind parameter.
-    Refer to `#5467 <https://github.com/Qiskit/qiskit-terra/issues/5467>` for more
+    Refer to `#5467 <https://github.com/Qiskit/qiskit-terra/issues/5467>`__ for more
     details. 
     It is now possible to call:
-    execute(circuit, backend, parameter_binds=[{pv1: [...], pv2: [...]}])
+    execute(circuit, backend, parameter_binds=[{pv1: [...], pv2: [...]}])

releasenotes/notes/add-call-instruction-6f4fc37994090c2f.yaml → releasenotes/notes/0.17/add-call-instruction-6f4fc37994090c2f.yaml

@@ -11,30 +11,6 @@ deprecations:
     Please use :py:func:`~qiskit.pulse.transforms.flatten` instead.
 
 features:
-  - |
-    Pulse :py:class:`~qiskit.pulse.instructions.Call` instruction is added.
-    This instruction represents calling a schedule as a subroutine from within another schedule.
-    This is not exposed to end users, but internally used for compiling purpose.
-
-    This instruction is implicitly used in the pulse builder call function.
-    This defines a reference to another program, and no further optimization is performed
-    between call instructions.
-
-    For example,
-
-    .. code-block:: python
-
-      qc_x = QuantumCircuit(1)
-      qc_x.x(0)
-
-      with pulse.build(backend) as sched:
-          pulse.call(qc_x)
-          pulse.call(qc_x)
-
-    Because two call instructions are viewed as references to the external program,
-    two ``qc_x`` are not merged though they are consecutive x gates which form an identity.
-
-upgrade:
   - |
     Pulse :py:func:`~qiskit.pulse.call` function can take parameter object with
     a parameterized subrotuine. We can assign different parameters for each subroutine call.

releasenotes/notes/0.17/add-config-processor-type-field-916f98f2eebf7e72.yaml

@@ -0,0 +1,8 @@
+---
+features:
+  - |
+    The :class:`qiskit.providers.models.QasmBackendConfiguration` has a new
+    field ``processor_type`` which can optionally be used to provide
+    information about a backend's processor in the form:
+    ``{"family": <str>, "revision": <str>, segment: <str>}``. For example:
+    ``{"family": "Canary", "revision": "1.0", segment: "A"}``.

releasenotes/notes/0.17/add-parameters-and-is_parameterized-to-pulse-d5695dd14e407537.yaml

@@ -0,0 +1,25 @@
+---
+features:
+  - |
+    The :py:class:`qiskit.pulse.Schedule`,
+    :py:class:`qiskit.pulse.Instruction`, and :py:class:`qiskit.pulse.Channel`
+    classes now have a :attr:`~qiiskit.pulse.Schedule.parameter` property
+    which will return any :class:`~qiskit.circuit.Parameter` objects used
+    in the object and a :meth:`~qiskit.pulse.Schedule.is_parameterized()`
+    method which will return ``True`` if any parameters are used in the
+    object.
+
+    For example:
+
+    .. jupyter-execute::
+
+        from qiskit.circuit import Parameter
+        from qiskit import pulse
+
+        shift = Parameter('alpha')
+
+        schedule = pulse.Schedule()
+        schedule += pulse.SetFrequency(shift, pulse.DriveChannel(0))
+
+        assert schedule.is_parameterized() == True
+        print(schedule.parameters)

releasenotes/notes/0.17/add-piecewise-polynomial-chebyshev-66c82ffe1d749dd6.yaml

@@ -0,0 +1,25 @@
+---
+features:
+  - |
+    Added a :class:`~qiskit.circuit.library.PiecewiseChebyshev` to the
+    :mod:`qiskit.circuit.library` for implementing a piecewise Chebyshev
+    approximation of an input function. For a given function :math:`f(x)`
+    and degree :math:`d`, this class class implements
+    a piecewise polynomial Chebyshev approximation on :math:`n` qubits
+    to :math:`f(x)` on the given intervals. All the polynomials in the
+    approximation are of degree :math:`d`.
+
+    For example:
+
+    .. jupyter-execute::
+
+        import numpy as np
+        from qiskit import QuantumCircuit
+        from qiskit.circuit.library.arithmetic.piecewise_chebyshev import PiecewiseChebyshev
+        f_x, degree, breakpoints, num_state_qubits = lambda x: np.arcsin(1 / x), 2, [2, 4], 2
+        pw_approximation = PiecewiseChebyshev(f_x, degree, breakpoints, num_state_qubits)
+        pw_approximation._build()
+        qc = QuantumCircuit(pw_approximation.num_qubits)
+        qc.h(list(range(num_state_qubits)))
+        qc.append(pw_approximation.to_instruction(), qc.qubits)
+        qc.draw(output='mpl')

releasenotes/notes/add_array_to_latex-0b5f655a47f132c0.yaml → releasenotes/notes/0.17/add_array_to_latex-0b5f655a47f132c0.yaml

@@ -1,8 +1,9 @@
 ---
 features:
   - |
-    Can now use :func:`array_to_latex()` to represent vectors and matrices as
-    human-friendly LaTeX.
+    Added a new function :func:`~qiskit.visualization.array_to_latex` to
+    the :mod:`qiskit.visualization` module that can be used to represent
+    and visualize vectors and matrices with LaTeX.
 
     .. jupyter-execute::
 

releasenotes/notes/0.17/add_state_ipython-6fd6305f3db04a23.yaml

@@ -0,0 +1,29 @@
+---
+features:
+  - |
+    The :class:`~qiskit.quantum_info.Statevector` and
+    :class:`~qiskit.quantum_info.DensityMatrix` classes now have
+    :meth:`~qiskit.quantum_info.StateVector.draw` methods which allow objects
+    to be drawn as either text matrices, IPython Latex objects, Latex source,
+    Q-spheres, Bloch spheres and Hinton plots. By default the output type
+    is the equivalent output from ``__repr__`` but this default can be changed
+    in a user config file by setting the ``state_drawer`` option. For example:
+
+    .. jupyter-execute::
+
+            from qiskit.quantum_info import DensityMatrix
+            dm = DensityMatrix.from_label('r0')
+            dm.draw('latex')
+
+    .. jupyter-execute::
+
+            from qiskit.quantum_info import Statevector
+            sv = Statevector.from_label('+r')
+            sv.draw('qsphere')
+
+    Additionally, the :meth:`~qiskit.quantum_info.DensityMatrix.draw` method
+    is now used for the ipython display of these classes, so if you change the
+    default output type in a user config file then when a
+    :class:`~qiskit.quantum_info.Statevector` or a
+    :class:`~qiskit.quantum_info.DensityMatrix` object are displayed in
+    a jupyter notebook that output type will be used for the object.

releasenotes/notes/bit-classes-register-index-optional-9aa6feff4fce3524.yaml → releasenotes/notes/0.17/bit-classes-register-index-optional-9aa6feff4fce3524.yaml

@@ -4,4 +4,5 @@ features:
     The constructors of the :class:`~qiskit.circuit.Bit` class and subclasses,
     :class:`~qiskit.circuit.Qubit`, :class:`~qiskit.circuit.Clbit`, and
     :class:`~qiskit.circuit.AncillaQubit`, have been updated such that their
-    two parameters, ``register`` and ``index`` are now optional.
+    two parameters, ``register`` and ``index`` are now optional. This enables
+    the creation of bit objects that are independent of a register.

releasenotes/notes/calling_a_pass-4148f285ea717c74.yaml → releasenotes/notes/0.17/calling_a_pass-4148f285ea717c74.yaml

@@ -1,13 +1,15 @@
 ---
 features:
   - |
-    A new quick way to call a pass is being introduced for convenience. Now it is possible to direcly call a
-    :class:`~qiskit.transpiler.BasePass` instance with a :class:`~qiskit.circuit.quantumcircuit.QuantumCircuit`
-    instance as a parameter to run the pass on the given circuit.
+    All transpiler passes (ie any instances of
+    :class:`~qiskit.transpiler.BasePasss`) are now directly callable.
+    Calling a pass provides a convenient interface for running the pass
+    on a :class:`~qiskit.circuit.QuantumCircuit` object.
 
-    For example, in case a transformation pass such as :class:`~qiskit.transpiler.passes.BasisTranslator`:
+    For example, running a single transformation pass, such as
+    :class:`~qiskit.transpiler.passes.BasisTranslator`, can be done with:
 
-    .. code-block::
+    .. jupyter-execute::
 
       from qiskit import QuantumCircuit
       from qiskit.transpiler.passes import BasisTranslator
@@ -18,11 +20,14 @@ features:
 
       pass_instance = BasisTranslator(sel, ['rx', 'rz', 'cx'])
       result = pass_instance(circuit)
+      result.draw(output='mpl')
 
-    For the case of an analysis pass, a property set (as `dict` or as :class:`~qiskit.transpiler.propertyset.PropertySet`)
-    needs to be added as a parameter and it might be modified "in-place":
+    When running an analysis pass, a property set (as ``dict`` or as
+    :class:`~qiskit.transpiler.PropertySet`)
+    needs to be added as a parameter and it might be modified "in-place".
+    For example:
 
-    .. code-block::
+    .. jupyter-execute::
 
       from qiskit import QuantumCircuit
       from qiskit.transpiler.passes import Depth

releasenotes/notes/check-name-string-in-setter-openqasm-valid-0fe1d7c42e37b679.yaml → releasenotes/notes/0.17/check-name-string-in-setter-openqasm-valid-0fe1d7c42e37b679.yaml

@@ -4,7 +4,7 @@ fixes:
     The :meth:`~qiskit.circuit.Register.name` setter method of class
     :class:`~qiskit.circuit.Register` previously did not check the assigned
     string to be a valid register name as per the  
-    `OpenQASM specification <https://arxiv.org/pdf/1707.03429v2.pdf>`_. 
+    `OpenQASM specification <https://arxiv.org/pdf/1707.03429v2.pdf>`__. 
     This check is performed when the name is specified in the constructor.
     With this update, this check is also now performed in the setter method
 

releasenotes/notes/0.17/circuit-meas-level-one-147399217ce0b34b.yaml

@@ -0,0 +1,11 @@
+---
+features:
+  - |
+    The :class:`~qiskit.circuit.QasmQobjConfig` class now has an optional
+    kwarg for ``meas_level`` and ``meas_return``. These fields can be used
+    to enable generating :class:`~qiskit.circuit.QasmQobj` job payloads that
+    support ``meas_level=1`` (kerneled data) for circuit jobs (previously
+    this was only exposed for :class:`~qiskit.circuit.PulseQobj` objects).
+    The :func:`~qiskit.compiler.assemble` function has been updated
+    to set this field for :class:`~qiskit.circuit.QasmQobj` objects it
+    generates.