Cirq on IQM
The cirq-iqm package is deprecated and the GitHub repository has been archived. New versions of Cirq on IQM will be published as part of the iqm-client package and can be installed from public PyPI with pip install iqm-client[cirq]. See the latest documentation at https://docs.meetiqm.com/iqm-client/user_guide_cirq.html for more information. The source code is available as part of the iqm-client package and a public mirror of the source code is available at https://github.com/iqm-finland/sdk. For support, you can contact support@meetiqm.com.
Google Cirq adapter for IQM’s quantum architectures.
What is it good for?
Currently Cirq on IQM can
take an arbitrary quantum circuit created using Cirq or imported from an OpenQASM 2.0 file
map the circuit into an equivalent one compatible with the chosen IQM quantum architecture
optimize the circuit by commuting and merging gates
simulate the circuit using one of Cirq’s simulators
run the circuit on an IQM quantum computer
Installation
The recommended way is to install the distribution package cirq-iqm directly from the Python Package Index (PyPI):
$ pip install cirq-iqmDocumentation
The documentation of the latest Cirq on IQM release is available here.
Jump to our User guide for a quick introduction on how to use Cirq on IQM.
Take a look at the Jupyter notebook with examples: examples/usage.ipynb.
You can build documentation for any older version locally by cloning the Git repository, checking out the corresponding tag, and running the docs builder. For example, to build the documentation for version 12.2:
$ git clone git@github.com:iqm-finland/cirq-on-iqm.git
$ cd cirq-on-iqm
$ git checkout 12.2
$ tox run -e docstox run -e docs will build the documentation at ./build/sphinx/html. This command requires the tox,, sphinx and sphinx-book-theme Python packages (see the docs optional dependency in pyproject.toml); you can install the necessary packages with pip install -e ".[dev,docs]"
Copyright
Cirq on IQM is free software, released under the Apache License, version 2.0.
Copyright 2020–2024 Cirq on IQM developers.
1 maintainer
Metadata
1 maintainer
Release files for cirq-iqm 17.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 | Provenance | Actions |
|---|---|---|---|---|
| cirq_iqm-17.0.tar.gz | 235.7 kB | Without provenance | Details for cirq_iqm-17.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cirq_iqm-17.0-py3-none-any.whl | Python 3 | none | any | Details for cirq_iqm-17.0-py3-none-any.whl |
Total release size: 272.1 kB
Release files / cirq_iqm-17.0.tar.gz
| Download URL | cirq_iqm-17.0.tar.gz |
|---|---|
| Size | 235.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
35fd5ab192cfdd73e21f89cef87e7d8348bd75acc3660e85815922f3a21f8d63
|
|
BLAKE2b-256 checksum How to use checksums |
433867a9641b4387fa46d09a42e3adcc21c1b2dc14cbcf673f3cbdf4c2c870d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / cirq_iqm-17.0-py3-none-any.whl
| Download URL | cirq_iqm-17.0-py3-none-any.whl |
|---|---|
| Size | 36.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26dd670b9e06c5a5c62f70584e2d8451a1d9fbc51769a2092a74e0946eae7576
|
|
BLAKE2b-256 checksum How to use checksums |
5e25f31ed4f2ed452cfe666cb69b8920d04342505e41d72a24ada1c2a06b79b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for cirq-iqm 17.0
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.
