Figure generation#

This gallery focuses on paper-ready and analysis-ready plotting workflows in GeoPrior.

Unlike the examples in tables_and_summaries/, the pages collected here begin from plotting scripts whose main purpose is to generate visual outputs: main figures, supplementary figures, diagnostic panels, sensitivity plots, transfer figures, and spatial analytics views.

The emphasis is therefore on communication through figures. These examples show how GeoPrior turns model outputs, diagnostic signals, and support artifacts into interpretable visual summaries that can be used for analysis, reporting, and manuscript preparation.

Typical outputs in this section include:

  • publication-style PNG, SVG, or EPS figures,

  • multi-panel diagnostic layouts,

  • sensitivity heatmaps and comparison plots,

  • spatial forecast maps and hotspot analytics panels,

  • transferability and impact figures,

  • validation and cumulative-summary plots.

In other words, this gallery is about building the figures that communicate results, not the intermediate artifacts that those figures depend on.

Module guide#

Module

Main output

Purpose

plot_driver_response.py

Relationship figure

Plot driver-response relationships to show how key forcing or context variables relate to predicted behavior.

plot_core_ablation.py

Ablation comparison figure

Plot the core ablation comparisons used to interpret the main model-design trade-offs.

plot_uncertainty.py

Uncertainty figure

Plot the main uncertainty diagnostics, including calibration and reliability-oriented views.

plot_spatial_forecasts.py

Spatial forecast maps

Plot the main spatial forecast maps and multi-panel forecast layouts.

plot_physics_sanity.py

Physics sanity figure

Plot sanity checks for the physics-informed components.

plot_physics_maps.py

Physics map panels

Plot map-based views of learned or inferred physics quantities.

plot_physics_fields.py

Field diagnostic figure

Plot field-level diagnostics for physical parameters and related outputs.

plot_physics_profiles.py

Profile diagnostics

Plot profile-style physics diagnostics, typically for appendix or supplementary interpretation.

plot_litho_parity.py

Parity / agreement figure

Plot lithology-related parity or agreement diagnostics.

plot_ablations_sensitivity.py

Sensitivity surface figure

Plot sensitivity surfaces and ablation-response summaries.

plot_physics_sensitivity.py

Physics sensitivity figure

Plot the response of physical metrics or residuals to sensitivity settings.

plot_sm3_identifiability.py

Identifiability figure

Plot SM3 identifiability diagnostics.

plot_sm3_bounds_ridge_summary.py

Bounds / ridge summary

Plot ridge and bounds summaries for SM3-style identifiability experiments.

plot_sm3_log_offsets.py

Log-offset diagnostics

Plot SM3 log-offset diagnostics and related parameter-behavior summaries.

plot_xfer_transferability.py

Transferability figure

Plot transferability performance across source-target settings.

plot_xfer_impact.py

Transfer impact figure

Plot transfer impact in terms of retention, hotspot overlap, and related measures.

plot_external_validation.py

Validation figure

Plot external point-support validation results.

plot_geo_cumulative.py

Cumulative summary figure

Plot cumulative geo-style summaries across years or scenarios.

plot_hotspot_analytics.py

Hotspot analytics figure

Plot hotspot analytics views that summarize spatial hotspot behavior over time or across settings.

plot_uncertainty_extras.py

Supplementary uncertainty panels

Plot additional uncertainty panels beyond the main uncertainty figure.

Reading path#

A useful way to move through this gallery is to follow the logic of a complete visual analysis workflow:

  1. begin with core model-behavior figures,

  2. continue to uncertainty and sensitivity structure,

  3. move into spatial and physics-aware visual diagnostics,

  4. finish with transfer, impact, and validation views.

That is why the examples are grouped by plotting purpose rather than only by command family.

Why this separation matters#

This gallery deliberately keeps three concerns distinct:

  • artifact construction,

  • plot generation,

  • figure interpretation.

That separation makes the workflow easier to understand. It also helps users distinguish between commands that build reusable analysis products, scripts that turn those products into figures, and pages that focus on explaining what the resulting visuals actually mean.

Notes#

  • These examples are intentionally compact and lesson-oriented.

  • The scripts in this section are plot-first: they may print small summaries, but their main output is a figure file.

  • A useful rule of thumb is:

    • tables_and_summaries/ builds reusable artifacts,

    • model_inspection/ explains helper-based diagnostics,

    • figure_generation/ turns results into visual outputs.

  • Many of these scripts are naturally suited to PNG, SVG, or EPS export for manuscripts, appendices, reports, and presentation material.

Core ablation: learning what physics adds to the workflow

Core ablation: learning what physics adds to the workflow

Ablations and sensitivities: learning where the model behaves well in lambda space

Ablations and sensitivities: learning where the model behaves well in lambda space

Driver-response plots: learning how the response moves with the drivers

Driver-response plots: learning how the response moves with the drivers

External validation: comparing inferred effective fields against independent site evidence

External validation: comparing inferred effective fields against independent site evidence

Cumulative subsidence on a satellite-style map

Cumulative subsidence on a satellite-style map

Hotspot analytics: turning future forecasts into decision-ready priority maps

Hotspot analytics: turning future forecasts into decision-ready priority maps

Lithology parity: comparing the geological composition of the two cities

Lithology parity: comparing the geological composition of the two cities

Physics fields: learning to read the physical story in a map

Physics fields: learning to read the physical story in a map

Physics maps: turning pointwise payloads into readable spatial fields

Physics maps: turning pointwise payloads into readable spatial fields

Physics profiles: reducing a 2D lambda landscape into readable 1D lessons

Physics profiles: reducing a 2D lambda landscape into readable 1D lessons

Physics sanity: checking closure agreement and residual behavior

Physics sanity: checking closure agreement and residual behavior

Physics sensitivity: learning how lambda choices reshape the physics diagnostics

Physics sensitivity: learning how lambda choices reshape the physics diagnostics

SM3 bounds versus ridge: learning the two main failure modes

SM3 bounds versus ridge: learning the two main failure modes

SM3 identifiability: learning when recovery is accurate and when parameters slide along a ridge

SM3 identifiability: learning when recovery is accurate and when parameters slide along a ridge

SM3 log offsets: learning where the inferred fields drift from their priors

SM3 log offsets: learning where the inferred fields drift from their priors

Spatial forecasts: how to read observed maps, fitted maps, and future forecast maps together

Spatial forecasts: how to read observed maps, fitted maps, and future forecast maps together

Cross-city transferability: learning what survives transfer between cities

Cross-city transferability: learning what survives transfer between cities

Forecast uncertainty: learning how calibration behaves across cities and horizons

Forecast uncertainty: learning how calibration behaves across cities and horizons

Expanded uncertainty diagnostics: learning what the main uncertainty figure still hides

Expanded uncertainty diagnostics: learning what the main uncertainty figure still hides

Transfer impact: what transfer changes for retention, risk, and hotspot stability

Transfer impact: what transfer changes for retention, risk, and hotspot stability

Cross-city transferability (v3.2): what survives when a workflow moves to the other city

Cross-city transferability (v3.2): what survives when a workflow moves to the other city