QCEngine
Documentation: GitHub Pages
Quantum chemistry program executor and IO standardizer (QCSchema) for quantum chemistry.
Example
A simple example of QCEngine's capabilities is as follows:
>>> import qcengine as qcng
>>> import qcelemental as qcel
>>> mol = qcel.models.v1.Molecule.from_data(""" # QCSchema v1 or v2
O 0.0 0.000 -0.129
H 0.0 -1.494 1.027
H 0.0 1.494 1.027
""")
>>> inp = qcel.models.v1.AtomicInput( # QCSchema v1
molecule=mol,
driver="energy",
model={"method": "SCF", "basis": "sto-3g"},
keywords={"scf_type": "df"}
)
>>> inp = qcel.models.v2.AtomicInput( # QCSchema v2
molecule=mol,
specification={
"driver": "energy",
"model": {"method": "SCF", "basis": "sto-3g"},
"keywords": {"scf_type": "df"}
})
These input specifications can be executed with the compute function along with a program specifier:
>>> ret = qcng.compute(inp, "psi4")
The results contain a complete record of the computation:
>>> ret.return_result
-74.45994963230625
>>> ret.properties.scf_dipole_moment
[0.0, 0.0, 0.6635967188869244]
>>> ret.provenance.cpu
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
See the documentation for more information.
License
BSD-3C. See the License File for more information.
Metadata
Release files for qcengine 0.52.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 |
|---|---|---|---|---|
| qcengine-0.52.0.tar.gz | 406.2 kB | With provenance | Details for qcengine-0.52.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qcengine-0.52.0-py3-none-any.whl | Python 3 | none | any | Details for qcengine-0.52.0-py3-none-any.whl |
Total release size: 800.1 kB
Release files / qcengine-0.52.0.tar.gz
| Download URL | qcengine-0.52.0.tar.gz |
|---|---|
| Size | 406.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2bdcc93d33a43a8b799f47d8152ec3b4ae02343e97da1ecb656d741c8ce930e8
|
|
BLAKE2b-256 checksum How to use checksums |
5d853431676f6862706e4b75eeac0571c3eb8c316e15ccca1a25108563118943
|
| 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 Oct 16, 2026.
Transparency logRelease files / qcengine-0.52.0-py3-none-any.whl
| Download URL | qcengine-0.52.0-py3-none-any.whl |
|---|---|
| Size | 393.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
231f3b4da63de3ae3315fa879a4de8a4bec4db330c9d539769e1975e406eedeb
|
|
BLAKE2b-256 checksum How to use checksums |
a29d4c445157e2bda3ebfcb971c111427f338f71ecbcc13d4627a9b1db534120
|
| 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 Oct 16, 2026.
Transparency logSecurity for qcengine 0.52.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 qcengine-0.52.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 Oct 16, 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.