omnibias-ferminet
FermiNet bridge for the omnibias closed-form n-th derivative framework.
Install
pip install omnibias-ferminet
# Optional: pull in folx for the bit-stable Laplacian comparison test
pip install omnibias-ferminet[folx]
omnibias-ferminet depends on omnibias-core, omnibias-jax, and
jax>=0.4.30. It does not require a FermiNet installation to import
or to be unit-tested (mock log|psi| factories are provided for the bridge
contracts); a real FermiNet checkout is needed only at production VMC time.
What is in here
omnibias.ferminet.folx_compat:forward_laplacian,closed_form_forward_laplacian,laplacian_factory-- folx-API drop-ins so any FermiNet / DeepQMC code that imports fromfolxcan switch to omnibias's closed-form Laplacian by changing one import.omnibias.ferminet.integration: the production bridge -- envelope value / gradient / Hessian, optional one-body backflow, and themake_omnibias_envelope_local_kinetic_energyandmake_omnibias_tier2_local_kinetic_energyfactories that the upstream FermiNetlaplacian_methodswitch consumes.omnibias.ferminet.restricted: Tier-2 / Tier-2-full restricted FermiNet ansatz with end-to-end closed-form Laplacian (used to bring the bridge up before plugging into the upstream FermiNet checkpoint).tier2_grad_laplacian_log_psiexposes the gradient and Laplacian oflog|det M|separately (a bit-identical refactor of the kinetic path) so an additive correlation factor composes correctly.omnibias.ferminet.jastrow: closed-form symmetric Padé-Jastrow correlation factorexp(J)-- analytic value / gradient / Laplacian (jastrow_value_grad_laplacian) with physical e-e (1/2,1/4) and e-n (-Z) cusp slopes, plusjastrow_slater_local_kinetic_energycombining it with a Slater determinant (correct cross term in|grad log|psi||^2).omnibias.ferminet.multiblockandomnibias.ferminet.multiblock_integration: multi-block FermiNet primitives for Born-Oppenheimer / nuclear-Hessian work.
Public API (lazy)
from omnibias.ferminet.folx_compat import (
forward_laplacian, closed_form_forward_laplacian, laplacian_factory,
OmnibiasFwdLaplResult,
)
from omnibias.ferminet.integration import (
envelope_value_grad_hessian,
apply_optional_backflow,
make_omnibias_envelope_local_kinetic_energy,
make_omnibias_tier2_local_kinetic_energy,
)
from omnibias.ferminet.restricted import (
Tier2Params, Tier2SymParams,
tier2_log_abs_psi, tier2sym_log_abs_psi,
tier2_local_kinetic_energy, tier2sym_local_kinetic_energy,
)
The top-level omnibias.ferminet namespace deliberately does not
re-export these: importing the bridge is opt-in so the package stays
cheap to import in scripts that do not need FermiNet.
Contract
omnibias-ferminet produces a Laplacian that is bit-identical to
FermiNet's default autograd path on the closed-shell systems we have
validated (Be 4-electron 4-walker test in
the private release-validation archive
row R1: rel_err = 0.0 to ULP, vs folx <= 5.07e-15). This is a
bit-stable contract for the CPU deterministic forward path; on
stochastic GPU runs we hold to a 1-sigma reproducibility budget.
License
Apache-2.0. See LICENSE and ../../LICENSING.md.
You never need a commercial licence for this package.
Metadata
Release files for omnibias-ferminet 0.2.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 |
|---|---|---|---|---|
| omnibias_ferminet-0.2.0.tar.gz | 90.9 kB | With provenance | Details for omnibias_ferminet-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| omnibias_ferminet-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for omnibias_ferminet-0.2.0-py3-none-any.whl |
Total release size: 165.5 kB
Release files / omnibias_ferminet-0.2.0.tar.gz
| Download URL | omnibias_ferminet-0.2.0.tar.gz |
|---|---|
| Size | 90.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
38144d40f1777c58b3ecdd30e574e5a20bf221a7b3ee52241d217d79e108acc4
|
|
BLAKE2b-256 checksum How to use checksums |
00da8a4eb536c0d7e86dbfeec31789da719c83b01d4b6a50f11938119ddc0015
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Sep 13, 2026.
Transparency logRelease files / omnibias_ferminet-0.2.0-py3-none-any.whl
| Download URL | omnibias_ferminet-0.2.0-py3-none-any.whl |
|---|---|
| Size | 74.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
94c65a252344726936b94c0174636545be04043435b421e7bcc8a5b409154d1b
|
|
BLAKE2b-256 checksum How to use checksums |
6ae796a143c77a8fadae0436432b17aa8d2ec7abcd81afa1f7fe9bfb1ac2c2e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Sep 13, 2026.
Transparency logSecurity for omnibias-ferminet 0.2.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 omnibias_ferminet-0.2.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 Sep 13, 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.