Skip to main contentIBM Quantum Documentation
This page is from a dev version of Qiskit SDK. This is a new interface that does not exist in the stable version.

PiecewiseLinearPauliRotationsGate

class qiskit.circuit.library.PiecewiseLinearPauliRotationsGate(num_state_qubits=None, breakpoints=None, slopes=None, offsets=None, basis='Y', label=None)

GitHub

Bases: Gate

Piecewise-linearly-controlled Pauli rotations.

For a piecewise linear (not necessarily continuous) function f(x)f(x), which is defined through breakpoints, slopes and offsets as follows. Suppose the breakpoints (x0,...,xJ)(x_0, ..., x_J) are a subset of [0,2n1][0, 2^n-1], where nn is the number of state qubits. Further on, denote the corresponding slopes and offsets by aja_j and bjb_j respectively. Then f(x) is defined as:

f(x)={0,x<x0aj(xxj)+bj,xjx<xj+1f(x) = \begin{cases} 0, x < x_0 \\ a_j (x - x_j) + b_j, x_j \leq x < x_{j+1} \end{cases}

where we implicitly assume xJ+1=2nx_{J+1} = 2^n.

Construct piecewise-linearly-controlled Pauli rotations.

Parameters

  • num_state_qubits (int | None) – The number of qubits representing the state.
  • breakpoints (list[int] | None) – The breakpoints to define the piecewise-linear function. Defaults to [0].
  • slopes (Sequence[float] | None) – The slopes for different segments of the piecewise-linear function. Defaults to [1].
  • offsets (Sequence[float] | None) – The offsets for different segments of the piecewise-linear function. Defaults to [0].
  • basis (str) – The type of Pauli rotation ('X', 'Y', 'Z').
  • label (str | None) – The label of the gate.

Attributes

base_class

Get the base class of this instruction. This is guaranteed to be in the inheritance tree of self.

The “base class” of an instruction is the lowest class in its inheritance tree that the object should be considered entirely compatible with for _all_ circuit applications. This typically means that the subclass is defined purely to offer some sort of programmer convenience over the base class, and the base class is the “true” class for a behavioral perspective. In particular, you should not override base_class if you are defining a custom version of an instruction that will be implemented differently by hardware, such as an alternative measurement strategy, or a version of a parametrized gate with a particular set of parameters for the purposes of distinguishing it in a Target from the full parametrized gate.

This is often exactly equivalent to type(obj), except in the case of singleton instances of standard-library instructions. These singleton instances are special subclasses of their base class, and this property will return that base. For example:

>>> isinstance(XGate(), XGate)
True
>>> type(XGate()) is XGate
False
>>> XGate().base_class is XGate
True

In general, you should not rely on the precise class of an instruction; within a given circuit, it is expected that Instruction.name should be a more suitable discriminator in most situations.

decompositions

Get the decompositions of the instruction from the SessionEquivalenceLibrary.

definition

Return definition in terms of other basic gates.

label

Return instruction label

mutable

Is this instance is a mutable unique instance or not.

If this attribute is False the gate instance is a shared singleton and is not mutable.

name

Return the name.

num_clbits

Return the number of clbits.

num_qubits

Return the number of qubits.

params

The parameters of this Instruction. Ideally these will be gate angles.

Was this page helpful?
Report a bug or request content on GitHub.