Fix restart-reproducibility tests for ESM models#131
Conversation
|
Results from running DetailsThe restart reproducibility test fails. Based on earlier comments from @MartinDix, I think this is to be expected due to the cable implementation. |
|
Hi @dougiesquire, I'm getting failing CI tests with the changes
Just realised I need to update the ESM1.5 config |
I think it's failing on the ESM1.5 tests because we don't have an example |
|
I think we need to turn off two of the test parameterizations since they no longer make sense. Mind if I push to this branch? |
|
Yeah go for it! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #131 +/- ##
==========================================
- Coverage 75.21% 75.18% -0.03%
==========================================
Files 18 18
Lines 916 927 +11
==========================================
+ Hits 689 697 +8
- Misses 227 230 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
dougiesquire
left a comment
There was a problem hiding this comment.
LGTM - thanks @blimlim!
|
Thanks @dougiesquire. I'd just had the PR as a draft while the tests were breaking.Marked it as ready for review – are you happy to re-review? |
dougiesquire
left a comment
There was a problem hiding this comment.
Looks even better this time!
|
Thanks @dougiesquire! ... looks like it still needs an additional review from someone else before merging. @jo-basevi would you be happy to have a look at these changes? |
|
Thanks @CodeGat! |
Closes #123
This PR configures the UM and CICE in ESM1.5/1.6 to write daily restarts, allowing for the restart reproducibility test to be run.
The changes hard code a daily restart frequency regardless of the run length. There is a risk here, if anyone modifies the tests to use a longer runtime (e.g. a month or a year).
Is it acceptable as is? I think it's too complicated to set the dump frequency to exactly match any runtime, as you have to start worrying about calendar types and exact start dates.
An alternative would be to require exactly one of years, month, or seconds is non-zero, and swap the dump frequency to 1 month or 1 day accordingly.
Let me know what sounds best!