Headwater 100 km2 MF6 Transient Reference#
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.
This case reuses the committed 100 km2 outlet-2 triangular mesh instead of meshing at runtime. It exposes the reference three-year MODFLOW 6 replay used as the baseline for the newer realistic-scenario family, with a compact set of flow-state, support, and cumulative budget figures copied into the gallery.
See also
Read the Simulation walkthrough if you want the parameter mapping, a recommended reading order, and the first modifications to try.





Case Setup#
Static gallery manifest: the committed capability-gallery manifest records the published assets and their generation context.
The source run used a committed triangular mesh, the flow-only process chain, and common postprocess/display switches.
Execution chain: committed mesh_input bundle -> MODFLOW 6 transient flow -> postprocess rasters and synthesis figures -> gallery publication.
What It Shows#
How a committed mesh-input workflow differs from the runtime-meshed simulation pages.
How monthly synthetic recharge drives three years of cumulative recharge and discharge on a real basin support.
How the same run can surface both global synthesis figures and direct water-table maps without shipping the full solver workspace.
Key Parameters#
[mesh_input] mesh_path and bundle_dir lock the support to the versioned 100 km2 outlet-2 mesh, which makes this page a support-reuse workflow rather than a meshing example.
[simulation.time] start_datetime, end_datetime, and step_value define the three-year monthly replay window shown in the cumulative curves.
[[data.recharge.sources]] values, freq, and runoff_ratio define the synthetic forcing chronology that drives the transient response.
[flow.param.K.field], [flow.param.Sy.field], and [flow.param.Ss.field] are the main parameters to perturb when comparing this reference run against the more complex scenario overlays.
How To Read It#
Open the support overview first to verify that the run reused the committed mesh bundle and sampled the structural surfaces as expected.
Read the flow-state triptych next for the compact basin-wide synthesis, then use the direct water-table maps when you need one variable isolated.
Use the cumulative recharge/discharge panel last to judge whether the imposed forcing and the integrated basin response remain coherent over the three-year window.
Next Steps#
Read the simulation walkthrough for the general mapping between config sections and displayed figures.
Use the committed-mesh comparison pages in the simulation-comparison section when you want to compare this style of replay against other supports or solver families.
Reproduce#
Run the underlying example or validation case with:
python -m tools.doc_gallery
Refresh the committed gallery artifacts with:
python -m tools.doc_gallery
Source Pointers#
examples/projects/09_capability_gallery/README.mdexamples/projects/09_capability_gallery/simulation_regression/headwater_100km2_outlet_2_mf6_transient_reference/manifest.jsonhydromodpy/analysis/capability_gallery.py
Artifacts#
docs/source/_static/capability_gallery/simulation/headwater_100km2_outlet_2_mf6_transient_reference_flow_state_triptych.pngdocs/source/_static/capability_gallery/simulation/headwater_100km2_outlet_2_mf6_transient_reference_recharge_discharge_cumulative.pngdocs/source/_static/capability_gallery/simulation/headwater_100km2_outlet_2_mf6_transient_reference_watertable_elevation.pngdocs/source/_static/capability_gallery/simulation/headwater_100km2_outlet_2_mf6_transient_reference_watertable_depth.pngdocs/source/_static/capability_gallery/simulation/headwater_100km2_outlet_2_mf6_transient_reference_support_overview.pngdocs/source/_static/capability_gallery/simulation/headwater_100km2_outlet_2_mf6_transient_reference_summary.jsonstores the displayed metrics plus source hashes used bypython -m tools.doc_gallery --check.