Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

qccompute

image image image CI

Runs quantum chemistry programs on qcdata inputs: one input or many, in this process or in worker processes, with an optional calculation store. Every program, whether written in Python for the protocol or an external program brought in by qccodec, runs the same way.

Documentation: qccompute.docs.afh.org

Install

The new runner is in alpha. Install the alpha line with its matching packages pinned (a plain pip install qccompute resolves the previous stable release):

uv pip install --prerelease=allow "qcdata==0.24.0a2" "qccompute[qccodec]==0.23.0a1" "qcstore==0.1.0a1"

qccompute alone is the runner, for programs that implement its protocol; the qccodec extra adds external programs (xtb, ORCA, Psi4, CREST, ...) and qcstore is the calculation store.

One way to run things

import qccompute
from qcdata import CalcType, Model, ProgramInput, Structure

water = Structure(
    symbols=["O", "H", "H"],
    geometry=[[0.0, 0.0, 0.0], [0.524, 1.687, 0.48], [1.146, -0.45, -1.354]],  # bohr
)
inp = ProgramInput(
    program="xtb", calctype=CalcType.gradient, structure=water, model=Model(method="gfn2")
)

out = qccompute.compute(inp)                 # one input -> ProgramOutput
outs = qccompute.compute([inp] * 8)          # a list runs side by side -> list
future = qccompute.submit(inp)               # start one -> Future of its output
with qccompute.session(inp) as s:            # one molecule at many geometries
    frame = s.compute(water.geometry * 1.01)
  • Failures raise. A failed calculation raises qcdata.ProgramError; its output is the failed ProgramOutput, with partial results and logs. A list runs everything first, then raises one qcdata.ProgramErrors group whose results holds every output in order. raise_exc=False returns failures in place.
  • A store, if you want one. compute(inputs, store=store, tags=[...]) looks each input up first and stores what it ran, with the identities of the programs that made it; a run is reused only when those are the programs that would run now.
  • Threads per calculation. Each calculation gets the threads it asks for: its threads keyword, else its program's plan (1 unless the program states more, or all of the runner's for a program that scales), at most the runner's.
  • A share of the machine. qccompute.compute and qccompute.session belong to the default runner: every core and GPU this process may use. A Runner of your own takes a share and closes its worker processes when done:
with qccompute.Runner(threads=16, gpus=["0"], isolation="process") as runner:
    for out in runner.as_completed(inputs, timeout=3600):
        print(out.success, out.results.energy)

Programs

A program is any object with name, version(), capabilities(), settings_schema(), record_schema(), plan(inp) and compute(inp, ctx=None), registered under the qccompute.programs entry points (or with qccompute.register_program in a script). The protocol is structural, so a program without subprograms imports only qcdata. qccompute.program.FunctionProgram turns Python functions of the positions into a program, and qccompute.testing.check_program checks one against the contract.

from qccompute.program import FunctionProgram

def harmonic(x):  # positions (bohr) -> energy (Eh), gradient (Eh/bohr)
    return float((x**2).sum()), 2 * x

qccompute.register_program(FunctionProgram("harmonic", harmonic))

The QC Suite

  • qcref - Reference data: physical constants, conversion factors, a periodic table, solvents, each value with its source.
  • qcdata - Data structures for quantum chemistry inputs and results. Documentation
  • qcinf - Cheminformatics algorithms and structure utilities for qcdata structures.
  • qccodec - External programs as programs qccompute runs: their input files, output parsers, and execution. Documentation
  • qccompute - Runs programs on qcdata inputs. Documentation

Support

Questions and bug reports: GitHub issues.

Metadata

Release files for qccompute 0.23.0a5

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

Source distribution (sdist)

Source distribution for qccompute 0.23.0a5
File Size Uploaded Provenance Actions
qccompute-0.23.0a5.tar.gz 642.1 kB With provenance Details for qccompute-0.23.0a5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for qccompute 0.23.0a5
File Interpreter ABI Platform Actions
qccompute-0.23.0a5-py3-none-any.whl Python 3 none any Details for qccompute-0.23.0a5-py3-none-any.whl

Total release size: 721.6 kB

Release files / qccompute-0.23.0a5.tar.gz

Download URL qccompute-0.23.0a5.tar.gz
Size 642.1 kB
Tags Source
SHA-256 checksum
How to use checksums
f390b9fe8f221772c67f12ebdd2d855a3e961e275ba4a69acbf857e7e4c5d215
BLAKE2b-256 checksum
How to use checksums
01652db115d10e1e6ca73f1d60d17d0ac151f6d58ec3f362ade623cd004eb9a7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 17, 2026.

Transparency log

Release files / qccompute-0.23.0a5-py3-none-any.whl

Download URL qccompute-0.23.0a5-py3-none-any.whl
Size 79.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a2eb8764e04ed7c2b9951b27453c8c9c260ad742736bc9d753fe4eac5a01bec3
BLAKE2b-256 checksum
How to use checksums
b003310ac6766e21a578f75d9810803abc9e6e2933a70fa6ac8d3027890522f6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 17, 2026.

Transparency log

Security for qccompute 0.23.0a5

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for qccompute-0.23.0a5.tar.gz

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 Nov 17, 2026.

Transparency log

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.

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