the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
Review of climate simulation by simple climate models
Abstract. Simple Climate Models (SCMs) are a key tool in climate research, enabling the rapid exploration of climate responses beyond the reach of more complex models and aiding in the estimation of future climate uncertainty. Over the past two decades, the number and diversity of SCMs have expanded considerably, increasing their use but also complicating efforts to understand differences in model structure and their implications. The reduced-complexity model intercomparison project (RCMIP) has begun to address this challenge by comparing output from a wide range of SCMs. However, the need for a systematic analysis of model structure remains. Here, we complement RCMIP’s work by systematically analysing the structure, components, and development histories of the 14 SCMs participating in RCMIP. We begin with a summary of the core principles underpinning SCM-based climate simulation, then review genealogy and design choices of each model. This synthesis provides a comprehensive reference for both developers and users, clarifying the diverse approaches within the SCM landscape and supporting informed use and further development of these models.
- Preprint
(1058 KB) - Metadata XML
- BibTeX
- EndNote
Status: open (until 01 Nov 2025)
- RC1: 'Comment on egusphere-2025-2691', Anonymous Referee #1, 06 Sep 2025 reply
-
CC1: 'Comment on egusphere-2025-2691', Marcus Sarofim, 25 Sep 2025
reply
First: Kudos to the authors for pulling together a great review of existing reduced complexity model structures, components, and other factors. This will be very much appreciated by those of us who work with reduced complexity models.
Second: I have a couple minor comments:
Minor comment one regards this statement:
“Moreover, ESMs operate at finer scales, benefitting local and regional analysis, although downscalling approaches to generate regional climate emulators from SCMs have also been explored (Beusch et al., 2020; Mitchell, 2003; Mathison et al., 2025)”
I think this sentence, as written, is slightly misleading because most (all?) regional climate emulators depend on ESM data. All three cited approaches - Beusch et al (MESMER), Mitchell (pattern scaling), and Mathison et al. (PRIME) rely on ESM output in order to build their databases. I’d also recommend adding Tebaldi et al. (2022) (STITCHES) to your list of regional climate emulators (and which also relies on ESM data). Perhaps if the sentence was reframed as, “Moreover, ESMs operate at finer scales, benefitting local and regional analysis. Pattern scaling approaches that leverage ESM data to generate regional climate emulators, which can then be coupled with reduced complexity models to provide higher resolution functionality, have also been explored (citations).”
As a more general statement (and less relevant to this manuscript), I would like the ESM community to lean into the role of understanding the patterns of responses to forcing by running stylized scenarios (e.g., isolating GHG, aerosol, and land use change forcing components) rather than running scenarios produced by IAMs, which add complexity to comparing different scenarios as they differ on all 3 forcing types. Then, these various pattern scaling approaches could be coupled to reduced complexity models to project more realistic scenarios as well as important probabilistic assessments.
Minor comment two is that I would be interested in understanding in what fashion (if at all) box models and IRM approaches differ in terms of behavior. After looking at RCMIP and various other tests, I haven’t identified any fundamental differences between IRMs (as a class) and box models (as a class). Perhaps the discussion at lines 390-409 regarding mathematical equivalence is the answer to this question? If that’s true, maybe this equivalence could be emphasized even more.
Minor additional notes:
Typo: downscaling, not scalling
Figure 10 typo: atmopshere should be atmosphere
Citation: https://doi.org/10.5194/egusphere-2025-2691-CC1
Viewed
HTML | XML | Total | BibTeX | EndNote | |
---|---|---|---|---|---|
1,559 | 95 | 9 | 1,663 | 14 | 21 |
- HTML: 1,559
- PDF: 95
- XML: 9
- Total: 1,663
- BibTeX: 14
- EndNote: 21
Viewed (geographical distribution)
Country | # | Views | % |
---|
Total: | 0 |
HTML: | 0 |
PDF: | 0 |
XML: | 0 |
- 1
Simple Climate Models (SCMs) make up a critical component of the climate model hierarchy and have been used for decades for climate assessment. Although many SCMs with varying levels of complexity exist, there have been few efforts to clarify differences in model structure. In this work, the authors review the 14 SCMs participating in the reduced-complexity model intercomparison project (RCMIP), organizing them by increasing complexity and creating a guide for developers and users.
Overall, this is a strong manuscript with a clear contribution in providing a comprehensive overview of some of the most widely used SCMs. The methodological choices of both which SCMs to include and what components to focus on (e.g. choosing structure over performance) are clear and sufficient. I have one major comment about the stated goals/conclusions of the manuscript. The rest of my questions/suggestions to improve the quality of the manuscript are relatively minor.
Specific Comments:
The paper aims to support informed use of SCMs, e.g. 1571-1572: “... while also informing about the implications of selecting one model over another.” While the detailed descriptions achieve this, the discussion could be strengthened by adding a paragraph that informs practical guidance for model selection. For example, you could briefly summarize which models are best suited for specific applications based on their features. This type of synthesis would make the paper’s thorough exploration of SCMs more accessible to the user community.
In a similar vein, there are points in the manuscript that explicitly address model advantages, but as a developer/user, I’d also love to see disadvantages/failure modes of these different models. Is there a consistent/rigorous way to define a failure mode of an SCM? If so, why have you chosen not to discuss them?
Minor:
Technical Corrections: