monoprop-bench-tools 0.9.0__tar.gz

monoprop_bench_tools-0.9.0/.gitignore

@@ -0,0 +1,189 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+# using lib/ would exclude the docs/src/lib directory used by next.js
+/lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# setuptools_scm / hatch-vcs
+src/*/_version.py
+packages/*/src/*/_version.py
+
+
+# ruff
+.ruff_cache/
+
+# OS specific stuff
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db
+
+# Common editor files
+*~
+*.swp
+
+external/upstream/_srcs/
+tests/cpp/_srcs/
+_dispatch*.py
+_constants.py
+build*/
+Testing/
+
+# pixi environments
+.pixi
+*.egg-info
+sandbox/**
+
+# locally generated benchmark artifacts (keep the tracked README.md)
+benches/results/**
+!benches/results/README.md
+
+# devcontainer files
+.devcontainer/devcontainer-lock.json
+
+# Useful when running in clusters
+logs/
+
+# Figures and sidecars regenerated by the third-party benchmark plotting scripts.
+# The published copies live in docs/public/benchmarks/; these are working artifacts.
+packages/bench-third-party/*.png
+packages/bench-third-party/*/*.png
+packages/bench-third-party/pauli_prop/pauli_scaling.md
+packages/bench-third-party/pauli_prop/pauli_speedup.md

monoprop_bench_tools-0.9.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

monoprop_bench_tools-0.9.0/PKG-INFO

