Orbitally gated monsoon wetlands as pulsed carbon sinks during the late Paleozoic Ice Age

This repository provides the processed CESM diagnostics and reproducible analysis scripts for the study “Orbitally gated monsoon wetlands as pulsed carbon sinks during the late Paleozoic Ice Age”. The dataset is organized around fixed-angular calendar-corrected monthly CESM outputs and a sequential Python workflow used to reproduce the main hydroclimate diagnostics, peat-burial emulator calculations, sensitivity analyses and figure products. The folder data_calendar_corrected_monthly/ contains 21 fixed-angular calendar-corrected monthly NetCDF files. Each file corresponds to one orbital configuration defined by eccentricity state, obliquity state and longitude of perihelion, for example Emax_Omax_90_monthly.nc, Emean_Omean_180_monthly.nc and Emin_Omin_180_monthly.nc. These files include the monthly climate fields used in the analyses, including near-surface temperature, precipitation components, evaporation, wind fields, land fraction and associated grid information. The folder scripts/ contains the Python scripts required to reproduce the analysis in the order used in the manuscript. The workflow begins with compute_monsoon_domain_corrected.py, which derives land-monsoon masks and area-weighted hydroclimate diagnostics from the corrected monthly NetCDF files. The figure scripts then reproduce the main manuscript analyses from Fig. 2 to Fig. 7, including monsoon precipitation and humid-window diagnostics, eccentricity–obliquity response surfaces, study-area peat-burial forcing extraction, nonlinear peat-carbon burial simulations, the orbital-coupling burial schematic, Sobol sensitivity analysis and spatial extrapolation of monsoon-belt peat-carbon burial over a 1.2 Myr orbital window. The repository also includes intermediate and output products generated by the scripts, such as monsoon masks, study-area forcing parameter files, peat-emulator diagnostics, Sobol sensitivity indices, orbital-trajectory burial fields and figure-ready outputs. The scripts are designed to be run sequentially from the project root. A README file describes the directory structure, required Python packages, processing order, expected inputs and generated outputs.