[solver] SolverConfig

TOML section: [solver]

Pydantic model: SolverConfig defined in hydromodpy.solver.base.solver_config.

Source on GitHub

Configuration block defining the active groundwater solver engine.

The V1 TOML form is backend = { backend = "modflow6" } for a built-in backend, or backend = { backend = "custom", name = "x" } for a plugin-registered backend.

Show fields: User User + Dev All

Fields

backend in TOML: [solver.backend]

backend = “modflow6” | “modflow_nwt” | “boussinesq” | “custom” factory user source

Active flow backend selector (discriminated union).

Pick a tab below: setting backend selects the matching schema.

modflow6

TOML: [solver.backend] with backend = "modflow6" – model Modflow6Backend (set backend = "modflow6").

modflow_nwt

TOML: [solver.backend] with backend = "modflow_nwt" – model ModflowNwtBackend (set backend = "modflow_nwt").

boussinesq

TOML: [solver.backend] with backend = "boussinesq" – model BoussinesqBackend (set backend = "boussinesq").

custom

TOML: [solver.backend] with backend = "custom" – model CustomBackend (set backend = "custom").

name

str required user source

Plugin-registered flow backend name (matches registry).

Starter TOML snippet

Click to expand a copy-pasteable [solver] TOML skeleton

Copy this block into your project.toml and uncomment the lines you want to set. Sub-tables ([parent.subfield]) appear in the order Pydantic expects them.

[solver]

[solver.backend]
# backend = "modflow6"

Entity-relationship diagram

Click to zoom and pan. Press Esc or click outside to close.