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 should put some thought into how we choose component versions.
I suggest for initial testing we should match what @dougiesquire's CIME-built executables used, to see if we can resolve all issues like #21. When that is all working we should consider upgrading to newer versions.
Any comments/objections?
The text was updated successfully, but these errors were encountered:
I suggest for initial testing we should match what @dougiesquire's CIME-built executables used, to see if we can resolve all issues like #21. When that is all working we should consider upgrading to newer versions.
After bumping into a similar issue (see #31), I would strongly support the suggestion of starting with exactly the same versions as @dougiesquire's CIME-built executables. This is straightforward to do, except for the CDEPS component, as recent changes to support JRA55-do introduce some conflicts.
Regarding the strategy to update, I suggest that we keep following CESM for while, at least until we need to incorporate new features that are not available yet in CESM.
By "following CESM" do you mean keeping up to date with the latest CESM, i.e. a strategy like this?
build exes (MOM6-CICE6, then MOM6-CICE6-WW3 and CICE6-WW3) with exactly the same component versions as @dougiesquire's CIME-built executables, and working configs with the same CESM inputs
configs (MOM6-CICE6, then MOM6-CICE6-WW3 and CICE6-WW3) with exes from step 1, but inputs from ACCESS-OM2
set up CI
upgrade to components used in latest CESM; get exes and configs working again
upgrade to more recent model components if needed for new features
@ezhilsabareesh8 - sounds like you may need to modify your JRA55-do support to be compatible with step 2.
Sorry for not been entirely clear. What I meant be "following CESM" was only regarding step 4. That would be assuming we agree on the starting point (steps 1-2).
Regarding the starting point, we could also create a version that is identical to the CESM version used by @dougiesquire and tag it in the repo, but only use it for reference. Then, immediately update CDEPS, leaving everything else unchanged.
That way the JRA55-do support would not need to be changed.
We should put some thought into how we choose component versions.
I suggest for initial testing we should match what @dougiesquire's CIME-built executables used, to see if we can resolve all issues like #21. When that is all working we should consider upgrading to newer versions.
Any comments/objections?
The text was updated successfully, but these errors were encountered: