qccompute
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
python -m pip install "qccompute[qccodec]" qcstore
qccompute alone is the runner, for programs that implement its protocol (pip install qccompute); the qccodec extra adds external programs (xtb, ORCA, Psi4, CREST, ...) and qcstore is the calculation store. Coming from 0.22? See the migration guide.
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; itsoutputis the failedProgramOutput, with partial results and logs. A list runs everything first, then raises oneqcdata.ProgramErrorsgroup whoseresultsholds every output in order.raise_exc=Falsereturns 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. - One thread count per calculation. Its
threadskeyword, else the runner's whole count; a list shares it, and nothing ever runs more threads than its runner has. For many calculations at once, setthreads(usually 1) on each. See Threads. - A share of the machine.
qccompute.computeandqccompute.sessionbelong to the default runner: every core and GPU this process may use (orOMP_NUM_THREADScores). ARunnerof your own takes a share and closes its worker processes when done:
with qccompute.Runner(threads=16, gpus=["0"], isolation="process") as runner:
outputs = runner.compute(inputs, timeout=3600)
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.0
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 |
|---|---|---|---|---|
| qccompute-0.23.0.tar.gz | 676.1 kB | With provenance | Details for qccompute-0.23.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qccompute-0.23.0-py3-none-any.whl | Python 3 | none | any | Details for qccompute-0.23.0-py3-none-any.whl |
Total release size: 769.7 kB
Release files / qccompute-0.23.0.tar.gz
| Download URL | qccompute-0.23.0.tar.gz |
|---|---|
| Size | 676.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dae9140cedcb26a7b8b50d7d890fa49e2814a76082726ead73750df211c6d300
|
|
BLAKE2b-256 checksum How to use checksums |
a9b2cd1756049afa5a65c237e76c078c4af0e2d5402f1c18af593b01d8089600
|
| 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 19, 2026.
Transparency logRelease files / qccompute-0.23.0-py3-none-any.whl
| Download URL | qccompute-0.23.0-py3-none-any.whl |
|---|---|
| Size | 93.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0352281696a2b2bb909e4d86392b6f46182a835a20be1d4574dfb47aae16eeac
|
|
BLAKE2b-256 checksum How to use checksums |
fbb9f5d722ffe20f89623bcce24068f91720853cc2d2f646f49a6def15e5a318
|
| 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 19, 2026.
Transparency logSecurity for qccompute 0.23.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for qccompute-0.23.0.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 19, 2026.
Transparency logA 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.