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

What is the expected enhancement?

Many users land in https://qiskit.org/documentation/stubs/qiskit.circuit.Parameter.html when search on how to parametrize circuits. @Cryoris did a good jobs at explaining them in https://quantumcomputing.stackexchange.com/questions/13558/how-to-add-several-parameters-in-qiskit-circuit . I think the Parameter docstring needs a short example.

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.
The dimension argument of qutip operators are quite inconsistent in the naming, type and description. Here are a few examples picked from the functions doc page:

• basis > dimensions: int or list of ints _Number of Fock states in Hilbert space. If a list, then

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

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

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)

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.