MQT Predictor: Automatic Device Selection with Device-Specific Circuit Compilation for Quantum Computing
MQT Predictor is a framework that allows one to automatically select a suitable quantum device for a particular application and provides an optimized compiler for the selected device. It not only supports end-users in navigating the vast landscape of choices, it also allows to mix-and-match compiler passes from various tools to create optimized compilers that transcend the individual tools. Evaluations on more than 500 quantum circuits and seven devices have shown that—compared to Qiskit's and TKET's most optimized compilation flows—the MQT Predictor yields circuits with an expected fidelity that is on par with the best possible result that could be achieved by trying out all combinations of devices and compilers and even achieves a similar performance when considering the critical depth as an alternative figure of merit.
Therefore, MQT Predictor tackles this problem from two angles:
-
It provides a method (based on Reinforcement Learning) that produces device-specific quantum circuit compilers by combining compilation passes from various compiler tools and learning optimized sequences of those passes with respect to a customizable figure of merit). This mix-and-match of compiler passes from various tools allows one to eliminate vendor locks and to create optimized compilers that transcend the individual tools.
-
It provides a prediction method (based on Supervised Machine Learning) that, without performing any compilation, automatically predicts the most suitable device for a given application. This completely eliminates the manual and laborious task of determining a suitable target device and guides end-users through the vast landscape of choices without the need for quantum computing expertise.
For more details, please refer to:
MQT Predictor is part of the Munich Quantum Toolkit (MQT) developed by the Chair for Design Automation at the Technical University of Munich.
If you have any questions, feel free to create a discussion or an issue on GitHub.
Getting Started
mqt-predictor is available via PyPI.
(venv) $ pip install mqt.predictor
The following code gives an example on the usage:
from mqt.predictor import qcompile
from mqt.bench import get_benchmark
# get a benchmark circuit on algorithmic level representing the GHZ state with 5 qubits from [MQT Bench](https://github.com/cda-tum/mqt-bench)
qc_uncompiled = get_benchmark(benchmark_name="ghz", level="alg", circuit_size=5)
# compile it using the MQT Predictor
qc_compiled, compilation_information, quantum_device = qcompile(
qc_uncompiled, devices="all", figure_of_merit="expected_fidelity"
)
# print the selected device and the compilation information
print(quantum_device, compilation_information)
# draw the compiled circuit
print(qc_compiled.draw())
Further documentation and examples are available at ReadTheDocs.
References
In case you are using MQT Predictor in your work, we would be thankful if you referred to it by citing the following publication:
@ARTICLE{quetschlich2024mqtpredictor,
AUTHOR = {N. Quetschlich and L. Burgholzer and R. Wille},
TITLE = {{MQT Predictor: Automatic Device Selection with Device-Specific Circuit Compilation for Quantum Computing}},
YEAR = {2024},
JOURNAL = {ACM Transactions on Quantum Computing (TQC)},
DOI = {10.1145/3673241},
EPRINT = {2310.06889},
EPRINTTYPE = {arxiv},
}
Acknowledgements
This project received funding from the European Research Council (ERC) under the European Union's Horizon 2020 research and innovation program (grant agreement No. 101001318), was part of the Munich Quantum Valley, which is supported by the Bavarian state government with funds from the Hightech Agenda Bayern Plus, and has been supported by the BMWK on the basis of a decision by the German Bundestag through project QuaST, as well as by the BMK, BMDW, the State of Upper Austria in the frame of the COMET program, and the QuantumReady project within Quantum Austria (managed by the FFG).
Metadata
Release files for mqt.predictor 2.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mqt_predictor-2.2.0.tar.gz | 2.5 MB | With provenance | Details for mqt_predictor-2.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mqt.predictor-2.2.0-py3-none-any.whl | Python 3 | none | any | Details for mqt.predictor-2.2.0-py3-none-any.whl |
Total release size: 3.8 MB
Release files / mqt_predictor-2.2.0.tar.gz
| Download URL | mqt_predictor-2.2.0.tar.gz |
|---|---|
| Size | 2.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9bd0a30cdec977eae3055831ce8886ef4505b4678f3f22c8b0966e21f3ec297
|
|
BLAKE2b-256 checksum How to use checksums |
d1d01f6f2ee37f18dcecb59fd187c9d6550e0e5683629156a55ee9a094fd98f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 2, 2025.
Transparency logRelease files / mqt.predictor-2.2.0-py3-none-any.whl
| Download URL | mqt.predictor-2.2.0-py3-none-any.whl |
|---|---|
| Size | 1.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
555936cfbe70106654a5ee19b720bbbbba2fc1c47a06cb9341054c37a559ebf4
|
|
BLAKE2b-256 checksum How to use checksums |
3c84b7cf2763869f7d7351e9ffe8e2dbfc25dcfdb3d68d449aa8c4a57deb6332
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 2, 2025.
Transparency logSecurity for mqt.predictor 2.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for mqt_predictor-2.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 2, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.