Q-CTRL Qiskit Adaptor
The aim of the Q-CTRL Qiskit Adaptor package is to provide export functions allowing users to deploy established error-robust quantum control protocols from the open literature and defined in Q-CTRL Open Controls on IBM Quantum hardware.
Anyone interested in quantum control is welcome to contribute to this project.
Table of Contents
Installation
Q-CTRL Qiskit Adaptor can be installed through pip or from source. We recommend
the pip distribution to get the most recent stable release. If you want the
latest features then install from source.
Requirements
To use Q-CTRL Qiskit Adaptor you will need an installation of Python. We recommend using the Anaconda distribution of Python. Anaconda includes standard numerical and scientific Python packages which are optimally compiled for your machine. Follow the Anaconda Installation instructions and consult the Anaconda User guide to get started.
We use interactive jupyter notebooks for our usage examples. The Anaconda python distribution comes with editors for these files, or you can install the jupyter notebook editor on its own.
Using PyPi
Use pip to install the latest version of Q-CTRL Qiskit Adaptor.
pip install qctrl-qiskit
From Source
The source code is hosted on Github. The repository can be cloned using
git clone git@github.com:qctrl/python-qiskit.git
Once the clone is complete, you have two options:
-
Using setup.py
cd python-qiskit python setup.py develop
Note: We recommend installing using
developto point your installation at the source code in the directory where you cloned the repository. -
Using Poetry
cd python-qiskit ./setup-poetry.sh
Note: if you are on Windows, you'll need to install Poetry manually, and use:
cd python-qiskit poetry install
Once installed via one of the above methods, test your installation by running
pytest
in the python-qiskit directory.
pytest
Usage
See the Jupyter notebooks.
Contributing
For general guidelines, see Contributing.
Building documentation
Documentation generation relies on Spinx. Automated builds are done by Read The Docs.
To build locally:
-
Ensure you have used one of the install options above.
-
Execute the make file from the docs directory:
If using Poetry:
cd docs poetry run make html
If using setuptools:
cd docs # Activate your virtual environment if required make html
The generated HTML will appear in the docs/_build/html directory.
Credits
See Contributors.
License
See LICENSE.
Metadata
Release files for qctrl-qiskit 0.0.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 | Provenance | |
|---|---|---|---|---|
| qctrl-qiskit-0.0.1.tar.gz | 10.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qctrl_qiskit-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.5 kB
Release files / qctrl-qiskit-0.0.1.tar.gz
| Download URL | qctrl-qiskit-0.0.1.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fcb85324ccd2469c96a904c7ee8c7a240417dab9836b9489795b2e78f37467d8
|
|
BLAKE2b-256 checksum How to use checksums |
c85f7f67039d32dbd0d2691f280df34b03e6e77e05d6630c0addf7e1aac55be7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.0b4 CPython/3.7.4 Linux/5.0.0-1023-azure
|
Release files / qctrl_qiskit-0.0.1-py3-none-any.whl
| Download URL | qctrl_qiskit-0.0.1-py3-none-any.whl |
|---|---|
| Size | 10.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ce21ee32d3447f0c7399f7463744bbcb4e20ad3c6ec753e330f52d4ada70dc00
|
|
BLAKE2b-256 checksum How to use checksums |
634f3ad9b54602fedfc99540d84f6d1a4114b85d4141a6284e9330cc4251603b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.0b4 CPython/3.7.4 Linux/5.0.0-1023-azure
|
Security for qctrl-qiskit 0.0.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.