Choosing model component versions #49
Replies: 3 comments
-
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. @aekiss @dougiesquire What do you think? |
Beta Was this translation helpful? Give feedback.
-
By "following CESM" do you mean keeping up to date with the latest CESM, i.e. a strategy like this?
@ezhilsabareesh8 - sounds like you may need to modify your JRA55-do support to be compatible with step 2. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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?
Beta Was this translation helpful? Give feedback.
All reactions