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?

It would be useful if the XY gate could be added to the existing circuit library https://qiskit.org/documentation/apidoc/circuit_library.html

The use case is for a basis gate for the qiskit transpiler.

Description of the issue
PhasedISwapPowGate is an EigenGate but unlike most other eigen gates, it's constructor does not take global_shift as an argument and it always defaults to 0.

For consistency, we should add an additional global_shift parameter to PhasedISwapPowGate.

Cirq version
0.13.0.dev

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

Feature details

I would like to enable a regularizer option for the weights of a KerasLayer, i.e., something similar to a “kernel_regularizer” option for Dense and Conv layers in Tensorflow:

https://www.tensorflow.org/api_docs/python/tf/keras/layers/Dense

More background provided here: https://discuss.pennylane.ai/t/adding-regularization-to-keraslayer/1420

Implementation

Yes, it

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.

Describe the issue
"where a and a† are the raising a lowering operators of the resonator photons"
Describe what you expect to see
"where a and a† are the raising and lowering operators of the resonator photons"

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)

The standard gates were defined pre-DEFGATE-AS so everything is an ugly matrix. Rewrite the file to use the most natural and straightforward definitions.