No-Seepage Surface-Interaction Comparison#

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 page isolates the same synthetic hillslope after moving the surface well above the imposed east boundary head. The goal is to test whether the methods converge once seepage and surface overflow are intentionally removed from the physical picture.

  • Run source: out/sih_tx_4cmp_linux_no_seepage_20260415

  • Methods: MODFLOW-NWT, MODFLOW 6, MODFLOW 6 irregular triangles, Boussinesq local partition

  • Run source: out/sih_tx_4cmp_linux_no_seepage_kx8_20260416

  • Methods: MODFLOW-NWT, MODFLOW 6, MODFLOW 6 irregular triangles, Boussinesq local partition

Case Setup#

  • Same strip geometry and time stepping as the ramp benchmark, but the topography is lifted uniformly by 10 m while the imposed east head stays unchanged.

  • This keeps the groundwater system below the ground surface throughout the run and removes seepage/overflow from the intended physical regime.

  • The comparison therefore targets the subsurface transient response rather than the surface-partition closure.

What It Shows#

  • How total outflow collapses toward the east boundary when seepage is suppressed by construction.

  • How storage change compares once the surface-interaction mechanism is no longer the dominant difference.

  • How the same no-seepage setup behaves at reference and high hydraulic conductivity.

Key Parameters#

  • Topography offset = +10 m relative to the ramp benchmark.

  • Reference hydraulic conductivity scale = 0.2x the baseline strip conductivity.

  • Time step = 15 days, east imposed head unchanged, same recharge ramp and dry recovery chronology.

How To Read It#

  • If the top panel aligns much better than in the ramp case, the previous disagreement mainly came from seepage or surface-interaction closure.

  • Use the storage panel to check whether one method still keeps more water even after seepage is removed.

  • Use the conductivity tabs to check whether the agreement is robust when transmissivity is increased while the no-seepage geometry is kept unchanged.

Next Steps#

  • Compare this page with the ramp benchmark to isolate which disagreements are specifically tied to surface interaction.

  • Use the transient investigation outputs when you need the full solver budget and the decomposed outflow components.

Reproduce#

Run the underlying example or validation case with:

python tools/doc_gallery/generate_code_comparison_assets.py

Refresh the committed gallery artifacts with:

python -m tools.doc_gallery

Source Pointers#

  • tools/doc_gallery/manifests/code_comparison_cases.json

  • tools/investigate_surface_interaction_hillslope_transient.py

  • tools/doc_gallery/generate_code_comparison_assets.py

  • validation_cases/shared/boussinesq_budget.py

  • examples/projects/09_capability_gallery/code_comparison/surface_interaction_no_seepage/no_seepage_reference_k.png

  • examples/projects/09_capability_gallery/code_comparison/surface_interaction_no_seepage/no_seepage_reference_k.json

  • examples/projects/09_capability_gallery/code_comparison/surface_interaction_no_seepage/no_seepage_high_k.png

  • examples/projects/09_capability_gallery/code_comparison/surface_interaction_no_seepage/no_seepage_high_k.json

Artifacts#

  • docs/source/_static/capability_gallery/code_comparison/surface_interaction_no_seepage_configuration.png

  • docs/source/_static/capability_gallery/code_comparison/no_seepage_reference_k.png

  • docs/source/_static/capability_gallery/code_comparison/no_seepage_high_k.png

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