qiskit

Environment

• Qiskit Terra version: 0.19.x (and main)
• Python version: 3.10
• Operating system: linux

What is happening?

The options object from in the fake backends don't get passed down to the underlying simulator. For example, if you ca

How can we reproduce the issue?

from qiskit.circuit import QuantumCircuit
from qiskit import execute
from qiskit

Feature details

Due to the similarity, it is easy to confuse qml.X and qml.PauliX, especially since other methods of specifying circuits, e.g., QASM, use x for PauliX. But if a user uses qml.X in their circuit on a qubit device, nothing happens to inform them that the incorrect operation is being used:

@qml.qnode(dev)
def circ():
    qml.PauliX(wires=0)
    qml.Hada

The grammar was extended with some built-in math functions that were out of the specification. TSC decided that the functions included in Qiskit/openqasm#275 should be part of the specification.

Describe the Issue

1. In section 2.4.3 on Controlled Rotations, the line "A controlled R_x(θ) could similarly be made using CNOT gates." seems incorrect.
2. I assume that the line claims that replacing R_y(θ/2) by R_x(θ/2) (similarly for the -θ case), in the circuit above, we would get a controlled R_x(θ). This is incorrect.
3. Passing |1> through q_0, we get X R_x(-θ/2) X R_x(θ/2)q_1, fo

Currently mitiq.benchmarks contains RB and mirror circuits, and needs more benchmark circuits.

GHZ circuits provide natural scaling with the number of qubits, are structured (in contrast to random as with RB and mirror circuits), and have additional nice features for benchmarking error mitigation:

• GHZ circuits result in idle qubits for which it is natural to apply dynamical decoupling.

Whenever a slide has minted code, like so:

\begin{frame}[fragile]{Example minted}
	\begin{minted}{python}
		from qiskit_aqua import run_algorithm

		print(run_algorithm(params)['result'])
	\end{minted}
\end{frame}

One is unable to add the \pagenumber before \end{frame} as it gets left aligned instead of right aligned:
![image](https://user-images.githubusercontent.com/1

Currently, the RasQ-LED demo can only be started from touch screen desktop.
Thus, it cannot be used on a system without a touch display.
Add an option to start this demo in rasqberry-config.

If you search for int( you'll find casts throughout a lot of the codebase. This might be left-over from before _params_validation() was added. The task is to remove these redundant casts and add a few assertions/additional tests as needed.

Need more tutorials contributed by the community