Simulation Workflows#
Note
This page and its static assets are auto-generated by python -m tools.doc_gallery. The Sphinx build only reads committed PNG and JSON artifacts.
These cases show complete launcher workflows: preprocessing, solver execution, transport when relevant, and the compact figures used to inspect the result.
See also
Read Simulation walkthrough if you want a guided entry point before opening the case pages below.
Current Coverage#
Study areas: Brittany regional laboratory, Headwater 100 km2 outlet 2, Naizin catchment, Nancon watershed.
Process families shown: Comparison, Display, Flow, Observed hydrography diagnostics, Planning, Postprocess, Reporting, Simulation, Transport.
Mesh supports: Committed Triangular Mesh Input, Project Scoped basin support, Runtime Gmsh Triangular Mesh.
Flow solvers: MODFLOW 6, MODFLOW-NWT.
Transport solvers: MODFLOW 6 GWT.
Postprocess outputs surfaced: Coverage Gap Summary, Flow State Triptych, Hydrograph, Hydrographic network comparison, Piezometric map, Recharge Discharge Cumulative, Recipe Coverage Summary, Simulated active network overlay, Site Recipe Matrix, Support Overview, Water budget, Watertable Depth, Watertable Elevation.
Workflow families: Runtime Mesh Build (1), Committed Mesh Replays (1), Observed Basin Diagnostics (1), Regional Orchestration (4).
Grow this category by workflow family rather than by one flat list of runs; add new pages where the reading objective really changes.
Workflow Families#
The cases below are grouped by workflow role so the simulation section can grow without turning into one long undifferentiated card wall.
Runtime Mesh Build#
These cases build the spatial support during the run, then surface the minimum set of solver and postprocess figures needed to understand what the runtime pipeline produced.
MODFLOW 6 on a Gmsh Catchment Mesh
End-to-end launcher run with embedded Gmsh meshing, MODFLOW 6 flow, and GWT transport.
Committed Mesh Replays#
These cases keep the spatial support fixed and focus on how forcing, hydraulic parameters, and solver settings shape the replay on an already versioned basin mesh.
Headwater 100 km2 MF6 Transient Reference
Committed-mesh MODFLOW 6 replay on the 100 km2 outlet-2 basin, published as stable transient postprocess figures.
Observed Basin Diagnostics#
These cases stay close to one observed basin and use stable figures to connect solver response, reference hydrography, and integrated basin diagnostics.
Nancon Transient NWT Basin Diagnostics
Observed-basin transient MODFLOW-NWT run with stable figures linking hydrography diagnostics, groundwater state, hydrograph, and basin budget.
Regional Orchestration#
These cases do not focus on one child solver run. They document how one population of sites and reusable recipes expands into a coordinated study plan.
Regional Lab Dry Plan on Headwater 100 km2
Dry-run orchestration example showing how one regional site catalog expands into simulation and comparison recipes.
Regional Lab MF6 Reference Recipe on Headwater 100 km2
Recipe-focused orchestration view isolating the committed MF6 replay workflow across the selected headwater population.
Regional Lab Backend Comparison Recipe on Headwater 100 km2
Recipe-focused orchestration view isolating the committed backend-comparison workflow across the headwater screening population.
Regional Lab Transient Backend Comparison Recipe on Headwater 100 km2
Recipe-focused orchestration view isolating the transient pulsed-recharge backend-comparison workflow across the committed headwater population.