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
ClimaCoupler implements a "Leaderboard" module. Fundamentally, this module does two things:
Allow users to specify observational data and compute bias and RMSE between simulated data and observations
Allow users to specify RMSEs for other models and compare how our model performs
While the module works, there are some drawbacks, mostly stemming from the fact that the code is embedded in ClimaCoupler
it clunky to use if one has already some output
small modifications require going through the entire ClimaCoupler CI (which takes >1 h)
it cannot be used by other packages
With this SDI, we move the module from ClimaCoupler to ClimaAnalysis. In the process, we update it to make use of newer features recently introduced in ClimaAnalysis (that will lead to simpler code).
Cost/Benefits/Risks
Benefits include:
Fixing the problems above
Allowing ClimaLand to directly use this code for comparing against observations
Extracting some code that is useful in itself (e.g., computing integrals of OutputVars)
The logic of the code is already implemented and working, so the main cost is developer time.
Once this is completed, we will be able to directly compute bias and mse from two OutputVars. Packages like ClimaCoupler will load simulation data and observation data as OutputVars.
SDI Revision Log
The text was updated successfully, but these errors were encountered:
The Climate Modeling Alliance
Software Design Issue 📜
Purpose
ClimaCoupler implements a "Leaderboard" module. Fundamentally, this module does two things:
While the module works, there are some drawbacks, mostly stemming from the fact that the code is embedded in ClimaCoupler
With this SDI, we move the module from ClimaCoupler to ClimaAnalysis. In the process, we update it to make use of newer features recently introduced in ClimaAnalysis (that will lead to simpler code).
Cost/Benefits/Risks
Benefits include:
OutputVar
s)The logic of the code is already implemented and working, so the main cost is developer time.
People and Personnel
Components
Inputs
Results and Deliverables
Scope of Work
At higher level, there are two main components:
Bias/RMSE
split_by_season
#59constrained_cmap
#62OutputVar
reader to support more generic NetCDF files #68resampled_as
, a function that resamples anOutputVar
to the same dimensions as another one #65integrate_*
functions to allow for integrating of anOutputVar
. In this, we follow the same pattern as theaverage_*
functions. #75plot_bias
#86split_by_season
for OutputVar #78find_best_single_model
,find_worst_single_model
, andmedian
for struct that store RMSEs #89plot_box_plot
andplot_leaderboard
using structs that store RMSEs #90reordered_as
, a function that reorders anOutputVar
to match the ordering of dimensions of another one #94OutputVar
#95Once this is completed, we will be able to directly compute bias and mse from two OutputVars. Packages like ClimaCoupler will load simulation data and observation data as OutputVars.
SDI Revision Log
The text was updated successfully, but these errors were encountered: