Four-Simulation Moderate Suite with Surface-Excess 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 keeps the same four simulations as the moderate suite but adds observables that only make sense for the triangular/Boussinesq side of the comparison: surface-excess time series, a surface-excess map, and an explicit budget-diagnostics figure. It is the diagnostic companion page for understanding where the multi-simulation spread comes from.

See also

Read the gallery and validation reading guide if you want the parameter mapping, a recommended reading order, and the first modifications to try.

Summary comparison figure for four-simulation moderate suite with surface-excess diagnostics.

Case Setup

• Base simulations are identical to the four-simulation moderate suite: MF6 structured, NWT structured, MF6 triangular, and Boussinesq triangular.

• Additional observables expose surface-excess response and Boussinesq budget structure rather than only the shared state variables.

• The page is intentionally denser because it is meant for diagnosis after reading the simpler synthesis page.

What It Shows

• How a multi-simulation suite can be extended with targeted diagnostic observables instead of only repeating the same state metrics.

• How Boussinesq-specific surface-excess and budget views help explain disagreements seen in the more generic four-simulation page.

• How the same comparison backbone can support both a compact synthesis page and a more causal diagnostic page.

Key Parameters

• This config keeps the multi-simulation backbone but adds observables that are diagnostic rather than universally shared across all simulations.

• Use the surface-excess series and map to explain why the Boussinesq triangular simulation departs from the MODFLOW simulations under moderate forcing.

• The budget diagnostics are explanatory aids, not a replacement for the comparable cross-simulation metrics shown on the simpler suite page.

How To Read It

• Read this page after the simpler four-simulation suite, not before it.

• Use it when you need a causal explanation for one mismatch, especially on the Boussinesq triangular branch, rather than a first-pass comparison overview.

• Keep in mind that not every diagnostic observable exists for every simulation, so this page is partly asymmetric by design.

Next Steps

• Use the gallery and validation reading guide to distinguish example pages, comparison pages, and validation pages.

• Go back to the simulation walkthrough when you need to inspect one contributing run in isolation.

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

• docs/source/_static/capability_gallery/simulation_comparison/ex12_multi_simulation_moderate_causes_comparison_manifest.json

• docs/source/_static/capability_gallery/simulation_comparison/ex12_multi_simulation_moderate_causes_comparison_metrics.json

• docs/source/_static/capability_gallery/simulation_comparison/ex12_multi_simulation_moderate_causes_observables.csv

• docs/source/_static/capability_gallery/simulation_comparison/ex12_multi_simulation_moderate_causes_summary_metrics.csv

• docs/source/_static/capability_gallery/simulation_comparison/ex12_multi_simulation_moderate_causes_difference_metrics.csv

Artifacts

• docs/source/_static/capability_gallery/simulation_comparison/ex12_multi_simulation_moderate_causes.png

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