Emulating the Forced Response of Climate Models with Generative Machine Learning

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2605.16929v2 Announce Type: replace Abstract: Global climate models are essential tools to simulate past and potential future pathways of climate change, as well as associated climate impacts. Shared Socioeconomic Pathways (SSPs) describe a range of future scenarios of global economic and demographic development. These SSPs are intrinsically linked to changes in climate forcings -- the external drivers, such as greenhouse gas and aerosol emissions, which change Earth's energy balance over time. These forcings act as boundary conditions in Earth System Models (ESM), providing insight into the potential climatic impacts of each SSP. Running an ESM, however, is extremely computationally expensive, conflicting with the need for large ensemble runs to provide robust estimates in the presence of internal variability and scenario uncertainty. Machine Learning emulators provide a promising avenue towards fast and cheap scenario generation, but until recently lacked uncertainty quantification and the ability to condition on external forcings. Here, we build upon recent work and extend it by training on multiple SSPs. We successfully generate scenarios of IPSL -- CM6A -- LR unseen during training and remain physically consistent with the underlying climate model, even under strong extrapolation scenarios. Our emulator is validated against MESMER -- M, a statistical emulator of land surface temperature. Our research demonstrates that our model, ArchesClimate -- SSP, does not simply imitate scenarios seen during training, but is actually capable of modeling the response of a …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2605.16929
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.