the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
Can We Trust LLMs for Complex Earth System Model Analysis? Silent Failure and Evidence from Module-Grounded Benchmarking
Abstract. Large language models (LLMs) are becoming increasingly capable of complex scientific scripting, but this growing robustness creates a paradox: the more trustworthy their outputs appear, the more easily scientifically incorrect results can pass unnoticed. In Earth system model (ESM) analysis, such silent failures are more dangerous than visible crashes because they produce plausible figures and statistics that may be accepted without detailed inspection. We address this risk with ESFlow, a module-grounded agentic AI framework that constrains the LLM to compose workflows from validated analysis tools rather than generate arbitrary code. The LLM reads an auto-generated, self-describing catalog and outputs a YAML (human-readable data-serialization) workflow, which is then executed by a deterministic engine. We demonstrate this framework with a validated tool library for Energy Exascale Earth System Model (E3SM) land surface hydrology diagnostics in a benchmark spanning seven analysis tasks and six contemporary LLMs. Across both single-attempt runs and runs augmented with automatic self-debugging, the module-grounded approach attains an overall success rate above 80 %, maintains a low and stable silent-failure rate, and reaches 100 % success for the three high-capability models, whereas unconstrained Python code generation succeeds in only about 5 % of runs and sees its silent-failure rate rise from roughly 16 % to about 40 % under self-debugging. These results suggest that increasing LLM capability does not remove the reliability problem in scientific scripting; it makes silent failures more consequential by making incorrect outputs more convincing. The answer to the trust question posed in the title is therefore conditional: unconstrained code generation is not trustworthy for complex ESM analysis, whereas module-grounded workflow composition can be highly reliable for frontier models and remains substantially more robust under iterative self-debugging. By shifting the LLM's role from code generation to the composition of trusted tools, this framework provides a safer, more scalable architecture for AI-assisted scientific discovery that is aligned with FAIR (findable, accessible, interoperable, and reusable) principles.
- Preprint
(3230 KB) - Metadata XML
-
Supplement
(43039 KB) - BibTeX
- EndNote
Status: open (until 23 Aug 2026)
-
CEC1: 'Comment on egusphere-2026-2237', Juan Antonio Añel, 06 Jun 2026
reply
-
AC1: 'Reply on CEC1', Tian Zhou, 07 Jun 2026
reply
Dear Dr. Añel,
Thank you for pointing this out. We agree that citing the ILAMB data server, and preserving the runtime ILAMB download links in the archived scripts, is not sufficient under the GMD Code and Data Policy.
We have now updated the Zenodo archive associated with the manuscript to include the ILAMB observation data required to reproduce the benchmark results presented in the paper:
- Zenodo record: https://zenodo.org/records/20584449
- DOI: https://doi.org/10.5281/zenodo.20584449
The updated archive includes the three ILAMB-derived NetCDF files used by the benchmark workflows:
- GPCCv2018 precipitation: ilamb/pr/GPCCv2018/pr.nc
- MODIS evapotranspiration: ilamb/evspsbl/MODIS/et_0.5x0.5.nc
- LORA runoff: ilamb/mrro/LORA/LORA.nc
These files are provided together with the existing E3SM sample model output, GRDC streamflow observations, basin polygons, source code, benchmark workflows, and benchmark outputs. The workflow engine still supports automated retrieval from the ILAMB data server during execution, but the updated Zenodo archive now provides a frozen copy of the exact ILAMB files needed for replication.
If the manuscript proceeds to revision, we will update the Code and Data Availability section and add the corresponding Zenodo citation to the bibliography.
Sincerely,
Tian ZhouCitation: https://doi.org/10.5194/egusphere-2026-2237-AC1 -
CEC2: 'Reply on AC1', Juan Antonio Añel, 08 Jun 2026
reply
Dear authors,
Thanks for addressing this issue so quickly. I have checked the repositories and we can consider now the current version of your manuscript in compliance with the code policy of the journal.
Juan A. Añel
Geosci. Model Dev. Executive Editor
Citation: https://doi.org/10.5194/egusphere-2026-2237-CEC2
-
AC1: 'Reply on CEC1', Tian Zhou, 07 Jun 2026
reply
-
RC1: 'Review of egusphere-2026-2237', Anonymous Referee #1, 05 Jul 2026
reply
Review of Zhou et al. “Can we trust LLMs for ESM analysis etc” submitted to GMD, 2026
In their submission to GMD, the authors present a software package, ESFlow, which enables LLM-assisted compilation and orchestration of ESM data analysis from pre-existing analysis modules available from a trusted resource. These analysis modules clearly define their required inputs and resulting outputs, including sufficiently rich metadata, to ensure interoperability between workflow steps and avoid ambiguities in the LLM’s decision process. ESFlow provides an interface allowing any existing LLM to be plugged into the system and aid the ESM data analysis process. The authors show that this system works well based on an analysis use-case in which E3SM data is analysed for river runoff in 6 major basins spread of the entire globe. This alone is a great result and introduces a nice tool.
Where the paper shines, in my opinion, is the analysis that follows. The authors use the ESFlow framework to analyse a) the performance of an ensemble of LLMs using the ESFlow interface over a range of analysis use-cases (from simple to rather complex) and b) the performance of the ESFlow-enabled construction of analysis pipelines compared to when LLM’s are given the same analysis task to design and execute the workflow from scratch. The ranking of workflow outcomes is done in four categories: Success, Silent Failure, Obvious Failure and Crash. Here, the most interesting, and a focus of the paper, is the Silent Failure category, which implies that the workflow produces results which look true at first glance, but are actually wrong – hence the most dangerous version of LLM-assisted analysis results. Performance is evaluated w.r.t. a baseline obtained from a human-conceived and tested analysis workflow.
For a), there is some spread in performance across different LLMs, with the major big models (Claude Opus 4.6, GPT-5, Gemini 2.5 Flash) performing almost flawlessly throughout, and smaller models showing weaknesses. Interestingly, silent failures occur for only one model in this setup (o4-mini), and only so for the more complex tasks. Overall, a) shows that the ESFlow framework works well. In total, 31 of 168 runs do not succeed at first shot, with 8 of those being silent failures.
For b), the vast majority of workflow designs and executions actually crash at the first attempt, i.e. they do not execute (111 of 168). Interestingly, when the LLMs don’t crash, they mostly produce silent failures (for the simplest analysis use case), 27 in total. Only 9 of 168 runs achieve a success at first shot.
The authors then explore the capacity of LLMs to correct themselves (to e.g. recover from a crash) by allowing for up to three rounds of self-debugging in case of a crash. The result from this, especially for setup b), is concerning: a lot of runs that crashed in the first round now execute, but mostly produce silent failures he majority of crashes is converted into silent failures (61 runs now work, but 39 of those become silent failures). This is a huge issue in my opinion and constitutes a strong message of this paper.
In summary, the paper is of very high relevance and is at the heart of current developments and advances in data analysis, not just in the geosciences, but across disciplines. The scientific community has to find ways to enable trustworthy applications of AI in their processes and the approach presented in this paper is one of the ways to go: enabling AI to rely on trusted resources beats pure code generation by lengths. I could go more into detail on this, but will not do so due to time limitations. Thank you for this important work! It paves the way for more globally inclusive approaches of workflow construction.
The paper fits very well into the scope of GMD (see above), it presents a novel concept to enable trustworthy LLM-assisted ESM data analysis and advances this field significantly conceptually. Methods and assumptions are valid and clearly outlined and the conclusion is supported by the results. The source code and all supporting material is provided on zenodo (while I must say that I did not attempt to execute it due to lack of technical fitness on my end). Overall, the description of the technical backbone of ESFlow is kept very short in the paper - this could be expanded.
The overall structure and language are clear and the assistance of Claude Code is acknowledged by the authors.
Nevertheless, I do have just very few general remarks which need addressing before the paper can be accepted for publication in GMD. None of them concern the scientific content of the paper.
General remarks
References:
I have a problem with the fact that a lot of the literature cited here is only available on arxiv, and it is often not clear to which journal the paper was actually submitted for review or if a paper has been submitted to a peer-reviewed journal at all.
Although I understand that finding appropriate, peer-reviewed literature for this topic is difficult, I request the authors to cite peer-reviewed literature especially for the Introduction or provide more citation details for the non-peer-reviewed preprints which they cite.
Further, although this may be obvious, but the authors do not provide ANY reference for the LLMs they use. Please add!
Lines 17-20, and 75-76: in these two instances, the authors declare their approach to be aligned with the FAIR principles. This is a very long shot and does not play justice to the concept behind FAIR and the efforts of the community behind the evolving concepts of applying the FAIR principles to workflows (refer to e.g. Wilkinson et al., 2025). The approach presented here is purely local, the workflow produced is, as far as I can see, not abstracted using a common workflow language and is not provided in a centralized, FAIR enabling repository with citation information, standardized, machine interepretable metadata and a PID. Further, all the analysis modules are geared to work with E3SM and would have to be adopted for other models, implying that standardization along common domain-specific vocabularies has not been done (Lines 315-319). As I said, the approach presented in this paper paves the way for more inclusive, global approaches for composing workflows, also in a FAIR manner. The current state is however not FAIR, rather a first step towards it.
Figures:
According to GMD guidelines, the authors should check that the figures provided in the paper are suitable for color-vision impaired audiences. Clearly, this has not been done, as the colors red and green appear in the same plots for Figures 3, 5, 6 and 7. The problem is especially relevant in Figures 6 and 7, in which evaluation results become virtually visually indistinguishable. I request the authors to consult the GMD provided resource (https://www.geoscientific-model-development.net/submission.html#figurestables) to check an adapt their plots.
Title:
As far as I know, the name of the code introduced in a paper, in this case ESFlow, must be mentioned in the title for a paper published in GMD.
References:
Wilkinson, S.R., Aloqalaa, M., Belhajjame, K., et al Applying the FAIR Principles to computational workflows. Sci Data 12, 328 (2025). https://doi.org/10.1038/s41597-025-04451-9
Citation: https://doi.org/10.5194/egusphere-2026-2237-RC1
Viewed
| HTML | XML | Total | Supplement | BibTeX | EndNote | |
|---|---|---|---|---|---|---|
| 491 | 252 | 26 | 769 | 126 | 23 | 18 |
- HTML: 491
- PDF: 252
- XML: 26
- Total: 769
- Supplement: 126
- BibTeX: 23
- EndNote: 18
Viewed (geographical distribution)
| Country | # | Views | % |
|---|
| Total: | 0 |
| HTML: | 0 |
| PDF: | 0 |
| XML: | 0 |
- 1
Dear authors,
Unfortunately, after checking your manuscript, it has come to our attention that it does not comply with our "Code and Data Policy".
https://www.geoscientific-model-development.net/policies/code_and_data_policy.html
In the "Code and Data Availability" section of your manuscript you state that the ILAMB dataset is retrieved from ilamb.org. However, we can not accept this. You must provide with your manuscript a repository (acceptable according to our policy) with the ILAMB data necessary to replicate the work you present here.
The GMD review and publication process depends on reviewers and community commentators being able to access, during the discussion phase, the code and data on which a manuscript depends, and on ensuring the provenance of replicability of the published papers for years after their publication. Please, therefore, publish the ILAMB data in one of the appropriate repositories and reply to this comment with the relevant information (link and a permanent identifier for it (e.g. DOI)) as soon as possible. We cannot have manuscripts under discussion that do not comply with our policy.
Later, if the Topical Editor decides to continue with the review or publication process of your manuscript and you are requested to upload a new version of it, then The 'Code and Data Availability’ section of your manuscript must also be modified to cite the new repository locations, and corresponding references added to the bibliography.
I must note that if you do not fix this problem, we cannot continue with the peer-review process or accept your manuscript for publication in GMD.
Juan A. Añel
Geosci. Model Dev. Executive Editor