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

What is the expected enhancement?

We should add support for Dict[str, Optional[OperatorBase]] structures to be passed as aux_operators into our algorithms.

Motivation

Currently, both the `MinimumEigens

I'm getting type errors in pycharm when I'm trying to run a FrozenCircuit. I think there should be no downside to switching the type annotation to AbstractCircuit, of which both Circuit and FrozenCircuit derive?

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

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

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

In QASM2, the BNF listed a set of buit-in unary functions,sin j cos j tan j exp j ln j sqrt. However, it was not explicit on their meaning.

QASM3 specification does not list (as far as I could check) the built-in functions and their meaning and I think it should.

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

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

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:

There seems to be confusion between 'schedule' and 'scheduler' throughout sources and doc. They seem to be used interchangeably, which seems confusing. Is a "schedule" the same as a "scheduleR"?

For example, consider the following code snippet in src/compressor/compressor.lisp:

  (let ((lschedule (make-lscheduler)))
    ;; load up the logical schedule

The variable lschedule and