dwave-inspector
A tool for visualizing problems submitted to, and answers received from, a D-Wave structured solver such as an AdvantageTM quantum computer.
This example shows a typical usage: a binary quadratic model minor-embedded onto a quantum processing unit (QPU).
from dwave.system import DWaveSampler, EmbeddingComposite
import dimod
import dwave.inspector
# Get sampler
sampler = EmbeddingComposite(DWaveSampler())
# Define a problem
x, y, z = dimod.Binaries(['x', 'y', 'z'])
bqm = x*y - x*z + 2*y
# Sample
sampleset = sampler.sample(bqm, num_reads=100)
# Inspect
dwave.inspector.show(sampleset)
Installation or Building
If Ocean SDK 2.0+ is installed:
dwave install inspector
Otherwise, install the package from PyPI:
pip install dwave-inspector
and then install the closed-source dependency with:
pip install dwave-inspectorapp --extra-index=https://pypi.dwavesys.com/simple
Please note this closed-source dependency is released under the D-Wave EULA license.
Alternatively, clone and build from source:
git clone https://github.com/dwavesystems/dwave-inspector.git
cd dwave-inspector
pip install -r requirements.txt
python setup.py install
When building from source, the closed-source component still needs to be installed as above.
License
Released under the Apache License 2.0. See LICENSE file.
Visualization component released under the D-Wave EULA.
Contributing
Ocean’s contributing guide has guidelines for contributing to Ocean packages.
Release Notes
D-Wave Inspector uses reno to manage its release notes.
When making a contribution to D-Wave Inspector that will affect users, create a new release note file by running:
reno new your-short-descriptor-here
You can then edit the file created under releasenotes/notes/. Remove any sections not relevant to your changes. Commit the file along with your changes.
See reno’s user guide for details.
Metadata
Release files for dwave-inspector 0.5.5
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 |
|---|---|---|---|---|
| dwave_inspector-0.5.5.tar.gz | 35.3 kB | Without provenance | Details for dwave_inspector-0.5.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dwave_inspector-0.5.5-py3-none-any.whl | Python 3 | none | any | Details for dwave_inspector-0.5.5-py3-none-any.whl |
Total release size: 65.8 kB
Release files / dwave_inspector-0.5.5.tar.gz
| Download URL | dwave_inspector-0.5.5.tar.gz |
|---|---|
| Size | 35.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb8273c72bdac907761d0f8c10b23ce516b6d2e5e7f608d5b168d17bccd1ce96
|
|
BLAKE2b-256 checksum How to use checksums |
f2582d5f02a4a44c6074bc3f82bf883bc6391cbfd40dfe7db3df3377e499d5a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Release files / dwave_inspector-0.5.5-py3-none-any.whl
| Download URL | dwave_inspector-0.5.5-py3-none-any.whl |
|---|---|
| Size | 30.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
77aff77948e8b61cce42ff5230a4cf9b7397cd55141055c559d7407c9e825d95
|
|
BLAKE2b-256 checksum How to use checksums |
2f93d5be9efd8403596ea022d0b9b748217b7ac12aeda3ea63e4ba0228f29dad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Security for dwave-inspector 0.5.5
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.