Skip to main content

Otter

Otter calculates electronic and ionic structure in warm and hot dense matter. From composition, mass density, and temperature it can solve a quantum average-atom or Thomas–Fermi model, construct neutral pseudoatoms, build effective ion–ion potentials, and solve one- or multicomponent QOZ/HNC equations.

Otter is based primarily on the pseudoatom model of Starrett and Saumon (2014).

Capabilities

  • finite-temperature quantum (KS-DFT, QM) and Thomas–Fermi (TF) electronic structure; the QM model provides orbital levels, occupations, and density components;
  • pseudoatom densities n_pa(r) and screening densities n_scr(r), with form factors f(k)=n_ion(k) and q(k)=n_scr(k);
  • effective ion–ion potentials V_ij(r) and V_ij(k);
  • one- and multicomponent QOZ/HNC results g_ij(r) and S_ij(k).

Install

Otter uses a reproducible editable installation from source. It requires CPython 3.12 or newer, Git, and Poetry 2.1.3.

macOS, Linux, or WSL:

curl -sSL https://install.python-poetry.org | python3 - --version 2.1.3

Windows PowerShell:

(Invoke-WebRequest -Uri https://install.python-poetry.org -UseBasicParsing).Content | py - --version 2.1.3

Verify the installation:

poetry --version

Clone and install:

git clone https://github.com/otter-hed/otter.git
cd otter
poetry install

Dependencies are locked by poetry.lock; Otter is installed in editable mode.

Otter's built-in local-density Dirac exchange is the dependency-free default used by the validated warm- and hot-dense-matter workflows. Libxc is optional and is needed only for additional LDA correlation or GGA functionals such as lda_pw, lda_pz, lda_vwn, and pbe.

To enable these additional functionals:

poetry install --extras libxc

PyPI distributes the Libxc Python bindings as source, so this optional step requires CMake and a C compiler. See the XC installation guide.

poetry run python -c "import otter; print(otter.__version__)"

Quick start

Run an introductory calculation in Google Colab:

Open In Colab

Run the complete single-species workflow from the repository root:

poetry run python examples/single_species_workflow.py

The default state is Al at rho=8.1 g/cm^3 and Te=Ti=15 eV. Edit the input block to change the state or output controls. The script plots the electronic density, effective potential, g_ii(r), and S_ii(k), and saves PNG, PDF, and NPZ files.

For mixtures, run mixture_workflow.py.

Saved workflow state

The versioned NPZ schema stores units and convergence metadata together with the selected scientific quantities. The default complete profile retains native electronic profiles and levels, q/f, electron response and LFC, interaction channels, and g_ij/S_ij. The smaller electronic_summary profile includes compact bound levels; ion_structure retains f/q/g/S. Optional groups add quantities such as chi_ee_k without requiring a complete export. Existing state schemas remain readable. In a complete archive:

  • q_k == n_scr_k and f_k == n_ion_k;
  • G_ee_k, chi0_k, chi_ee_k, v_ie_k, c_ie_k, v_ee_k, and c_ee_k;
  • gij_r, sij_k, vij_r, and vij_k.

gee_k and g_ee_k are temporary compatibility aliases for G_ee_k.

The default windows are r < 20 Bohr and k < 20 Bohr^-1. Archives load with allow_pickle=False and are written atomically. See the state-export guide for in-memory and NPZ access.

Quantum continuum calculations can be slow near pressure ionization. continue_plasma_workflow_from_electronic_result reuses a validated electronic result for subsequent QOZ/HNC calculations.

Validation and documentation

Browse the documentation, example gallery, and scientific benchmarks.

Examples and benchmarks calculate from their input parameters. From the repository root, for example:

poetry run python docs/examples/plot_al_full_workflow.py
poetry run python benchmarks/examples/plot_doppner_2023_be_ionization.py

The current source tree does not include precomputed Otter NPZ files. Scripts write new results locally; literature reference data and recorded website figures, tables, and terminal output remain included. MD comparisons require LAMMPS/MPI and first calculate the Otter pair potentials. See the reproduction guide for each page's commands, optional dependencies, and download formats.

Build the documentation, including its recorded example and benchmark results:

poetry install
poetry run make -C docs strict

This build does not run AA or MD calculations. Open docs/build/html/index.html after the build. Start with:

Digitized publication curves and author-provided numerical data have separate provenance and rights manifests; they are not covered by Otter's BSD software license unless a dataset explicitly says otherwise. The current bundled reference sets are published by maintainer decision with source attribution and license status NOASSERTION. Read the reference-data notice before reuse. The executable gate poetry run python tools/check_public_release.py rejects any future manifest that reintroduces an unresolved public-release action.

Development

poetry install
poetry run pytest -q
poetry run make -C docs strict
poetry run python -m build
poetry run python -m twine check dist/*

Anyone interested in Otter is welcome to contribute. See CONTRIBUTING.md for numerical and benchmark review requirements and CHANGELOG.md for user-visible changes.

Citation

If you use Otter in a scientific publication, please cite:

Chongbing Qu and Dominik Kraus, Otter, version 0.3.0, computer software (2026), https://github.com/otter-hed/otter.

@misc{QuKraus2026Otter,
  author  = {Qu, Chongbing and Kraus, Dominik},
  title   = {Otter},
  year    = {2026},
  note    = {Computer software, version 0.3.0},
  url     = {https://github.com/otter-hed/otter}
}

The same metadata are available in CITATION.cff. Otter is also available through GitHub's Cite this repository menu. Runtime configuration objects provide config.citation(style="plain"|"bibtex"|"cite") and expose their canonical citation_keys as scientific provenance for selected physical models; these are not additional software-citation requirements. See CITATIONS.md.

Acknowledgements

The authors thank Zachary A. Johnson and C. E. Starrett for helpful discussions.

Chongbing Qu gratefully acknowledges financial support from HEDI and the China Scholarship Council (CSC).

Otter is distributed under the BSD 3-Clause License.

Metadata

Release files for otter-hed 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for otter-hed 0.3.0
File Size Uploaded
otter_hed-0.3.0.tar.gz 378.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for otter-hed 0.3.0
File Interpreter ABI Platform
otter_hed-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 765.7 kB

Release files / otter_hed-0.3.0.tar.gz

Download URL otter_hed-0.3.0.tar.gz
Size 378.5 kB
Tags Source
SHA-256 checksum
How to use checksums
4ef224a46df2e30e5f41d062ede17d896f46f78d34f5e328989deb5a5362cea5
BLAKE2b-256 checksum
How to use checksums
285b54ecb0096b0a342928b331862c6cef64196a51d77f9bcea14e56fdb78f10
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 Sep 10, 2026.

Transparency log

Release files / otter_hed-0.3.0-py3-none-any.whl

Download URL otter_hed-0.3.0-py3-none-any.whl
Size 387.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f132212ff4d2515060f711164dcfa1f7728cc6e947f9d6b52248d176a1c7ee36
BLAKE2b-256 checksum
How to use checksums
57dbfa63c1cae0edc95c19cb1681f52dfd700206875d82cf7b958af890eeea71
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 Sep 10, 2026.

Transparency log

Release history Release notifications | RSS feed

0.3.1

2 release files

This release

0.3.0 This release

2 release files

0.2.2

2 release files

0.2.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page