E3SM-Project
I/O: frequency units discrepancy
Specific situation: REST_N=nminutes. EAMxx doesn't recognize this and errors out.
More generally, CIME expects:
'none', 'never', 'nsteps', 'nstep', 'nseconds', 'nsecond', 'nminutes', 'nminute', 'nhours', 'nhour', 'ndays', 'nday', 'nmonths', 'nmonth', 'nyears', 'nyear', 'date', 'ifdays0', 'end'
EAMxx expects
['nsteps','nsecs','nmins','nhours','ndays','nmonths','nyears']
So in my my situation, the issue is nmins vs nminutes. Both EAMxx and CIME support the minutes spec, but with different names.
Suggested fix: Support nseconds, nsecond, nsecs, etc., i.e. aliases.
As an aside, EAMxx doesn't support end. Not sure how often folks use REST_N=end.
CC @bartgol @tcclevenger @AaronDonahue
We did mention the possibility of adding support for a rest file written at the end (regardless of when that happens), but we never acted on it. There may be an open issue about it, I need to check. Meanwhile, I think it should be fairly easy to add all other names overloads.
Done in https://github.com/E3SM-Project/scream/pull/3086
pls (everyone here) reopen if you disagree :) thanks
@AaronDonahue gentle note: The "fixes" syntax in github is a bit specific (see https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests). Of note, "addresses" isn't a recognized keyword and the issue number must be right after the keyword (without the word "issue")