This release is a pre-release and may not be stable for production use.
quapp-dwave-ocean
Quapp D-Wave Ocean library supporting Quapp Platform for Quantum Computing.
Overview
quapp-dwave-ocean provides providers, devices, factories, and async tasks to
run
Binary Quadratic Models (BQMs) via D-Wave Ocean within the Quapp Platform. It
supports
D-Wave system and hybrid devices as well as a QuaO quantum simulator, featuring
consistent context-rich logging, robust error handling, and standardized
project/workspace
headers for clean integration with backend services.
Features
- Provider and device factories for:
- D-Wave System devices
- D-Wave Hybrid devices
- Quapp D-Wave Ocean simulator
- Asynchronous circuit export to SVG (BQM visualization) with optional compression and upload.
- Consistent, instance-level logging across provider/device creation, job invocation, export, and fetching.
- Standardized project/workspace header handling for backend invocations.
- Improved error handling and diagnostics in critical paths (export, provider/device creation, job processing).
- Job fetching workflow encapsulated for clarity and maintainability.
Installation
Install via pip:
pip install quapp-dwave-ocean
Recently Changes Highlights
- chore: Bump a version to
0.0.1.dev2and updatequapp-commondependency to0.0.11.dev6 - refactor: Replace global logger usage with instance-level logging and enhance debug information across D-Wave Ocean modules
- feature: Create
DWaveOceanJobFetchingclass for managing job fetching logic in D-Wave Ocean backend - feature: Add
DWaveOceanCircuitExportTaskfor exporting and processing D-Wave Ocean circuit visualizations - refactor: Update import paths from
qapp_commontoquapp_commonfor consistency across modules
For detailed usage and API references, please refer to the in-code documentation or contact the maintainers.
Metadata
Release files for quapp-dwave-ocean 0.0.2.dev2
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 | |
|---|---|---|---|---|
| quapp_dwave_ocean-0.0.2.dev2.tar.gz | 21.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| quapp_dwave_ocean-0.0.2.dev2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 45.2 kB
Release files / quapp_dwave_ocean-0.0.2.dev2.tar.gz
| Download URL | quapp_dwave_ocean-0.0.2.dev2.tar.gz |
|---|---|
| Size | 21.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52359226ddf8920547ddb62cdbd8b7c0d0553e5ca30a50c562a097f5c8066ecb
|
|
BLAKE2b-256 checksum How to use checksums |
1c3e4638c991bf3756edb9c0917249315f7ed2b47b038ee732984a18ee8cdea3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.22
|
Release files / quapp_dwave_ocean-0.0.2.dev2-py3-none-any.whl
| Download URL | quapp_dwave_ocean-0.0.2.dev2-py3-none-any.whl |
|---|---|
| Size | 23.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec2f9e7d04913720f814485f1bb5ebc08610aec5c40380bd83a3698d6c1b6dad
|
|
BLAKE2b-256 checksum How to use checksums |
e06c34879abf59b16add48512d04556b56f23d8ed012fb5934839fad97c480b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.22
|
Security for quapp-dwave-ocean 0.0.2.dev2
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.