@@ -0,0 +1,106 @@
+Metadata-Version: 2.5
+Name: monoprop-bench-tools
+Version: 0.9.0
+Summary: Benchmark harness for monoprop: memory accounting, model builders, and result renderers.
+Project-URL: Homepage, https://github.com/Algorithmiq/monoprop
+Project-URL: Bug Tracker, https://github.com/Algorithmiq/monoprop/issues
+Project-URL: Changelog, https://github.com/Algorithmiq/monoprop/releases
+Author-email: Algorithmiq Development Team <aurora@algorithmiq.fi>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Scientific/Engineering :: Physics
+Classifier: Topic :: System :: Benchmark
+Classifier: Typing :: Typed
+Requires-Python: <3.15,>=3.11
+Requires-Dist: monoprop
+Requires-Dist: numpy>=2
+Requires-Dist: psutil>=7.2
+Requires-Dist: tabulate>=0.9
+Provides-Extra: gpu-cuda12
+Requires-Dist: cupy-cuda12x>=13; extra == 'gpu-cuda12'
+Provides-Extra: gpu-cuda13
+Requires-Dist: cupy-cuda13x>=14; extra == 'gpu-cuda13'
+Description-Content-Type: text/markdown
+
+# monoprop-bench-tools
+
+The benchmark harness behind [monoprop](https://github.com/Algorithmiq/monoprop):
+the pieces that are reusable outside a single benchmark run, packaged separately
+so scripts, notebooks and third-party comparisons can depend on them without
+vendoring the repository's `benches/` directory.
+
+| Module | What it gives you |
+| --- | --- |
+| `monoprop_bench_tools.memory.cpu` | Exact peak-RSS measurement from the kernel's `VmHWM`. |
+| `monoprop_bench_tools.memory.gpu` | The device-side counterpart, over CUDA memory-pool counters or a CuPy allocation hook. |
+| `monoprop_bench_tools.models` | Builders for the benchmarked problems: a configurable random problem, a 120-mode Fermi-Hubbard model, and a 127-qubit kicked-Ising model. |
+| `monoprop_bench_tools.report` | Renders a run's artifacts into a side-by-side Markdown report. |
+| `monoprop_bench_tools.bmf` | Renders a run's artifacts into [Bencher](https://bencher.dev/) Metric Format JSON. |
+
+## Install
+
+```bash
+pip install monoprop-bench-tools
+```
+
+### GPU support
+
+`monoprop_bench_tools.memory.gpu` needs [CuPy](https://cupy.dev/), and only
+CuPy. Pick the extra matching your CUDA toolkit:
+
+```bash
+pip install "monoprop-bench-tools[gpu-cuda12]"   # CUDA 12.x
+pip install "monoprop-bench-tools[gpu-cuda13]"   # CUDA 13.x
+```
+
+Pick one, not both: the two CuPy builds ship the same top-level `cupy` package.
+On a host with no system CUDA toolkit, add CuPy's bundled one with
+`pip install "cupy-cuda12x[ctk]"`.
+
+Without CuPy the module still imports, and every reading reports
+`Method.UNAVAILABLE` instead of a figure you might mistake for a real one.
+
+## Use
+
+Measure the peak resident footprint of a block, exactly (no sampling):
+
+```python
+from monoprop_bench_tools.memory.cpu import HighWaterMark
+from monoprop_bench_tools.models import build_hubbard_problem
+
+with HighWaterMark() as hwm:
+    propagator, circuit = build_hubbard_problem()
+    propagator.build_graph(circuit)
+
+print(f"{hwm.peak_mb:.0f} MB peak, exact={hwm.exact}")
+```
+
+Render the artifacts of a run:
+
+```bash
+monoprop-bench-report benches/results             # writes REPORT.md
+monoprop-bench-bmf benches/results ci-linux       # BMF JSON on stdout
+```
+
+Both read the two files a run leaves in the results directory:
+`time-<label>.json` (pytest-benchmark timings) and `<label>.json` (memory,
+operator sizes, configuration). The schema is documented in the repository's
+`benches/results/README.md`, and written by the suite in `benches/conftest.py`.
+
+## Scope
+
+This package deliberately holds no benchmarks. monoprop's own suite lives in the
+repository's `benches/` directory, because its benchmark names are the key
+Bencher's history is stored under and must not move with a library release.
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

monoprop_bench_tools-0.9.0/README.md

@@ -0,0 +1,74 @@
+# monoprop-bench-tools
+
+The benchmark harness behind [monoprop](https://github.com/Algorithmiq/monoprop):
+the pieces that are reusable outside a single benchmark run, packaged separately
+so scripts, notebooks and third-party comparisons can depend on them without
+vendoring the repository's `benches/` directory.
+
+| Module | What it gives you |
+| --- | --- |
+| `monoprop_bench_tools.memory.cpu` | Exact peak-RSS measurement from the kernel's `VmHWM`. |
+| `monoprop_bench_tools.memory.gpu` | The device-side counterpart, over CUDA memory-pool counters or a CuPy allocation hook. |
+| `monoprop_bench_tools.models` | Builders for the benchmarked problems: a configurable random problem, a 120-mode Fermi-Hubbard model, and a 127-qubit kicked-Ising model. |
+| `monoprop_bench_tools.report` | Renders a run's artifacts into a side-by-side Markdown report. |
+| `monoprop_bench_tools.bmf` | Renders a run's artifacts into [Bencher](https://bencher.dev/) Metric Format JSON. |
+
+## Install
+
+```bash
+pip install monoprop-bench-tools
+```
+
+### GPU support
+
+`monoprop_bench_tools.memory.gpu` needs [CuPy](https://cupy.dev/), and only
+CuPy. Pick the extra matching your CUDA toolkit:
+
+```bash
+pip install "monoprop-bench-tools[gpu-cuda12]"   # CUDA 12.x
+pip install "monoprop-bench-tools[gpu-cuda13]"   # CUDA 13.x
+```
+
+Pick one, not both: the two CuPy builds ship the same top-level `cupy` package.
+On a host with no system CUDA toolkit, add CuPy's bundled one with
+`pip install "cupy-cuda12x[ctk]"`.
+
+Without CuPy the module still imports, and every reading reports
+`Method.UNAVAILABLE` instead of a figure you might mistake for a real one.
+
+## Use
+
+Measure the peak resident footprint of a block, exactly (no sampling):
+
+```python
+from monoprop_bench_tools.memory.cpu import HighWaterMark
+from monoprop_bench_tools.models import build_hubbard_problem
+
+with HighWaterMark() as hwm:
+    propagator, circuit = build_hubbard_problem()
+    propagator.build_graph(circuit)
+
+print(f"{hwm.peak_mb:.0f} MB peak, exact={hwm.exact}")
+```
+
+Render the artifacts of a run:
+
+```bash
+monoprop-bench-report benches/results             # writes REPORT.md
+monoprop-bench-bmf benches/results ci-linux       # BMF JSON on stdout
+```
+
+Both read the two files a run leaves in the results directory:
+`time-<label>.json` (pytest-benchmark timings) and `<label>.json` (memory,
+operator sizes, configuration). The schema is documented in the repository's
+`benches/results/README.md`, and written by the suite in `benches/conftest.py`.
+
+## Scope
+
+This package deliberately holds no benchmarks. monoprop's own suite lives in the
+repository's `benches/` directory, because its benchmark names are the key
+Bencher's history is stored under and must not move with a library release.
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

monoprop_bench_tools-0.9.0/pyproject.toml

@@ -0,0 +1,87 @@
+[build-system]
+requires = ["hatchling>=1.27", "hatch-vcs>=0.4"]
+build-backend = "hatchling.build"
+
+
+[project]
+name = "monoprop-bench-tools"
+authors = [
+  { name = "Algorithmiq Development Team", email = "aurora@algorithmiq.fi" },
+]
+description = "Benchmark harness for monoprop: memory accounting, model builders, and result renderers."
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+readme = "README.md"
+requires-python = ">=3.11,<3.15"
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Intended Audience :: Science/Research",
+  "Intended Audience :: Developers",
+  "Operating System :: POSIX :: Linux",
+  "Operating System :: MacOS",
+  "Programming Language :: Python",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3 :: Only",
+  "Topic :: Scientific/Engineering :: Physics",
+  "Topic :: System :: Benchmark",
+  "Typing :: Typed",
+]
+dynamic = ["version"]
+dependencies = [
+  "monoprop",
+  "numpy>=2",
+  "psutil>=7.2",
+  "tabulate>=0.9",
+]
+
+
+[project.optional-dependencies]
+gpu-cuda12 = ["cupy-cuda12x>=13"]
+gpu-cuda13 = ["cupy-cuda13x>=14"]
+
+
+[project.urls]
+Homepage = "https://github.com/Algorithmiq/monoprop"
+"Bug Tracker" = "https://github.com/Algorithmiq/monoprop/issues"
+Changelog = "https://github.com/Algorithmiq/monoprop/releases"
+
+
+[project.scripts]
+monoprop-bench-report = "monoprop_bench_tools.report:main"
+monoprop-bench-bmf = "monoprop_bench_tools.bmf:main"
+
+
+[dependency-groups]
+test = ["pytest>=8.2.2,<9.1"]
+
+
+# Only consulted when this package is tested on its own; a run from the
+# repository root is governed by the root pyproject.toml.
+[tool.pytest.ini_options]
+minversion = "8.0"
+addopts = ["--import-mode=importlib", "-ra", "--strict-markers", "--strict-config"]
+xfail_strict = true
+filterwarnings = ["error"]
+testpaths = ["tests"]
+
+
+# `monoprop` is a workspace member during development, but the published
+# distribution resolves it from PyPI like any other dependency.
+[tool.uv.sources]
+monoprop = { workspace = true }
+
+
+# The version comes from the repository's git tags, so a monoprop release tags
+# the tools that measure it. `root` points at the repository, not this package.
+[tool.hatch.version]
+source = "vcs"
+raw-options = { root = "../.." }
+
+[tool.hatch.build.hooks.vcs]
+version-file = "src/monoprop_bench_tools/_version.py"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/monoprop_bench_tools"]
+
+[tool.hatch.build.targets.sdist]
+include = ["src", "tests", "README.md", "LICENSE"]

monoprop_bench_tools-0.9.0/src/monoprop_bench_tools/__init__.py

@@ -0,0 +1,30 @@
+# Copyright 2026 Algorithmiq
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+"""Benchmark harness for monoprop.
+
+The reusable half of monoprop's benchmark suite: memory accounting
+(:mod:`monoprop_bench_tools.memory`), the builders for the benchmarked problems
+(:mod:`monoprop_bench_tools.models`), and the two renderers of a run's artifacts
+(:mod:`monoprop_bench_tools.report`, :mod:`monoprop_bench_tools.bmf`).
+
+Submodules are not imported eagerly, so ``import monoprop_bench_tools`` stays
+cheap and does not require the optional GPU dependencies.
+"""
+
+from __future__ import annotations
+
+from monoprop_bench_tools._version import __version__, __version_tuple__
+
+__all__ = ["__version__", "__version_tuple__"]