Qiskit Quantinuum Provider
Qiskit is an open-source framework for working with noisy quantum computers at the level of pulses, circuits, and algorithms.
This project contains a provider that allows access to Quantinuum quantum devices.
Installation
You can install the provider using pip:
pip3 install qiskit-quantinuum-provider
pip will handle installing all the python dependencies automatically and you
will always install the latest version.
Setting up the Quantinuum Provider
Once the package is installed, you can access the provider from Qiskit via the following import:
from qiskit_quantinuum import Quantinuum
You will need credentials for the Quantinuum Quantum Service. Credentials are tied to an e-mail address that can be stored on disk with:
Quantinuum.save_account('username@company.com')
After the initial saving of your account information, you will be prompted to enter your password which will be used to acquire a token that will enable continuous interaction until it expires. Your password will not be saved to disk and will be required infrequently to update the credentials stored on disk or when a new machine must be authenticated.
The credentials will then be loaded automatically on calls that return Backends, or can be manually loaded with:
Quantinuum.load_account()
This will load the most recently saved credentials from disk so that they can be provided for each interaction with Quantinuum's devices.
Storing a new account will not invalidate your other stored credentials. You may have an arbitrary number of credentials saved. To delete credentials you can use:
Quantinuum.delete_credentials()
Which will delete the current accounts credentials from the credential store. Please keep in mind this only deletes the current accounts credentials, and not all credentials stored.
With credentials loaded you can access the backends from the provider:
backends = Quantinuum.backends()
backend = Quantinuum.get_backend(device)
You can then use that backend like you would use any other qiskit backend. For example, running a bell state circuit:
from qiskit import *
qc = QuantumCircuit(2, 2)
qc.h(0)
qc.cx(0, 1)
qc.measure([0,1], [0,1])
result = execute(qc, backend).result()
print(result.get_counts(qc))
License
Metadata
Release files for qiskit-quantinuum-provider 0.4.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 | Actions |
|---|---|---|---|---|
| qiskit_quantinuum_provider-0.4.1.tar.gz | 25.7 kB | Without provenance | Details for qiskit_quantinuum_provider-0.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qiskit_quantinuum_provider-0.4.1-py3-none-any.whl | Python 3 | none | any | Details for qiskit_quantinuum_provider-0.4.1-py3-none-any.whl |
Total release size: 61.9 kB
Release files / qiskit_quantinuum_provider-0.4.1.tar.gz
| Download URL | qiskit_quantinuum_provider-0.4.1.tar.gz |
|---|---|
| Size | 25.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
423e2a43c9d4bb03acd8fe4313bcfce29badb63af29f00e989bf187537d5f521
|
|
BLAKE2b-256 checksum How to use checksums |
5446291a526d23682db5274ddee040a45bd35d6c7839a8ac0b27db6843030476
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.0 CPython/3.12.4
|
Release files / qiskit_quantinuum_provider-0.4.1-py3-none-any.whl
| Download URL | qiskit_quantinuum_provider-0.4.1-py3-none-any.whl |
|---|---|
| Size | 36.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
17242c39b2b9f2573a99ef0f8844fc78cd7fb05a05d505067778d2d3f85df3fb
|
|
BLAKE2b-256 checksum How to use checksums |
b6155f6cffca188b9273fb6219c23f77fb989b4ae17d7d5a1ded2a068a2cbd1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.0 CPython/3.12.4
|
Security for qiskit-quantinuum-provider 0.4.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.