QICK: Quantum Instrumentation Control Kit
QICK is an open-source qubit controller, consisting of firmware, software, and an optional frontend for use with Xilinx RFSoC development boards. The goal of the project is to provide a powerful, flexible, cost-effective, and easy-to-learn platform for control and readout of a diverse range of quantum systems.
QICK supports the ZCU111, ZCU216, and RFSoC4x2 development boards. We generally recommend using the newer generation of RFSoCs (ZCU216 and RFSoC4x2) for better overall performance.
It consists of:
- Firmware for the supported RFSoC boards, both compiled bitstreams and source for the designs and modules
- The
qickPython package, which includes the interface to the firmware and an API for writing QICK programs - Jupyter notebooks demonstrating usage
See our Read the Docs site for:
- Documentation of the firmware and software
- A quick-start guide for setting up your board and running the example Jupyter notebooks
- Ways to communicate with QICK developers and the community
- Extensions to QICK for added functionailty
Updates
The QICK firmware and software is still very much a work in progress. We strive to be consistent with the APIs but cannot guarantee backwards compatibility.
Frequent updates to the QICK firmware and software are made as pull requests. Each pull request will be documented with a description of the notable changes, including any changes that will require you to change your code. We hope that this will help you decide whether or not to update your local code to the latest version. We strive for, but cannot guarantee, bug-free and fully functional pull requests. We also do not guarantee that the demo notebooks will keep pace with every pull request, though we make an effort to update the demos after major API changes.
Our version numbering follows the format major.minor.PR, where PR is the number of the most recently merged pull request. This will result in the PR number often skipping values, and occasionally decreasing. The tagged release of a new minor version will have the format major.minor.0.
Tagged releases can be expected periodically. We recommend that everyone should be using at least the most recent release. We guarantee the following for releases:
- The demo notebooks will be compatible with the QICK library, and will follow our current best recommendations for writing QICK programs.
- The firmware images for all supported boards will be fully compatible with the library and the demo notebooks.
- Release notes will summarize the pull request notes and explain both breaking API changes (what you need to change in your code) and improvements (why you should move to the new release).
We recommend that you "watch" this repository on GitHub to get automatic notifications of pull requests and releases.
Contribute
You are welcome to contribute to QICK development by forking this repository and sending pull requests.
All contributions are expected to be consistent with PEP 8 -- Style Guide for Python Code.
We welcome bug reports and feature requests via GitHub Issues.
License
The QICK source code is licensed under the MIT license, which you can find in the LICENSE file. You are free to use QICK, with or without modification, under the terms of this license.
The QICK logo was designed by Dr. Christie Chiu.
Open-Source Commitment
QICK is and will remain a fully open-source project under the MIT license. Commercial partnerships or integration agreements with third-party companies do not change the licensing, governance, or availability of this project. All QICK source code, including firmware, software, and documentation, will continue to be freely available in this repository, and the QICK developers will continue to support the community. If you have questions or concerns, please don't hesitate to reach out.
1 maintainer
Metadata
1 maintainer
Release files for qick 0.2.431
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| qick-0.2.431.tar.gz | 16.7 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qick-0.2.431-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.9 MB
Release files / qick-0.2.431.tar.gz
| Download URL | qick-0.2.431.tar.gz |
|---|---|
| Size | 16.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
768e1d1f5fc6bb335e31b137246719784fe7a9246af8a4cffa3b4cc838830468
|
|
BLAKE2b-256 checksum How to use checksums |
6b93e0882f7fa02f24cc4eb7d424b93031471777a2d52029b101c57615a0ce5b
|
| 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 12, 2026.
Transparency logRelease files / qick-0.2.431-py3-none-any.whl
| Download URL | qick-0.2.431-py3-none-any.whl |
|---|---|
| Size | 17.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b4efa34750404e968d977fb2fbcbf1af9842152ec108b182c0342c0e9b365083
|
|
BLAKE2b-256 checksum How to use checksums |
6392f22baf60ac1aa2d04fcbec6e90b288cadf45d61bb92155a26e80c0b7c97e
|
| 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 12, 2026.
Transparency log
