wellbalanced
Global (0D) and 1D fluid models of low-temperature plasmas.
- Global model (
GlobalModel): the density of every species, the electron energy and optionally the gas temperature, balanced over the volume of a chamber. Reactions, ions leaving through the walls at the Bohm speed (with an edge-to-centre ratio) and through magnetic cusps (hybrid leak width), neutral wall reactions, gas feed and pumping, and volume sources such as a fast beam. Steady states in seconds, and scans that continue from one steady state to the next. - 1D fluid model (
Fluid1D): drift-diffusion of every species with Scharfetter-Gummel fluxes, the electron energy equation and Poisson’s equation, fully implicit. Walls, prescribed densities or fluxes at either end, changeable between steps, as the fluid side of a coupling to a particle code. - 2D axial-azimuthal drift fluid of a magnetron (
DriftFluid2D): magnetised electrons with the Hall tensor, inertial ions, neutral depletion and refill, the electron energy and a semi-implicit Poisson solve; the gradient-drift instability and spoke diagnostics (mode number, phase velocity against E x B, cathode modulation, potential hump). - A global model of the magnetron ionization region (
Magnetron,wellbalanced.magnetron): Ar and the sputtered metal, Bohm losses through the target with sputtering and self-sputtering, argon refill and sputter wind, driven by the discharge current and voltage of a pulse or of dc; it reports the argon rarefaction, the metal to argon ratio, the metal share of the ion flux and the self-sputtering share against the current. Yields and geometry are placeholders, not data. - The neutral gas of a magnetron (
GasDynamics,wellbalanced.gasdynamics): argon and the sputtered metal as one compressible gas in 1D or 2D (HLLC, species diffusion, heat conduction), with the sputter wind, the return of neutralized ions, ionization sinks, wall heat exchange and a refill reservoir as inputs a plasma model can update; the rarefaction that spokes depend on. The continuum limit, so Knudsen numbers near 1 need a kinetic check. - A beam-driven plasma neutralizer (
wellbalanced.neutralizer): a fast beam’s charge states on the gas and on the plasma it makes, coupled to a global model of the channel fed by the beam’s stripped and secondary electrons, iterated to a fixed point in seconds. - The data of the kinetic codes: rates come from plasmacoll’s cross sections averaged over a Maxwellian, the data its Monte Carlo collisions use, so a fluid and a kinetic model of the same plasma differ in their physics, not their data.
The name: a well-balanced scheme keeps the steady states of its equations exactly, and steady balances are what this code is for.
Documentation: https://max-models.github.io/wellbalanced/
Example
from plasmacoll import CrossSection
from plasmacoll.constants import ELECTRON_MASS
from wellbalanced import ELECTRON, Chamber, GlobalModel, Reaction, Species
argon, argon_ion = Species.atomic("Ar", 39.948), Species.atomic("Ar+", 39.948, 1)
ionization = Reaction.from_cross_section(
("e", "Ar"),
("e", "e", "Ar+"),
CrossSection.constant(2.0e-20, threshold=15.76),
ELECTRON_MASS,
electron_energy_loss=15.76,
)
model = GlobalModel(
species=[ELECTRON, argon, argon_ion],
reactions=[ionization],
chamber=Chamber(volume=1.0e-3, wall_area=0.06, h_factor=0.5),
power=100.0,
fixed={"Ar": 1.0e20},
)
state = model.steady_state()
print(state.electron_temperature, state.electron_density, state.power)
Install
With uv:
make install # uv sync --extra dev, plus the pre-commit hooks
Or with pip, in a Python environment (3.10 or newer):
pip install -e .
The test, docs and dev extras install the test runner, the
documentation tooling and the linters:
pip install -e ".[dev]"
Development
Formatting and linting use ruff, type checking pyright, run by pre-commit and in CI:
make lint # ruff check, ruff format --check, pyright
make test # pytest with coverage
Commit messages follow Conventional Commits; see CONTRIBUTING.md.
Build docs
The documentation in docs/ is an Astro + Starlight site: hand-written
pages, the notebooks in tutorials/ executed and published as pages,
complete Python scripts in examples/ published with their plots, and
the API reference generated from the docstrings with
starlight-pydocs. It needs
Node 22 or newer.
make docs-install # npm packages and the Python docs extra
make docs-notebooks # execute tutorials/*.ipynb and convert them to pages
make docs-examples # run examples/*.py and publish their plots
make docs-dev # live preview at http://localhost:4321/wellbalanced/
make docs-build # the static site in docs/dist
Build the README
README.md is rendered from README.qmd with
Quarto:
make readme
Releases
Before merging a release to main, update the version in
pyproject.toml, src/wellbalanced/__init__.py and CITATION.cff
(including its release date), and add the release notes to
CHANGELOG.md. The push to main creates a GitHub release with a
vX.Y.Z tag and publishes the package to PyPI with trusted publishing
(OIDC). The one-time PyPI and GitHub configuration is described in the
publishing
tutorial.
Metadata
Release files for wellbalanced 0.1.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 | |
|---|---|---|---|---|
| wellbalanced-0.1.0.tar.gz | 99.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wellbalanced-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 206.0 kB
Release files / wellbalanced-0.1.0.tar.gz
| Download URL | wellbalanced-0.1.0.tar.gz |
|---|---|
| Size | 99.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87284e5618e1a641bf0349ec4f603578a0dc41de79872ae68ce2a4bceadcd5a4
|
|
BLAKE2b-256 checksum How to use checksums |
6a8eef324a342ad6d455a0aa6a4c326bcb6f51372010b14de4fbe57c7085d250
|
| 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 20, 2026.
Transparency logRelease files / wellbalanced-0.1.0-py3-none-any.whl
| Download URL | wellbalanced-0.1.0-py3-none-any.whl |
|---|---|
| Size | 107.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
37786f007e95e72435648ea04c5dd751cb1c3428593ad54af58beb3a45ee50b9
|
|
BLAKE2b-256 checksum How to use checksums |
938bf1beb74ea76f0fa182dccb3db17c45791cb0f7776d8fe1515fa1cda05123
|
| 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 20, 2026.
Transparency logSecurity for wellbalanced 0.1.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for wellbalanced-0.1.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 Oct 20, 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.