Qiskit addon: circuit cutting
Table of Contents
About
Qiskit addons are a collection of modular tools for building utility-scale workloads powered by Qiskit.
This package implements circuit cutting. In this technique, a handful of gates and/or wires are cut, resulting in smaller circuits that are better suited for execution on hardware. The result of the original circuit can then be reconstructed; however, the trade-off is that the overall number of shots must be increased by a factor exponential in the number of cuts.
For a more detailed discussion on circuit cutting, check out our technical guide.
Documentation
All documentation is available at https://qiskit.github.io/qiskit-addon-cutting/.
Installation
We encourage installing this package via pip, when possible.
pip install 'qiskit-addon-cutting'
For information on installing from source, running in a container, and platform support, refer to the installation instructions in the documentation.
Deprecation Policy
We follow semantic versioning and are guided by the principles in Qiskit's deprecation policy. We may occasionally make breaking changes in order to improve the user experience. When possible, we will keep old interfaces and mark them as deprecated, as long as they can co-exist with the new ones. Each substantial improvement, breaking change, or deprecation will be documented in the release notes.
References
[1] Kosuke Mitarai, Keisuke Fujii, Constructing a virtual two-qubit gate by sampling single-qubit operations, New J. Phys. 23 023021.
[2] Kosuke Mitarai, Keisuke Fujii, Overhead for simulating a non-local channel with local channels by quasiprobability sampling, Quantum 5, 388 (2021).
[3] Christophe Piveteau, David Sutter, Circuit knitting with classical communication, arXiv:2205.00016 [quant-ph].
[4] Lukas Brenner, Christophe Piveteau, David Sutter, Optimal wire cutting with classical communication, arXiv:2302.03366 [quant-ph].
[5] K. Temme, S. Bravyi, and J. M. Gambetta, Error mitigation for short-depth quantum circuits, Physical Review Letters, 119(18), (2017).
License
Metadata
Release files for qiskit-addon-cutting 0.10.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 | |
|---|---|---|---|
| qiskit_addon_cutting-0.10.0.tar.gz | 739.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qiskit_addon_cutting-0.10.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 841.3 kB
Release files / qiskit_addon_cutting-0.10.0.tar.gz
| Download URL | qiskit_addon_cutting-0.10.0.tar.gz |
|---|---|
| Size | 739.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2970680a83224873af93f4a7063d425a323ace58e34d72ecfe043c015983cf52
|
|
BLAKE2b-256 checksum How to use checksums |
8440424d088b2ec8fd142170c45a77fe16702e50875c61825de369c8aeb0fe80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Mar 28, 2025.
Transparency logRelease files / qiskit_addon_cutting-0.10.0-py3-none-any.whl
| Download URL | qiskit_addon_cutting-0.10.0-py3-none-any.whl |
|---|---|
| Size | 101.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2e5e10a95d745addfc0b55e786428566ad31ee4667479d0a0d805a0525c416db
|
|
BLAKE2b-256 checksum How to use checksums |
52075fc32d7aa666c5f4645127fd51c140b15555a560264e5a4b74d0d9f1497d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Mar 28, 2025.
Transparency log