smeltery
A tiered screening funnel for biochemical systems that ranks only what it can resolve.
smeltery pushes candidate molecules (substitution analogues of a lead, for example) through successive tiers of increasingly expensive physics. At each tier it keeps the ones that are measurably better. It runs on the ferric quantum-chemistry engine.
What it does differently
- Compares differences, never totals. Total energies scale with molecular size, so ranking analogues of different formula by them is meaningless. smeltery ranks a paired ΔΔE against the parent compound instead, and refuses to rank totals across formulas.
- Pairs poses. Analogue pose i is built on parent pose i, so pose-to-pose noise cancels. In the example below this cuts the uncertainty 10–17×.
- Admits when it can't tell. If two candidates are inside each other's uncertainty, the cut reports a tie, or "unranked", instead of an order.
- Records provenance. Every run writes a JSON record with the exact ferric commit (read from the installed package's metadata), settings and an input digest.
Quickstart
Requires Python 3.11–3.12, uv, and ferric's build prerequisites (Rust, libint2, OpenBLAS; see ferric's README). uv builds ferric from source at a pinned commit.
uv sync --extra dev
OPENBLAS_NUM_THREADS=1 uv run pytest -q
OPENBLAS_NUM_THREADS=1 uv run python examples/mwe_benzoic.py
Example
examples/mwe_benzoic.py places benzoic acid and two para-substituted
analogues in a two-charge, arginine-like pocket. It builds six paired poses
and computes each pose's field interaction energy,
ΔE_int = E(in field) − E(vacuum), with RHF/STO-3G:
candidate formula paired ddE unpaired SEM
benzoic C7H6O2 +0.0000 ± 0.0000 kcal/mol -
4-F C7H5FO2 +1.8097 ± 0.0683 kcal/mol 1.2054
4-Cl C7H5ClO2 +5.0243 ± 0.1228 kcal/mol 1.1959
cut (keep=1, z=2): survivors=['4-F'] | groups: [['4-F'], ['4-Cl']]
Electron-withdrawing substituents weaken binding to the cationic pocket, and Cl > F follows their Hammett σp values.
Correctness checks
tests/test_anchors.py checks the trivial limits, where the machinery must do
nothing:
- A molecule paired with itself gives a ΔΔE of exactly 0.0 on every pose. The test also checks that the field is non-zero, so this check can't pass vacuously.
- An empty field gives exactly zero interaction.
- An analogue's core coordinates are copied verbatim from the parent pose.
- smeltery's Å→Bohr conversion is exactly the one ferric uses, so point charges and atoms share one frame.
Each check was mutation-tested: breaking the pose copy, ranking a total energy, or passing charges in Å each makes a test fail.
Status
This is an early working example. The tier protocol, the paired-ΔΔE funnel, the resolution-aware cut and the run record work end to end. Docking, a force-field tier and real receptor pockets are next.
License
Licensed under either of MIT or Apache-2.0, at your option.
Metadata
Release files for smeltery 0.0.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 |
|---|---|---|---|---|
| smeltery-0.0.1.tar.gz | 30.7 kB | With provenance | Details for smeltery-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| smeltery-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for smeltery-0.0.1-py3-none-any.whl |
Total release size: 47.7 kB
Release files / smeltery-0.0.1.tar.gz
| Download URL | smeltery-0.0.1.tar.gz |
|---|---|
| Size | 30.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25cb814fb9ce9074336347f0f1c6cf03f7991c33a37bfedd2110f50fce8d6fea
|
|
BLAKE2b-256 checksum How to use checksums |
4f05c4f1b22ade20a9774486bf574d8f9ad26bce3d11911cf7aa52da5f8a17d7
|
| 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 5, 2026.
Transparency logRelease files / smeltery-0.0.1-py3-none-any.whl
| Download URL | smeltery-0.0.1-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8897ea59246186d670150a9a91325c1a455576c0db5229235bf408c67cc27ae
|
|
BLAKE2b-256 checksum How to use checksums |
fe6f7f8db09cb0f3a6d2fed103295a5de0d118dc745013693d248c72634895b8
|
| 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 5, 2026.
Transparency logSecurity for smeltery 0.0.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for smeltery-0.0.1.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 5, 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.