the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
Deploying Machine Learning components coupled to Earth System Models with OASIS3-MCT (v6) and Eophis (v1.1)
Abstract. The integration of machine learning (ML) components into Earth System Models (ESMs) holds significant potential for improving climate simulations, but it is often constrained by challenges related to interoperability, reproducibility, and computational efficiency. This paper presents a novel coupler-based approach that combines the OASIS3-MCT coupling library with Eophis, a high-performance Python library, to seamlessly deploy ML components in ESMs. By leveraging OASIS3-MCT's robust communication infrastructure, Eophis abstracts the technical complexities of coupling, enabling users to integrate Python-based ML models or analytical parameterizations into geophysical simulations with minimal overhead. Eophis provides a modular interface for defining data exchanges, synchronizing time steps, and managing parallel communications, including advanced features such as halo construction for Convolutional Neural Networks and hybrid CPU/GPU execution. We evaluate this framework by coupling the NEMO4 ocean model with both ML-based and analytical parameterizations, demonstrating scalability, asynchronous execution, and flexible resource allocation. Benchmarking results show that this approach allows to deploy Python components in NEMO without affecting time-to-solution while offering a user-friendly, reproducible, and collaborative workflow. By lowering the barrier to hybrid modeling, this work facilitates the integration of ML components into ESM workflows. The combination of OASIS3-MCT and Eophis offers a practical solution for bridging the gap between ML and climate modeling, supporting innovation in Earth system science while maintaining reproducibility and ease of use.
Competing interests: At least one of the (co-)authors is a member of the editorial board of Geoscientific Model Development.
Publisher's note: Copernicus Publications remains neutral with regard to jurisdictional claims made in the text, published maps, institutional affiliations, or any other geographical representation in this paper. While Copernicus Publications makes every effort to include appropriate place names, the final responsibility lies with the authors. Views expressed in the text are those of the authors and do not necessarily reflect the views of the publisher.- Preprint
(3342 KB) - Metadata XML
- BibTeX
- EndNote
Status: open (until 06 May 2026)
- RC1: 'Comment on egusphere-2026-854', Anonymous Referee #1, 22 Apr 2026 reply
-
RC2: 'Comment on egusphere-2026-854', Anonymous Referee #2, 25 Apr 2026
reply
The manuscript investigates the possibility of making an easy use of AI techniques in existing ESM. It addresses an interesting concept by focusing on coupling FORTRAN models with PYTHON functions via an existing coupler. The authors develop and evaluate a python tool called EOPHIS that adapts OASIS3-MCT coupling library for a new purpose. The manuscript demonstrates EOPHIS capacity to run python functions such as neural network inference or density bias correction within NEMO ocean model workflow in an efficient way. Authors show that it is possible to generalize the coupling of ESM to innovative python methods and modern infrastructure. EOPHIS usage sounds promising, it offers a way to test new methods developed with a modern, user-friendly langage before integrating them into an ESM environment. It also allows to externalize treatments on GPU.Â
I recommend clarifying the structure of sections 2.2 and 3 to improve readability. The role of EOPHIS and its interface with the OASIS3-MCT framework remain unclear. EOPHIS polymorphic characteristics make it difficult to describe. Introducing briefly OASIS3-MCT (before explaining how it is used) could provide helpful context for presenting EOPHIS. The motivation for developing a new Python library should be simplified. To improve clarity, authors might consider to draw a timeline illustrating where and how EOPHIS operates within the coupling process. To improve readability I suggest to use short sentences. I also advise having a single designation for each component along the manuscript. While a detailed comparison of CPU and GPU performance is beyond the scope of this manuscript, it may be worthwhile to briefly address their relative price and energy consumption.
I recommend publication with minor revisions. Please find below a list of minor specific comments in addition to the general suggestions that may be taken into consideration by the authors.Â
Figure 1 : The presence of two OASIS API boxes in the diagram is unclear. In accordance with L160 I suggest to illustrate EOPHIS positioning with two main boxes : ESM (including the OASIS Fortran API) and EOPHIS (including the OASIS Fortran API). Could you clarify the variables (a,b, F(a,b)) in the legend.
Figure 2 : Please clarify the role of Tunnel box by explaining how it is linked to OASIS API boxes from figure 1. It appears that EOPHIS encapsulates the 2nd OASIS API box. This should be clearly illustrated in both the figure and the legend. This figure describes components of the workflow not the workflow itself. Please explain briefly the workflow of the ESM/ML and how EOPHIS gets involved in it in section 3.1. If possible, I recommend separating the configuration phase from the execution phase.
Figure 3 : I suggest clarifying the role of EOPHIS in the data redistribution.Â
Figure 4 : Please separate configuration from execution. Authors might mention that EOPHIS configures light gray cells exchanges through OASIS3 MCT framework and it builds halos necessary for python functions.Â
Figure 7 : Can you comment on the differences in SYPD between both reference experiment a) and reference experiment b) ?Â
L135 : « Although OASIS3-MCT and coupling libraries providing similar API diversity, such as YAC, have already been employed for hybrid modelling, the practical steps required to develop such applications are not entirely straightforward. » To be clarified. Authors should make it explicit that the current coupling ESM/ML is done quasi-manually. « being not straightforward » understates the complexity and technical challenges involved in this process.
L154 : « Finally, even once OASIS3-MCT is properly configured on the Fortran side and the Python component equipped with the necessary features, additional work is needed to implement and configure the OASIS3- MCT interface within the Python script and to prepare the corresponding OASIS3-MCT namelist. » Please clarify what has to be configured or implemented. Please name clearly OASIS2-MCT Fortran API and OASIS2-MCT Python API.
L160 : « We propose a Python library named Eophis, which acts as a generic coupled OASIS3-MCT Python component equipped with the functionalities required by the coupling library, and in which any function from an external Python script can be imported and called with the exchanged data…. » From this description, it is not clear to me how does EOPHIS interact with OASIS and ESM. I suggest to make compatible the EOPHIS presentation and Figure 1.
L183… 191 : I recommend reorganizing this paragraph with a simple and sequential description  of the workflow.Â
L269 : « Additionally, the 2D cases are doubled. » This is not clear.
section 4 : I recommend explicitly stating the reasons why the 3D experiment did not utilize GPU resources.
Citation: https://doi.org/10.5194/egusphere-2026-854-RC2
Viewed
| HTML | XML | Total | BibTeX | EndNote | |
|---|---|---|---|---|---|
| 182 | 83 | 16 | 281 | 11 | 11 |
- HTML: 182
- PDF: 83
- XML: 16
- Total: 281
- BibTeX: 11
- EndNote: 11
Viewed (geographical distribution)
| Country | # | Views | % |
|---|
| Total: | 0 |
| HTML: | 0 |
| PDF: | 0 |
| XML: | 0 |
- 1
Please see my comment in the file.