Skip to main content

GraphQOMB

License PyPI version Python Versions Documentation Status codecov pytest typecheck Ruff

GraphQOMB (Qompiler for Measurement-Based Quantum Computing, pronounced graphcomb) is a compiler framework for measurement-based quantum computation (MBQC). It keeps the resource-state structure, classical feedforward, and execution schedule as separate first-class objects, then lowers them to an executable measurement pattern with a Pauli frame.

This design makes GraphQOMB useful both as an executable MBQC compiler and as a foundation for fault-tolerant workflows. The same core pipeline can be used to build patterns, study schedule-dependent resource tradeoffs, simulate them with statevector or density-matrix backends, and export compatible patterns to Stim-oriented downstream tooling.

Core Workflow

GraphQOMB is organized around three explicit compiler interfaces:

  • Labelled graph state: the resource state, measurement bases, and I/O registration.
  • Feedforward maps: explicit xflow and optional zflow describing classical dependencies.
  • Scheduler: preparation, entanglement, and measurement order for executable slices.

These are lowered with qompile(...) into a Pattern carrying:

  • a command stream for scheduled MBQC execution,
  • a PauliFrame for classical dependency tracking,
  • metrics such as max_space, depth, and active_volume.

Features

  • Explicit IR boundaries: work directly with graph-state, feedforward, and schedule objects instead of mixing them into a single representation.
  • Pattern lowering: compile MBQC IRs into executable patterns with TICK-delimited slices and Pauli-frame tracking.
  • Schedule analysis: compare depth-oriented and space-oriented schedules and inspect resulting resource metrics.
  • Simulation: run circuit or pattern simulations with statevector and density-matrix backends.
  • Stim export: compile compatible patterns to Stim text for downstream FT-oriented analysis.
  • Toolchain interoperability: use GraphQOMB downstream of circuit transpilation and graph-rewrite tooling such as PyZX and flow-finding utilities.

Installation

From PyPI

uv add graphqomb

Install optional PyZX integration:

uv add "graphqomb[pyzx]"

Install optional Stim integration:

uv add "graphqomb[stim]"

From Source

git clone https://github.com/UTokyo-FT-MBQC/graphqomb.git
cd graphqomb
uv sync

Install development dependencies:

uv sync --extra dev

Install documentation dependencies:

uv sync --extra doc

Quick Start

The quickest way to see the compiler pipeline is to start from an MBQC-native circuit, derive the graph/feedforward/schedule objects, and lower them into a pattern:

import numpy as np

from graphqomb.circuit import MBQCCircuit, circuit2graph
from graphqomb.qompiler import qompile
from graphqomb.simulator import PatternSimulator, SimulatorBackend

circuit = MBQCCircuit(3)
circuit.j(0, 0.5 * np.pi)
circuit.cz(0, 1)
circuit.cz(0, 2)
circuit.j(1, 0.75 * np.pi)
circuit.j(2, 0.25 * np.pi)

graphstate, xflow, scheduler = circuit2graph(circuit)
pattern = qompile(graphstate, xflow, scheduler=scheduler)

print("pattern depth:", pattern.depth)
print("pattern max space:", pattern.max_space)

simulator = PatternSimulator(pattern, SimulatorBackend.StateVector)
simulator.simulate()
print(simulator.state.state())

If you already have a graph-state design and explicit feedforward maps, you can skip circuit2graph(...) and call qompile(...) directly.

Documentation

Current Scope

GraphQOMB currently targets static, branch-free MBQC workflows. It is designed around causal feedforward dependencies and explicit scheduling, which makes it a good fit for pattern generation, simulation, and offline analysis of executable or fault-tolerant MBQC pipelines.

Development

Running Tests

uv run pytest
uv run pytest tests/test_specific.py

Code Quality

uv run ruff check
uv run ruff format
uv run mypy
uv run pyright

Building Documentation

cd docs
uv run sphinx-build -W source build

Contributing

Contributions are welcome. Please open an issue or pull request with:

  1. A clear description of the change.
  2. Tests for behavioral changes when applicable.
  3. Documentation updates for user-facing features.

Related Projects

  • graphix: MBQC software stack with a different abstraction strategy.
  • PyZX: ZX-calculus tooling that can be used upstream of GraphQOMB.
  • swiflow: Flow-finding utilities for MBQC dependency structures.
  • Stim: Fast stabilizer-circuit simulator targeted by the Stim export path.

Our ongoing projects

License

MIT License

Citation

If you use GraphQOMB in your research, please cite:

@software{graphqomb,
  title = {GraphQOMB: A Modular Graph State Qompiler for Measurement-Based Quantum Computation},
  author = {Masato Fukushima, Sora Shiratani, Yuki Watanabe, and Daichi Sasaki},
  year = {2025},
  url = {https://github.com/UTokyo-FT-MBQC/graphqomb}
}

Acknowledgements

We acknowledge the NICT Quantum Camp for supporting our development.

Special thanks to Fixstars Amplify:

amplify

Metadata

Release files for graphqomb 0.5.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for graphqomb 0.5.3
File Size Uploaded
graphqomb-0.5.3.tar.gz 224.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for graphqomb 0.5.3
File Interpreter ABI Platform
graphqomb-0.5.3-py3-none-any.whl Python 3 none any Details

Total release size: 376.5 kB

Release files / graphqomb-0.5.3.tar.gz

Download URL graphqomb-0.5.3.tar.gz
Size 224.8 kB
Tags Source
SHA-256 checksum
How to use checksums
da88dd33f1fc3179309083a47f833323829a7552cd0458d3152fa21b6c3e9a96
BLAKE2b-256 checksum
How to use checksums
47494a4fa22910d9e82f7d2b6ae2aa97216dc641e4518947df858cff73ce244e
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 Aug 14, 2026.

Transparency log

Release files / graphqomb-0.5.3-py3-none-any.whl

Download URL graphqomb-0.5.3-py3-none-any.whl
Size 151.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c37afebfffefc7901c9ddc16453cb14798a150738dc4d9c73aaf3b9dbb349b73
BLAKE2b-256 checksum
How to use checksums
88db112f56725170478f8aea5acf6934308d2f2126b4cbd5a76157315d27c53f
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 Aug 14, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.5.3 This release

2 release files

0.5.2

2 release files

0.5.1

2 release files

0.5.0

2 release files

0.4.2

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page