Skip to main content

qia-check

Heuremen LLC · https://indahl.ai/qia

Checks on IBM Quantum calibration figures before a run and after it. Your files are opened read-only and never changed. Reports go to a separate folder. Run on saved files, the checker sends nothing anywhere. Only the --pull option contacts IBM, with your own saved account, and only when you run it. Python 3.9 or later, standard library only.

Install

pip install qia-check

For the --pull option, which saves the live record from IBM, add the optional IBM client:

pip install "qia-check[ibm]"

The tool is then the command qia-check. It is also importable as the module qia_check.

Before a run

  1. Save the record you are about to run under. This needs the IBM client (pip install "qia-check[ibm]") and a saved IBM Quantum account. Let the checker do it: qia-check before --pull ibm_kingston Or save it yourself with QiskitRuntimeService().backend('ibm_kingston').properties().to_dict() written out as JSON.
  2. Check it: qia-check before record.json --qubits 0,1,5 Flags: T1 or T2 measured more than 24 hours before the record's stamp, error values of exactly 0, T2 above 2 x T1, and T1 and T2 measured more than 24 hours apart.
  3. Read the Guards before the work: pip install faultsguards, then python -m faultsguards guards

After a run

  1. Save the record again after the run, into the same folder as the first. Keep reports in a different folder.
  2. qia-check after records/ --start 2026-11-01T12:00:00Z --end 2026-11-01T12:40:00Z --qubits 0,1,5 Times are UTC, written with Z or an offset. The report names the latest record in the folder stamped at or before the start, lists every newer record stamped up to the end, and shows each change in the T1, T2 and readout-error figures on your qubits from one record to the next. If IBM recalibrated between your last saved record and the run, the record in force is not in the folder, so save one right before you submit.
  3. Read your write-up against the Faults: python -m faultsguards faults

The rest of the QIA package

The full package adds the YO record reader, the same-job T1 and T2 measurement, the check block and the paper. It is at https://indahl.ai/qia/package

How this was tested

See TESTED.md in the source distribution, installed under share/doc/qia-check/, and published at https://indahl.ai/qia/package

Terms

Heuremen LLC permits anyone to run, copy and change the code in this package, for any purpose, with attribution to Heuremen LLC and https://indahl.ai/qia

Your results remain yours. The text and data follow LICENSE, and their use to train, fine-tune or build AI models is not permitted.

Metadata

Release files for qia-check 1.0.0

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

Source distribution (sdist)

Source distribution for qia-check 1.0.0
File Size Uploaded Provenance Actions
qia_check-1.0.0.tar.gz 8.6 kB Without provenance Details for qia_check-1.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for qia-check 1.0.0
File Interpreter ABI Platform Actions
qia_check-1.0.0-py3-none-any.whl Python 3 none any Details for qia_check-1.0.0-py3-none-any.whl

Total release size: 19.4 kB

Release files / qia_check-1.0.0.tar.gz

Download URL qia_check-1.0.0.tar.gz
Size 8.6 kB
Tags Source
SHA-256 checksum
How to use checksums
b9b8efa172aff90b2021222e22c30518cd3ff178e86c4ac99e3947b10a06ca43
BLAKE2b-256 checksum
How to use checksums
3da2989414cbd1431599f97d565ec63af0c1a40fb8c08bf7bd69acde3bd9e9c6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.13

Release files / qia_check-1.0.0-py3-none-any.whl

Download URL qia_check-1.0.0-py3-none-any.whl
Size 10.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
43a0cf7870c35e4f5a657a43f33aa3ca9a41690116475aac1f2d4cd9e8551304
BLAKE2b-256 checksum
How to use checksums
51ec07fb5b3b90b2f1262802e6e2361ad14fb08eacbbf7a458f60cb958298cf3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.13

Security for qia-check 1.0.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.

Release history Release notifications | RSS feed

This release

1.0.0 This release

2 release files No provenance

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