Nancon Transient NWT Basin Diagnostics

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 publishes one real Nancon watershed run from the standard 02_nancon_watershed example project. Unlike the more synthetic launcher demonstrations, it stays close to one observed basin and uses stable figures to connect simulated groundwater response with reference hydrography and catchment-scale discharge diagnostics.

See also

Read the results-pages reading guide if you want the parameter mapping, a recommended reading order, and the first modifications to try.

Reference versus generated hydrographic linework on the Nancon basin, used as the structural context before reading the simulated response.

Simulated active drainage cells overlaid with the observed reference hydrography, including cell-overlap metrics on the same map.

Piezometric map from the same transient NWT run, used to read the main groundwater-state structure after the network diagnostics.

Observed-versus-simulated hydrograph used to judge whether the basin-scale temporal response remains coherent over the transient window.

Integrated basin water-budget figure from the same run, used after the maps and hydrograph to interpret the balance of inflows and outflows.

Case Setup

• Base config: project.toml loads the offline Nancon basin data bundle, activates recharge, etp, and top drainage, and defines the default display contract.

• Overlay config: run_transient_nwt.toml selects the monthly 2000-2002 transient window, the modflow_nwt backend, the homogeneous K/Sy/Ss values, and the stable capability-gallery publication block.

• Execution chain: observed-basin setup -> transient MODFLOW-NWT flow -> catalog-backed figure rendering -> stable publication into examples/projects/09_capability_gallery/simulation_regression/nancon_transient_nwt/.

What It Shows

• How one project-scoped MODFLOW-NWT transient run turns monthly recharge, ETP, and top drainage into a basin hydrograph and integrated water budget.

• How the simulated active drainage pattern compares to the observed hydrographic network on the same basin support.

• How classical project figures and newer hydrographic-network diagnostics can be committed together as one stable documentation case.

How To Read It

• Start with the hydrographic-network comparison to separate reference linework from the generated structural network before reading any simulated response.

• Read the simulated active-network overlay next: it tells you where the transient groundwater response aligns with or departs from the observed hydrography.

• Open the piezometric map after that to read the groundwater-state structure behind the network pattern.

• Use the hydrograph and water-budget figures last, once the spatial context is already clear, so that you do not over-interpret one temporal mismatch without checking where it comes from spatially.

Next Steps

• Read the results-pages reading guide for a stricter interpretation order across committed basin-result pages.

• Read the Nancon scientific worked case if you want the exact ETP -> EVT package path and the MODFLOW-NWT option rationale behind this run.

Reproduce

Run the underlying example or validation case with:

python -m hydromodpy run examples/projects/02_nancon_watershed/run_transient_nwt.toml

Refresh the committed gallery artifacts with:

python -m tools.doc_gallery

Case Parameters

Selected Parameters

Field	Meaning	Value	Source
[simulation.time] start_datetime	Start of the simulated period used by the flow and transport run.	2000-01-01	examples/projects/02_nancon_watershed/run_transient_nwt.toml
[simulation.time] end_datetime	End of the simulated period used by the flow and transport run.	2002-12-31	examples/projects/02_nancon_watershed/run_transient_nwt.toml
[simulation.time] step_value	Nominal time step used to discretize the simulation period.	1 month	examples/projects/02_nancon_watershed/run_transient_nwt.toml
[flow.param.K.field] value	Homogeneous hydraulic conductivity used by the flow model in this tutorial run.	5e-05	examples/projects/02_nancon_watershed/run_transient_nwt.toml
[flow.param.Sy.field] value	Specific yield used to control the free-surface response of the aquifer.	0.05	examples/projects/02_nancon_watershed/run_transient_nwt.toml

Mesh and Output Selection

Field	Meaning	Value	Source
[capability_gallery] assets	Subset of run outputs copied into the static documentation gallery.	hydrographic_network_comparison.png, simulated_active_network_reference_overlay.png, piezometric_map.png, hydrograph.png, water_budget.png	examples/projects/02_nancon_watershed/run_transient_nwt.toml

Source Pointers

• examples/projects/02_nancon_watershed/project.toml

• examples/projects/02_nancon_watershed/run_transient_nwt.toml

• examples/projects/02_nancon_watershed/README.md

• examples/projects/09_capability_gallery/simulation_regression/nancon_transient_nwt/manifest.json

• hydromodpy/analysis/capability_gallery.py

• hydromodpy/display/figures/simulated_active_network.py

• hydromodpy/display/figures/hydrographic_network_comparison.py

Artifacts

• docs/source/_static/capability_gallery/simulation/nancon_transient_nwt_hydrographic_network_comparison.png

• docs/source/_static/capability_gallery/simulation/nancon_transient_nwt_simulated_active_network_reference_overlay.png

• docs/source/_static/capability_gallery/simulation/nancon_transient_nwt_piezometric_map.png

• docs/source/_static/capability_gallery/simulation/nancon_transient_nwt_hydrograph.png

• docs/source/_static/capability_gallery/simulation/nancon_transient_nwt_water_budget.png

• docs/source/_static/capability_gallery/simulation/nancon_transient_nwt_summary.json stores the displayed metrics plus source hashes used by python -m tools.doc_gallery --check.