quantum

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: 0.18
• Python version: 3.7

What is the current behavior?

This follows #6574 . When a QuantumCircuit is initialized with isolates qubits there are some issues as follows

• `qc.reverse_bits()

Include a script that can generate weekly status reports to dev's leadership. The report should have enough buzzwords to make leadership feel as if progress is being made without providing any specific detail that defines said progress.

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

As I was inspecting the MultiControlledX gate, I noticed how it printed out:

MultiControlledX(array([[0, 1],
       [1, 0]]), wires=[0, 1, 2, 3])

And was quite confused as to where the array came from. It turns out MultiControlledX inherits from ControlledQubitUnitary with the Unitary matrix as an X gate. This makes MultiControlledX a parametrized gate.

Worse yet, th

Currently, the Bosonic backend does not support the MeasureFock and MeasureThreshold measurement operations. It would be great to add support for these two operations to the Bosonic backend.

This would entail writing functions to calculate the different probabilities up to a given cutoff, using numpy to sample from this distribution and writing update rules for updating the post measurement

Most documentation comments in the compiler only use the <summary> tag. For short comments, this is fine, but in many cases the summary is several paragraphs long and would be easier to read if it used standard documentation tags to structure the information. This is especially important for exceptions - exceptions mentioned in the <summary> tag are easy to miss, whereas the special `<exceptio

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:

This should prevent things like #701
It would be great to generate automatically the list of oldest dependencies with something like

import pkg_resources

package = pkg_resources.working_set.by_key["netket"]

oldest_dependencies = []

for requirement in package.requires():
    dependency = requirement.project_name
    if requirement.extras:
        dependency += '[' + ','.

Describe the bug

The QIR Runtime readme lists the required LLVM version as 11.0.0, while the prereq installation script uses version 11.1.0.

We need to create a Q.History documentation page that is similar in nature to the existing Q class documentation pages. See Q-ComplexNumber.html as an example.