omnibias-jax
JAX backend for the omnibias closed-form n-th derivative framework.
Why this is fast
All numbers float64, identical answers to autodiff up to ≤ 10⁻¹⁵. Full
derivation in docs/complexity.md.
- Closed-form Laplacian overhead is
O(1)in input dimensionD— independent ofDbecause the reduction collapses the inner sum once. - At
D = 240, 68× faster thanjax.hessian+ trace and 63× less memory. - Iterated Laplacian
Δᵏis 480× faster than folx-nested atk = 3; folx-nested OOMs atk = 4while omnibias finishes in ~0.1 ms. - Bit-identical to
omnibias-torchandomnibias-kerasfor every(activation, order)pair.
Install
pip install omnibias-jax
omnibias-jax depends on omnibias-core (pure-Python math) and jax>=0.4.30.
What is in here
- The same closed-form derivative kernels as
omnibias-torch, written in JAX (jax.numpy) so they JIT-compile cleanly inside FermiNet, vmc_jax, DeepQMC, and similar stacks. Polynomial coefficients are imported fromomnibias-core, so a JAXsigma^(n)(z)is bit-identical to the torchsigma^(n)(z)for everyn(this is the contract validated bytests/test_cross_backend_parity.py). - A backend-specific activation dictionary registered via the same
ActivationSpecprotocol as torch (get_activation,list_activations,register_activation). neural_field_laplacian/neural_field_hessian/ family: closed-form Laplacian and full Hessian for a one-layer scalar fieldf(x) = b + sum_h c_h sigma(W_h . x + b_h)onR^D. These are the primitives the FermiNet bridge inomnibias-ferminetcalls when composing through coordinate transformations.- Born-Oppenheimer derivative kernels (
coulomb_potential,make_local_energy,make_bo_force,make_bo_hessian,vibrational_frequencies) used to build analytic nuclear Hessians of neural-VMC energies.
Public API
from omnibias.jax import (
JaxActivationSpec, get_activation, list_activations,
register_activation, is_registered,
neural_field_laplacian, neural_field_value_grad_hessian,
coulomb_potential, make_local_energy,
make_bo_force, make_bo_hessian, vibrational_frequencies,
BankSpec, init_bias_scan, bias_scan, init_multipack, multipack_apply,
)
The FermiNet bridge (folx-compatible API, Tier-2 restricted FermiNet,
multiblock primitives) lives in the separate omnibias-ferminet
package; importing omnibias.jax does not trigger a FermiNet import,
so the JAX core remains useful when FermiNet is absent.
Wave-1 twins: init_multipack / multipack_apply (01-01, shipped)
and init_bias_scan / bias_scan / BankSpec (01-02, shipped). Same honesty as the
torch modules: interior shift along w, gamma is not delta -> 0.
Shipped Wave-3 twins: Scan-Net (init_scan_net / scan_net_apply;
on-lattice equivariance; G4 leftover-recorded), Jet-KAN (init_jet_kan
/ jet_kan_apply; model-jet exactness, KA theorem does not justify; G2
leftover-recorded), equivariant scan (gaussian-family steering;
discrete C_L; G5 leftover-recorded), hierarchical_scan (1-D
offsets), and Hermite ladder (hermite_basis / ladder_apply;
Rodrigues reweight required; G4 leftover-recorded).
License
Apache-2.0. See LICENSE and ../../LICENSING.md.
You never need a commercial licence for this package.
Metadata
Release files for omnibias-jax 0.4.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_jax-0.4.0.tar.gz | 193.9 kB | With provenance | Details for omnibias_jax-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| omnibias_jax-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for omnibias_jax-0.4.0-py3-none-any.whl |
Total release size: 373.8 kB
Release files / omnibias_jax-0.4.0.tar.gz
| Download URL | omnibias_jax-0.4.0.tar.gz |
|---|---|
| Size | 193.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
14f2f90cb8c962b0557469e59aa6c92737629df77d90fc04d309cb27e4835969
|
|
BLAKE2b-256 checksum How to use checksums |
955c76a9c3d7aa4ee8f0eaab675de7d37b383613a785fc4f1a9ff51dd35fc202
|
| 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_jax-0.4.0-py3-none-any.whl
| Download URL | omnibias_jax-0.4.0-py3-none-any.whl |
|---|---|
| Size | 179.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
98ecf86926ab58a407315b61aea2fdcb5b352a11e89fa32a3aaa3fa0aa051c06
|
|
BLAKE2b-256 checksum How to use checksums |
9f25bd22d85057ff81e2feaff395481c208b33a1abbbaf8a409cdbaf749b416f
|
| 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-jax 0.4.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_jax-0.4.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.