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
I think that the first thing that we should do in narrowing down this issue, is making sure that we get the same result within machine precision between CPU and GPU. A few places where we could have differences is where the order of operations could differ between the two implementations, in particular, reductions and DSS.
@juliasloan25 has already done some machine precision tests of atmos states, and she's seen departures after the first timestep (CliMA/ClimaCoupler.jl#614). I don't think we've looked any deeper yet though. Do we already have any CPU-GPU consistency tests in ClimaCore? I thought someone's mentioned them recently but I'm not totally sure where to look.
See stand-alone Moist held-suarez atmos runs here:
https://buildkite.com/clima/climacoupler-longruns/builds/514
Running with this script, which mimics the atmos driver.
Some plots (100d, i.e. 10 10-day averages):
Zonal mean wind
Zonal mean temperature
1st level temperature
Instantaneous 100d rhoe_tot (first level)
The text was updated successfully, but these errors were encountered: