MF6 Triangular vs NWT Structured on Moderate Forcing

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 compares a MODFLOW 6 run on the committed triangular support against a MODFLOW-NWT run on the historical 60x60 structured grid. It keeps the same moderate annual forcing as the shared-grid comparison but now mixes support families, so the page documents the combined effect of solver choice and spatial discretization.

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 mf6 triangular vs nwt structured on moderate forcing.

Case Setup

• Reference simulation: MODFLOW 6 on the committed triangular mesh.

• Candidate simulation: MODFLOW-NWT on the 60x60 structured grid.

• Map observables are resampled on a shared fine raster over the support intersection before parity metrics are computed.

What It Shows

• How solver and support differences accumulate when the comparison no longer uses one identical mesh.

• How a fine common raster and an intersection extent make map comparisons possible across incompatible supports.

• How point chronicles and outlet flux help decide whether disagreement is local, diffuse, or tied to basin export.

Key Parameters

• [comparison.fine_raster] enabled = true is essential here because the compared meshes are not natively aligned cell by cell.

• extent_mode = “intersection” keeps the comparison on the spatial footprint both supports actually share.

• Read outlet-flux differences with more caution than in the same-grid case: they now reflect both solver behaviour and support discretization.

How To Read It

• Treat this page as a mixed solver-and-support comparison, not as a pure solver benchmark.

• Read the parity metrics after checking the support mismatch described in the case setup; otherwise the numbers look more absolute than they really are.

• Use this page to understand what changes when you leave the shared-support regime used by the tighter comparison cases.

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_mf6_nwt_moderate_comparison_manifest.json

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

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

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

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

Artifacts

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

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