MNT Bench: Layout Library for Field-coupled Nanocomputing Circuits
MNT Bench is a field-coupled nanocomputing circuit benchmark suite for multiple gate libraries and clocking schemes.
MNT Bench is part of the Munich Nanotech Toolkit (MNT) developed by the Chair for Design Automation at the Technical University of Munich and is hosted at https://www.cda.cit.tum.de/mntbench/.
This documentation explains how to use MNT Bench to filter and download benchmarks.
Benchmark Selection
So far, the functions from the following benchmark sets are implemented and provided:
Gate Libraries
So far, MNT Bench supports the following native gate-sets:
- ONE (for QCA) gate set: [AND, OR, NOT, BUF]
- Bestagon (for SiDB) gate set: [AND, NAND, OR, NOR, XOR, XNOR, NOT, BUF]
Clocking Schemes
Most of the layouts are available for any of the following clocking schemes:
| 2DDWave | ESR |
|---|---|
 |
 |
| USE | RES |
|---|---|
 |
 |
| Row |
|---|
 |
Repository structure
src/mnt/bench/ Viewer backend, templates, and static assets
tests/ Unit and integration tests
Repository usage
There are three ways how to use this benchmark suite:
- Via the webpage hosted at https://www.cda.cit.tum.de/mntbench/
- Via the pip package
mnt.bench - Directly via this repository
Since the first way is rather self-explanatory, the other two ways are explained in more detail in the following.
Usage via the Python package
MNT Bench supports Python 3.10 through 3.14 and is available from PyPI.
python -m venv .venv
source .venv/bin/activate
python -m pip install mnt.bench
On Windows, activate the environment with .venv\Scripts\activate.
Locally hosting the MNT Bench Viewer
Additionally, this python package includes the same webserver used for the hosting of the MNT Bench webpage.
Start the MNT Bench Viewer from the terminal with either command:
mnt-bench
mnt.bench
This first searches for the most recent version of the benchmark files on GitHub and offers to download them.
The archive is stored in ~/.mntbench by default. Afterwards, the webserver is started locally.
The package includes an empty MNTBench_all.zip placeholder; the actual benchmarks are downloaded from the newest
compatible release containing the archive, which may be older than the package release.
Usage directly via this repository
Clone and install the repository with:
git clone https://github.com/cda-tum/mnt-bench.git
cd mnt-bench
python -m pip install .
Afterwards, the package can be used as described above.
1 maintainer
Metadata
1 maintainer
Release files for mnt.bench 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mnt_bench-0.4.1.tar.gz | 2.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mnt_bench-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.3 MB
Release files / mnt_bench-0.4.1.tar.gz
| Download URL | mnt_bench-0.4.1.tar.gz |
|---|---|
| Size | 2.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b271f5187d3302fb3dc52c8cc4aaca4a478addf61cafd27802815033d9b03379
|
|
BLAKE2b-256 checksum How to use checksums |
4ab57a70e18701deedb94cd51806466d0f116aeaf767d378eda73ff8ebe16825
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 7, 2026.
Transparency logRelease files / mnt_bench-0.4.1-py3-none-any.whl
| Download URL | mnt_bench-0.4.1-py3-none-any.whl |
|---|---|
| Size | 2.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2559914aaf5d520be86a0f149abd1bd79e33cfa59c6be19021214bbd095dba4c
|
|
BLAKE2b-256 checksum How to use checksums |
979789afb4f6e425d36cbde899f5dd89f9956e7a66298a124266ef08de3ef661
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 7, 2026.
Transparency log
