SEAMM Composite Plug-in
A SEAMM plug-in for composite methods: energies from recipes of ordinary calculations
Free software: BSD-3-Clause
Documentation: https://molssi-seamm.github.io/composite_step/index.html
Features
Composite methods as model chemistries, SEAMM:CMP@<recipe>, from recipes: short YAML files that say how the energy is made from ordinary calculations.
A small, checked language for combining the energies: basis-set extrapolations (inverse power, exponential HF, Schwenke), scaling and empirical terms.
Components are ordinary calculations with their own settings fingerprints, so the fragment store reuses them.
The shipped recipes r2SCAN-3c-HO and revDSD-r2SCAN-3c-HO, the Thermochemistry step’s quick and default presets.
Acknowledgements
This package was created with the molssi-seamm/cookiecutter-seamm-plugin tool, which is based on the excellent Cookiecutter.
Developed by the Molecular Sciences Software Institute (MolSSI), which receives funding from the National Science Foundation under award CHE-2136142.
History
- 2026.11.12.2 – Core-valence and relativistic corrections, and the tier-A recipes
Recipe components can be given their frozen core (named sets of frozen orbitals per element), a scalar-relativistic Hamiltonian with its nucleus model, and a decontracted basis, so recipes can add core-valence and scalar-relativistic corrections. A difference of two components must change one thing only, or the recipe is refused.
Three shipped recipes give accurate reference values after W4: CCSD(T)-F12 (H-Ar), CCSD(T) extrapolated from triple and quadruple zeta (H-Ar, Ga-Br), and the same with a decontracted relativistic correction for species with calcium. Their core-valence and relativistic corrections agree with W4’s to 0.13 and 0.01 kJ/mol on test reactions.
Components of one model chemistry with different settings are kept apart, in the job and the fragment store.
Needs orca-step 2026.11.12.1 or later for these settings.
- 2026.11.12.1 – Recipes that use the parts of an energy
Recipes can use the parts of a component’s energy: part(c, "name") for the HF energy, the CABS singles, the correlation energies and the triples that the program reports, and parts derived from them (the CCSD-F12 correlation, the scaled triples (T*), …). hf_part(c) is the HF energy and corr_part(c) the correlation alone, so a recipe can, for example, extrapolate the correlation energy and not the HF energy.
A recipe that splits an F12 calculation into HF and correlation must account for its CABS singles, and the HF parts of components with different references cannot be combined unless the recipe allows it; such recipes are refused when they are read.
A stored energy without the parts a recipe needs is computed again; parts are never derived.
- 2026.11.12 – Recipes that combine several calculations run in every step
A composite recipe that combines several calculations now runs wherever a model chemistry is used: the Energy step, the Thermochemistry step’s CBH approach, and the others that run model chemistries through seamm-exec’s Evaluator. Each component runs as one batch of its own program over all the structures, the cheapest first, with that program’s own memory and cores.
A structure that fails one component is not sent to the later ones, and its result names the component that failed.
Every result carries the composite record: the recipe’s fingerprint and every component’s settings fingerprint, in the same form whether the recipe has one component or several, and whether a component was computed or found in a store.
A user’s or a job’s own recipe (in a recipes directory of SEAMM’s data path) is found wherever its model chemistry runs.
Needs seamm-exec 2026.11.12 or later for recipes with several components.
- 2026.11.11 – First release: composite methods as model chemistries
Composite methods are described by recipes, short YAML files that say how the energy is made from ordinary calculations: the geometry and frequency level, single points at that geometry, and a formula that combines them, with basis-set extrapolations, scaling and empirical terms.
Every recipe is a model chemistry, SEAMM:CMP@<recipe>, for the steps that take one. Its components are ordinary calculations with their own settings fingerprints, so the fragment store reuses them.
The recipes r2SCAN-3c-HO and revDSD-r2SCAN-3c-HO are shipped; they are the Thermochemistry step’s quick and default presets.
The Composite step itself does nothing yet and is not offered in the editor.
Metadata
Release files for composite-step 2026.11.12.2
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 |
|---|---|---|---|---|
| composite_step-2026.11.12.2.tar.gz | 350.0 kB | Without provenance | Details for composite_step-2026.11.12.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| composite_step-2026.11.12.2-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for composite_step-2026.11.12.2-py2.py3-none-any.whl |
Total release size: 395.8 kB
Release files / composite_step-2026.11.12.2.tar.gz
| Download URL | composite_step-2026.11.12.2.tar.gz |
|---|---|
| Size | 350.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e6b9ce9b3e117c1afa71d3257c086766897e0c74abad8644ac2f14a95be94baa
|
|
BLAKE2b-256 checksum How to use checksums |
0cf83dabf9673c07feff7f5cab13ff447819cd4e3a4839e6c385370c55d951a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / composite_step-2026.11.12.2-py2.py3-none-any.whl
| Download URL | composite_step-2026.11.12.2-py2.py3-none-any.whl |
|---|---|
| Size | 45.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b753f945c3e52294d4d5315f0e72fd4efe8a9182aede95eab196e14ff8dec5f7
|
|
BLAKE2b-256 checksum How to use checksums |
0d25beac8e9f2da2f1df9f51f10abc259d39fd4531c625893bdcd7bcafc2e61b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for composite-step 2026.11.12.2
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.