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.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.11
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.11.tar.gz | 327.6 kB | Without provenance | Details for composite_step-2026.11.11.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| composite_step-2026.11.11-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for composite_step-2026.11.11-py2.py3-none-any.whl |
Total release size: 359.0 kB
Release files / composite_step-2026.11.11.tar.gz
| Download URL | composite_step-2026.11.11.tar.gz |
|---|---|
| Size | 327.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d02645e8d883b5f341c362fc4cc9d6c7883e5a39207de4d6133df676c80d718e
|
|
BLAKE2b-256 checksum How to use checksums |
754890b3ae9622b4dca1a98eb4de28d81b588f6f1ce60e7dfd48359f843ed816
|
| 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.11-py2.py3-none-any.whl
| Download URL | composite_step-2026.11.11-py2.py3-none-any.whl |
|---|---|
| Size | 31.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
fd9d2359fb1dc9fd959c422fcc5f7e495d72d480deaba14eb505af652d758583
|
|
BLAKE2b-256 checksum How to use checksums |
700f37e02bfa1980310da6f477558804f1806d61dd4fb2571b54d70c6042dbeb
|
| 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.11
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.