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

Environment

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

What is happening?

The configuration file stores dtm in nanoseconds while BackendV2 interfaces defines dtm in seconds.

https://github.com/Qiskit/qiskit-terra/blob/d692bb74a660d21b1fa8019d0b0efcce3c7f31d7/qiskit/test/mock/fake_backend.py#L170-L177

Related to a similar issue for dt:

Is your feature request related to a use case or problem? Please describe.
Right now a lot of modules (in particular tests) are pretty free form with how they do imports. It's a good practice to import modules wherever possible.

bad:

from cirq.devices import GridQubit

good:

from cirq import devices

devices.GridQubit(whatever)

**Describe the soluti

Feature details

The qml.kernels.utils.py file contains the utility functions to compute the square kernel matrix of a training set as well as the kernel matrix between training and test data. There are some aspects that could be updated though:

• These functions are not compatible with all frameworks, for example the usage of np.array in these functions prohibits using them with Torch or

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

Problem Description

Currently the documentation PDF has to be built locally for each release.

Proposed Solution

Build the documentation in a GitHub action either for each push or when deploying a release.

What is the expected enhancement?

The openQASM project should have release notes associated with each tagged release (see #321). These should contain a summary of all changes included in the prepared release (or the development branch). For ease (and distribution) of maintenance, we should consider using reno which has been used with success in Qiski

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

Is your feature request related to a problem? Please describe.
Adding concrete examples to API documentation comments can help clarify how Q# functions and operations are to be used. For example, the documentation for Microsoft.Quantum.Arrays.ElementsAt lists how the function acts on a variety of arrays:

right now, absolute jumps are conflated in the label object here. I'd prefer we instead introduce a new object called absolute-program-location or something like that. (I don't want to use "address" only because it feels too dishonest.) If we do this, then we'd change patch-labels to not overwrite these label objects, and we'