Showcase a new design for coupling ClimaOcean and ClimaCore-based models. The current ClimaCoupler assumes ClimaCore-based underlying objects, whereas ClimaOcean assumes Oceananigans-based objects, making the two difficult to communicate with each other. With this effort we aim to
unify the interfaces required to couple a component model to ClimaEarth, where the simulation will be setup
present a prototype as the basis for CMIP (on which we can iterate based on feedback)
Cost/Benefits/Risks
b: implements minimal features for ocean/atmosphere coupling
r: reasonable time investment
People and Personnel
Lead: @glwagner
Collaborators: @juliasloan25 @LenkaNovak
Reviewers:
Components
ClimaEarth.jl
Abstract Simulations from Oceananigans and generalize for use by other models
Coupler functionality (for prototyping, keep here, and later will likely be moved to out)
regridding
stagerring (use Oceananigans)
FV-FE (Cartesian available in ClimaCore)
masking and area fractions (perhaps not needed here?)
prescribed data readers (perhaps not needed here?)
flux calculation (NB: flux calculation outside of Atmos only really makes sense for one-timestep coupling)
(WIP)
The Climate Modeling Alliance
Software Design Issue đ
Purpose
Showcase a new design for coupling ClimaOcean and ClimaCore-based models. The current ClimaCoupler assumes ClimaCore-based underlying objects, whereas ClimaOcean assumes Oceananigans-based objects, making the two difficult to communicate with each other. With this effort we aim to
Cost/Benefits/Risks
People and Personnel
Components
Simulations
from Oceananigans and generalize for use by other modelsInputs
Results and Deliverables
Task Breakdown And Schedule
Oceananigans.jl / ClimaOcean.jl
ClimaEarth.jl
SDI Revision Log
CC
@tapios @simonbyrne @cmbengue