We need a stable interface with robust checks, so once standalone ClimaAtmos is complete, we can immediately test our AMIP configuration. We will also finalize all large software components that need input from scientists (i.e. partitioned surface fluxes).
once this is complete, the AMIP run can be used as a benchmark again
enhancements (other features used by AMIP setups)
fluxes: revise surface fluxes (also the order of timestepping (e.g. radiation) relative to flux computation in Atmos) + include the option to calculate partitioned fluxes
[x] physical tests (see Buildkite runs for different comparisons, also #355, and Slack #coupler-report )
reasonable comparison with observations (TOA fluxes, precipitation, circulation metrics), given the Atmos setup (benchmark)
Task Breakdown And Schedule
fig outstanding bugs in existing code (AMIP Roadmap non-optional requirements)
[x] #282 [25 April]
[x] masking - ensure all tests are implemented and passing for all masking options #286 [1 May]
[x] use most recent ClimaAtmos [15 May]
this will be done in #281 in a separate folder. Here we will update those API changes to the main driver, and we'll work together with @valeriabarra to update the general environment and tests.
[x] enable a surface flux calculation from the atmosphere (from averaged surface states) and partitioned flux calculation from the Coupler (using individual states) #311 [1 August]
SDI Revision Log
tasks to accomplish the Coupler release were split into two SDIs (WIP)
The Climate Modeling Alliance
Software Design Issue 📜
Purpose
We need a stable interface with robust checks, so once standalone ClimaAtmos is complete, we can immediately test our AMIP configuration. We will also finalize all large software components that need input from scientists (i.e. partitioned surface fluxes).
Cost/Benefits/Risks
b: streamlining AMIP delivery.
People and Personnel
Components
Results and Deliverables
QA
#coupler-report
)Task Breakdown And Schedule
SDI Revision Log
CC
@tapios @simonbyrne @cmbengue