handle edge case model no_leap, data gregorian#192
Conversation
|
Thanks for looking into this, @jedwards4b. Can we use this hash for testing 50439d3? I also didn't really understand your comment about RUN_STARTDATE. This shouldn't be modified for LAJA? |
|
Only full years are used in any case. I don't think you need to modify anything. Yes, please test with that hash and |
billsacks
left a comment
There was a problem hiding this comment.
@jedwards4b Thank you for all of your work on this tricky problem.
|
This case isn't running for some reason. I'm not really sure what to try next? |
|
This seems to have broken the cases that were previously running |
|
@wwieder I think that this is ready for you to try again now. |
|
Hi Jim, this seems to be working fro the sites where we have a full 4 years of input data, but not the 'edge cases' where there are only 3 complete years of input data (e.g. LAJA & GUAN with input data 2019-2021, or MOAB that I only want to spin up using 2018-2020). In all cases input data are GREGORIAN and model calendar is running NO_LEAP. |
|
For reference, I'm creating these cases as follows: from the following directory: |
|
So sorry. Looking into it now. |
|
I think I have a fix now, running several cases > 100 years to be sure. In the MOAB case I am getting Which is why I guess you only wanted to cycle to 2020 - is there a run_neon option for that? |
Description of changes
Handles an edge case of model in no_leap and data Gregorian. This case was handled prior to #191 which
messed it up.
Specific notes
Contributors other than yourself, if any:
CDEPS Issues Fixed (include github issue #):
Are there dependencies on other component PRs (if so list):
Are changes expected to change answers (bfb, different to roundoff, more substantial):
Any User Interface Changes (namelist or namelist defaults changes):
Testing performed (e.g. aux_cdeps, CESM prealpha, etc):
Hashes used for testing: