seamm_bsse
An engine-agnostic library for N-fragment, charge-aware counterpoise (BSSE)
corrections: given a cluster + fragment assignment + per-fragment charge,
generate_job_specs produces the 2N + 1 job specs a full-cluster-basis
correction needs (the full cluster; each fragment in the full cluster basis
with the rest ghosted; each fragment alone in its own basis), and combine
assembles the 2N + 1 results into a counterpoise-corrected total energy and
gradient. validate_fragments checks a fragment list for overlapping atoms,
unsupported open-shell fragments, and consistency with a known cluster
charge/multiplicity.
No quantum chemistry, no engine-specific input/output handling -- that stays
in each engine's own SEAMM step. orca_step's BSSE sub-step is the first
consumer: it drives real ORCA jobs through this library's job specs and
combine(), generalizing what used to be a two-fragment, neutral-singlet-only
ORCA Compound-script correction to an arbitrary number of fragments with
independent per-fragment charge. Validated against real ORCA on water/FEC/EC
dimers (reproduces the old, trusted Compound-script numbers to SCF-noise
level), charged two-body ion/water pairs (Na+/Cl-, Na+/H2O, Cl-/H2O, agreeing
with approximate literature binding energies to a few kcal/mol), and a real
N = 3 Na+/Cl-/H2O trimer. A Psi4 sub-step is planned next, as a thin wrapper
around Psi4's own native bsse_type='cp' driver rather than a second consumer
of this library's job-spec/combine() path -- Psi4 already does its own
N-fragment CP orchestration internally, so wrapping it gives an independent
cross-check of the ORCA path instead of the same arithmetic run twice.
See docs/developer_guide/campaigns/2026-08-03/bsse_architecture.rst for the
full design: the physics, the confirmed ORCA ghost-indexing detail that makes
combine() padding-only, what changed in orca_step, the validation results,
and the milestone sequence.
Motivating plan: ~/Sites/mlff-training/2026-07-28_ion-bsse-plan/.
Metadata
Release files for seamm-bsse 2026.8.7.1
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 |
|---|---|---|---|---|
| seamm_bsse-2026.8.7.1.tar.gz | 18.3 kB | Without provenance | Details for seamm_bsse-2026.8.7.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| seamm_bsse-2026.8.7.1-py3-none-any.whl | Python 3 | none | any | Details for seamm_bsse-2026.8.7.1-py3-none-any.whl |
Total release size: 36.1 kB
Release files / seamm_bsse-2026.8.7.1.tar.gz
| Download URL | seamm_bsse-2026.8.7.1.tar.gz |
|---|---|
| Size | 18.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c83d194b2f45c79e39b52d704af44280a417853c515cc9a4e6c576bf91d56d8
|
|
BLAKE2b-256 checksum How to use checksums |
c2745d0a49e83bfcba1ef728af165553fbb80e90b65729d0e7e851d77f528cca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / seamm_bsse-2026.8.7.1-py3-none-any.whl
| Download URL | seamm_bsse-2026.8.7.1-py3-none-any.whl |
|---|---|
| Size | 17.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9fc0ea2652769767a82859b49ab55d3657c14b6070c7b2b37eccd0e4e81a0d62
|
|
BLAKE2b-256 checksum How to use checksums |
8de3c15592ae96786284861f4626330a84413da0412b429b8f31364c6f694563
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for seamm-bsse 2026.8.7.1
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.