quantum-computing

Several katas could have better error messaging:

• Superposition : the test harness could log the actual state of the system after prep vs the expected state before asserting that they are the same (the change would add state prep and logging using DumpMachine to AssertEqualOnZeroState)
• BasicGates : a similar improvement, but a bit more extra code to write a unified test wrapper

Here are some examples:

• Root README is missing machine learning category of samples
• README in algorithms is missing repeat-until-success and sudoku-grover
• [README in diagnostics](https://github.com/microsoft/Quantum/blob/main/samples/diagnostics/RE

Information

• Qiskit Terra version: main
• Python version: any
• Operating system: any

What is the current behavior?

Coveralls will often indicate spurious changes in coverage, due to randomness, or protective code not needing to

Description of the issue
Similar to cirq.SQRT_ISWAP_INV, define a global constant for cirq.ISWAP_INV and replace usages of cirq.ISWAP ** -1 with cirq.ISWAP_INV.

https://github.com/quantumlib/Cirq/blob/7951f84a0110be719c8a9e07aa1ffec2b0a31990/cirq-core/cirq/ops/swap_gates.py#L356

Cirq version
0.14.0

To get this codebase up to standard, we need to add type hints. At the very least, perhaps we should start insisting that all new code has type hints added, but moreover we need to add typing to the code that currently exists.

This is a pretty large project, but luckily it can be done incrementally - I believe at this point it's a stretch goal for v1, if anyone wants to help it would be much ap

Is your feature request related to a problem? Please describe.
I would like to check the behavior of the parameter index in the function QubitCircuit.add_gate()

In qutip.qip.QubitCircuit.add_gate(), there is a optional list type attribute called index.
This seems to be used to insert gates in the middle of the gate list (qutip.qip.QubitCircuit.gates).
The corresponding code is

Feature details

The qml.transforms.insert() transform was recently added in PennyLaneAI/pennylane#1795, allowing users to insert a specified single qubit gate into a circuit with three orientations:

• at the start of the circuit
• at the end of the circuit
• after every gate in the circuit

However, it might also be nice to have the option of inserting multiqubi

For example, pylint would have caught ProjectQ-Framework/ProjectQ#19 via an undefined variable warning.

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
Some of the code cells in the Japanese translation of the textbook are outdated and might not work with the latest version of Qiskit. These files need to be updated by a Japanese speaker to match the English version of the textbook (under i18n/locales/ja/):

• ch-algorithms/shor.ipynb
• ch-algorithms/defining-quantum-circuits.ipynb
• `ch-algorithms/sim

The formulas at API page for https://docs.microsoft.com/en-us/qsharp/api/qsharp/microsoft.quantum.preparation.purifiedmixedstatewithdata are also broken, but I couldn't figure out what caused it at a glance.

Originally posted by @tcNickolas in microsoft/QuantumLibraries#484 (comment)

The standard gates were defined pre-DEFGATE-AS so everything is an ugly matrix. Rewrite the file to use the most natural and straightforward definitions.