You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to promote the GPU capability into the coupler code, still sharing the same the distribution context between Atmos and the surfaces (which are on the same grid), as we do with MPI.
This will be done in two stages, first making the minimal changes needed to get simulations and tests to run, then secondly propagating these changes throughout the repo and ensuring high code quality throughout.
GPU Buildkite run with the target AMIP setup, which is within ~5% performance of the standalone Atmos run (as in the MPI case - though double check this).
key cases in Buildkite on GPU: slabplanet, target AMIP, DYAMOND (excluding and including topography)
Task Breakdown And Schedule
The content you are editing has changed. Please copy your edits and refresh the page.
@sriharshakandala , @juliasloan25 Thanks for the meeting. Above I've added some details on what we discussed - please feel free to modify it as you feel fit. After CliMA/ClimaAtmos.jl#2341 is merged, let's release ClimaAtmos, after which we can update the coupler and get started on the GPU slabplanet. Looking forward to some fast testing! 🚀
The Climate Modeling Alliance
Software Design Issue 📜
Purpose
We need to promote the GPU capability into the coupler code, still sharing the same the distribution context between Atmos and the surfaces (which are on the same grid), as we do with MPI.
This will be done in two stages, first making the minimal changes needed to get simulations and tests to run, then secondly propagating these changes throughout the repo and ensuring high code quality throughout.
Cost/Benefits/Risks
b: faster AMIP + DYAMOND
People and Personnel
Inputs
Results and Deliverables
Task Breakdown And Schedule
initial runs [1 April 2024]
GPU performance [1 June 2024]
SDI Revision Log
CC
@tapios @cmbengue
The text was updated successfully, but these errors were encountered: