Skip to main content

EigenBridge

There are two quantum solvers. VQD can return several eigenvalues; QAOA returns only the ground state.

VQD -> run_vqd_eigensolver(matrix, k, use_noise=false) -> lowest k eigenvalues (k defaults to all) QAOA -> run_qaoa_eigensolver(matrix, use_noise=false) -> ground state only

Uncertainties (uq_values / uq_vectors)

  • For every VQD/QAOA path (noiseless and noisy), at each final optimized circuit/state, uq_values[i] = sqrt(max(0, ⟨H²⟩ − ⟨H⟩²)), where ⟨H⟩ is the reported eigenvalue and ⟨H²⟩ comes from the same estimator on H @ H at the same parameters. This is the standard deviation of a single measurement of H in the prepared state (intrinsic quantum / variational residual variance). Exact eigenstates give σ ≈ 0; approximate ansatz states give nonzero σ even without noise.
  • uq_vectors uses the same layout as the returned eigenvectors (column i = mode i). For each physical basis index j, uq_vectors[j, i] = sqrt(p_j (1 − p_j)) where p_j = ⟨|j⟩⟨j|⟩ is evaluated with the same estimator / circuit / parameters as the energy (FakeManila when use_noise=true). This is the std of a single-shot computational-basis occupation measurement for component j. Caveat: it can be > 0 even for an exact delocalized eigenstate (unlike σ_H, which is 0 for exact energy eigenstates). It is not “distance to the classical eigenvector.” Unused eigenvector columns stay 0. Reported eigenvectors still come from the ideal statevector of the optimized circuit; only the UQ uses the estimator/noise path.
  • Non–power-of-2 dimensions pad to the next power of two and place penalty = max(1.0, Gershgorin row-sum bound) on unused diagonal entries so pad eigenvalues stay outside the original spectrum while avoiding the old 10× entry-scale inflation of ⟨H²⟩ on small problems.
  • Noisy VQD keeps exact statevector overlaps; only the energy / projector estimator uses FakeManila noise (demo). Expect worse eigenvalues, especially for higher states.

Unit tests check that reported uq_values / filled uq_vectors entries are finite and nonnegative (filled columns not identically zero on the demo matrix), and that on the demo 3×3 matrix the ground-state interval [⟨H⟩−σ, ⟨H⟩+σ] contains the classical ground eigenvalue for noisy paths. They do not require noisy eigenvalues to match the classical answer.

Release files for qharm-eigenbridge 0.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for qharm-eigenbridge 0.0.3
File Size Uploaded
qharm_eigenbridge-0.0.3.tar.gz 15.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for qharm-eigenbridge 0.0.3
File Interpreter ABI Platform
qharm_eigenbridge-0.0.3-py3-none-any.whl Python 3 none any Details

Total release size: 26.4 kB

Release files / qharm_eigenbridge-0.0.3.tar.gz

Download URL qharm_eigenbridge-0.0.3.tar.gz
Size 15.2 kB
Tags Source
SHA-256 checksum
How to use checksums
9c73a7cd67e2eec47ea1ede10dbcc47aa35c108cc2609158ca9a6f348af9b5c3
BLAKE2b-256 checksum
How to use checksums
196b08d4d644570b29471ac2af29062226ec942b920d1bdadf6de6c383424fc1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release files / qharm_eigenbridge-0.0.3-py3-none-any.whl

Download URL qharm_eigenbridge-0.0.3-py3-none-any.whl
Size 11.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
96e3c0bf3a4e90c017a78d94a4a5651921913fb6682b37492cb628a4f6f1156c
BLAKE2b-256 checksum
How to use checksums
f76239c2f342866ed210cd66a3559b95d1252e1b41e5f9ec1669f3e264449ff0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.0.3 This release

2 release files

0.0.2

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page