-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CNP Budget failure for a non-Jan starting run. #6337
Comments
Hi Gautam, thanks for opening this thread. Please see attached for two run scripts that can both reproduce the error.
|
copying @rljacob --- I think we need non-jan tests in our test suites. An example, in the atmosphere (both eam and eamxx) we are often interested in runs starting say oct 1 or dec 1 with nudging. Because once nudged, we can afford ignoring the first month in a simulation, then we end up with a nice whole year left for analysis from a 15-month or 13-month run. The two scream sensitivity campaigns are 13-month-long pairs |
Noting an issue that had same error mesg: #6230 |
The C-states for all budgets (daily/monthly/annual/instantaneous/all time) are updated when the timestep is 1. Fixes #6337 [BFB]
The C-states for all budgets (daily/monthly/annual/instantaneous/all time) are updated on the first ELM step. Adds a 5-day SMS test that starts on 0001-12-28 and runs till 0002-01-01. Fixes #6337 [non-BFB] for tests greater than a year with C budgets.
The C-states for all budgets (daily/monthly/annual/instantaneous/all time) are updated on the first ELM step. Adds a 5-day SMS test that starts on 0001-12-28 and runs till 0002-01-01. Fixes #6337 [non-BFB] for tests greater than a year with budgets.
Error reported by @kchong75
The text was updated successfully, but these errors were encountered: