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

According to the official docs:

"The action of a __slots__ declaration is limited to the class where it is defined. As a result, subclasses will have a __dict__ unless they also define __slots__ (which must only contain names of any additional slots)."

What is the expected enhancement?

All subclasses down the inheritance chain (Qubit, Clbit, AncillaQubit) ought to define:

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.

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

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

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)

(Up for grabs for anyone who wants to do this)

Docpages generated for flax modules such as our models (RBM, RBMSymm, DenseSymm) are somehow... confused.
That's because Flax modules have a lot of methods scattered around and the attributes get put a bit everywhere.

Moreover, attributes of the model/layer itself are mixed with attributes common to all flax modules that are not really relevan

In addition to the current acceptable arguments for Q.Matrix, it ought to accept a Template literal (Template string) as a solo argument to make it trivially easy for something like this:

var m = new Q.Matrix(`
    1 2 3 4
    5 6 7 8`)

This makes the task of creating arbitrary matrices much more human readable than passing nested Arrays, or even just a series of Arrays.

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.

Information

• Qiskit Metal version:
• Python version:
• Operating system:

Conversation in slack at #metal.
https://qiskit.slack.com/archives/C01R8KP5WP7/p1638275287214400

What is the current behavior?

It a

moments.add() and circuit.add() are slightly inconsistent.
circuits accept both Instruction and Iterable[Instruction] while moments take a strict Iterable.
This is confusing for the user:

circ.moments.add(Instruction(gate, target))  # doesnt work
circ.moments.add([Instruction(gate, target)])  # works

while both work for circuit classes:

circ.add(Instruction(gat