quantum-programming-language

What is the expected enhancement?

Currently, accessing the preset passmanagers (outside of a call to transpile) requires building a pass_manager_config by hand, like:

from qiskit.transpiler import PassMan

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

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

RDMs returned from pyscf are spin summed. Use https://sunqm.github.io/pyscf/_modules/pyscf/fci/direct_spin1.html#FCISolver.make_rdm12s

to return non-spin summed versions. Recombine spin-separated RDMs like run_psi4 to get spin-orbital rdms before returning to OpenFermion.

Now that Q# + Python can use project files for references, we should add them here so IntelliSense can work better :)

It may be cool to have some counter of contributions showing up on the website, which could include from minimal to extensive information like the number of open PRs, commits, merged lines of code, contributors, etc.

If this were to update "live" or regularly, it could be very cool.

There may be some off-the-shelves tools such as github actions for this, see for example: https://github.com

Looking for a Zookeeper who can help manage and drive more algorithms to be implemented in the zoo!

https://github.com/qsharp-community/algorithm-zoo