Equity and Effectiveness of Groundwater Governance Policies (Model Inputs and Outputs)

This Zenodo record provides the model inputs and outputs associated with the GitHub repository Equity_and_effectiveness_GCP. The full simulation inputs and outputs are distributed here as a single archive. Contents The file model_inputs_output.zip contains the full contents of the repository’s inputs/ and outputs/ directories (including nested subfolders), structured to match the GitHub project layout: inputs/bootstrap_samples/: 500 bootstrapped climate and market scenario samples used to generate stochastic model runs. inputs/model_inputs/: 500 serialized model input files (.pkl) ready for execution across groundwater governance policy scenarios. inputs/supplementary/: supplementary inputs used for the fee-based (FB) analysis (e.g., bootstrap price tables used in marginal revenue calculations). outputs/: model run results and downstream analysis products for each policy scenario (Baseline/BAU, Uniform Restriction, Fee-Based, Priority-Based I, Priority-Based II, and R+PR), including intermediate aggregated datasets used for plotting as well as the final manuscript figures generated from those runs. How this archive should be used This archive is not required to run the model. All contents of inputs/ and outputs/ can be generated from the scripts in the GitHub repository (see the scripts/ directory). Instead, this Zenodo snapshot serves two purposes: Verification / regression testing: users can run the scripts to generate inputs/ and/or outputs and compare against the archived versions to confirm that their environment and workflow reproduce the reference results. Convenience: users who wish to inspect the complete run-ready artifacts and outputs without executing the full workflow (which may be computationally intensive) can download this archive directly. Notes The GitHub repository intentionally does not store the full inputs/ and outputs/ contents due to size limits; it includes only the folder structure placeholders. Full regeneration of outputs/ may require significant compute (e.g., HPC), depending on the number of bootstraps and scenarios executed.