MQT Bench: Benchmarking Software and Design Automation Tools for Quantum Computing
MQT Bench is a quantum circuit benchmark suite with cross-level support, i.e., providing the same benchmark algorithms for different abstraction levels throughout the quantum computing software stack. MQT Bench is part of the Munich Quantum Toolkit (MQT) developed by the Chair for Design Automation at the Technical University of Munich and is hosted at https://www.cda.cit.tum.de/mqtbench/.
If you have any questions, feel free to create a discussion or an issue on GitHub.
Getting Started
mqt-bench is available via PyPI.
(venv) $ pip install mqt.bench
The following code gives an example on the usage:
from mqt.bench import get_benchmark
# get a benchmark circuit on algorithmic level representing the GHZ state with 5 qubits
qc_algorithmic_level = get_benchmark(benchmark_name="ghz", level="alg", circuit_size=5)
# draw the circuit
print(qc_algorithmic_level.draw())
Detailed documentation and examples are available at ReadTheDocs.
Availability as a PennyLane Dataset
MQT Bench is also available as a PennyLane dataset.
References
In case you are using MQT Bench in your work, we would be thankful if you referred to it by citing the following publication:
@article{quetschlich2023mqtbench,
title = {{{MQT Bench}}: {Benchmarking Software and Design Automation Tools for Quantum Computing}},
shorttitle = {{MQT Bench}},
journal = {{Quantum}},
author = {Quetschlich, Nils and Burgholzer, Lukas and Wille, Robert},
year = {2023},
doi = {10.22331/q-2023-07-20-1062},
eprint = {2204.13719},
primaryclass = {quant-ph},
archiveprefix = {arxiv},
note = {{{MQT Bench}} is available at \url{https://www.cda.cit.tum.de/mqtbench/}},
}
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, and the State of Upper Austria in the frame of the COMET program (managed by the FFG).
Release files for mqt-bench 1.1.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mqt_bench-1.1.9.tar.gz | 5.0 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mqt.bench-1.1.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.1 MB
Release files / mqt_bench-1.1.9.tar.gz
| Download URL | mqt_bench-1.1.9.tar.gz |
|---|---|
| Size | 5.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
36ed1d4567e3483ba7ed6184482411ba46456584102bf58c46319bc67b15a0de
|
|
BLAKE2b-256 checksum How to use checksums |
80226f440ca3169af2d622e634233cb463edb3f054ee822d3b93c51d5f12b67f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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 Dec 1, 2024.
Transparency logRelease files / mqt.bench-1.1.9-py3-none-any.whl
| Download URL | mqt.bench-1.1.9-py3-none-any.whl |
|---|---|
| Size | 95.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dbcf813b1a402a97b1617b374ae4a95456bdef1ce58f1bd45b93d429c5374a26
|
|
BLAKE2b-256 checksum How to use checksums |
c29a819df87a8fe2120143b280c922ce58f60aeb42408b248b2d4cbddacb675a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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 Dec 1, 2024.
Transparency log
