-
Notifications
You must be signed in to change notification settings - Fork 312
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
some CLM history fields don't restart properly #31
Comments
Bill Sacks < sacks@ucar.edu > - 2014-11-30 20:12:40 -0700 From Mariana (from bug 2091): There are still two problems that I have to track down with the restarts. They are that NFIRE is not bfb on restart and that EFLX_GRND_LAKE has a fill pattern difference on restart. I am wondering how long these two bugs have been there - since neither of these fields appear in when the suffix |
Bill Sacks < sacks@ucar.edu > - 2014-11-30 20:13:13 -0700 From Mariana (from bug 2091): Committed refactor_koven_bugfix_n01_clm4_5_1_r098 [I think this should say: refactor_koven_bugfix_n02_clm4_5_1_r098] which fixed the restart problem for history variable NFIRE. Basically, it was to remove the following if clause in CNVegStateType.F90 Now only history variable EFLX_GRND_LAKE has a problem on restart. |
Bill Sacks < sacks@ucar.edu > - 2014-11-30 20:13:34 -0700 From Mariana (from bug 2091): I just confirmed that NFIRE was not bit-for-bit and EFLX_GRND_LAKE had fill pattern differences in clm4_5_1_r096 for the test: ERS_Ly5.f10_f10.ICLM45BGCCROP.yellowstone_intel |
Bill Sacks < sacks@ucar.edu > - 2014-11-30 20:16:04 -0700 As to Mariana's suggestion of changing the ERS_Ly5 test to include more history fields: I think this is a good idea. I'd suggest that, once the ERS test and others are set up to compare component history files as well as cpl hist files, we should change most or all of our reducedOutput tests to instead inherit from the "monthly" testmod, or something similar to it, so that they keep all of the default history fields, just with monthly rather than daily output. |
Bill Sacks < sacks@ucar.edu > - 2014-12-01 05:26:10 -0700 One more comment that I forgot to include from bug 2091, from me: At a glance, I'm not convinced that your fix for nfire is entirely correct. From a skim through CNFireMod, it looks like what's going on here is that nfire is only set in certain conditions, and when those conditions aren't met, it stays at its value from the previous time step. My intuition is that the correct thing to do is to either: (1) Set nfire in every time step - setting it to 0 in conditions where it is currently not being touched. (2) Keep the current logic (so nfire is only touched in certain conditions), and adding it as a restart field. I don't understand the fire code well enough to know which of those is correct. |
Bill Sacks < sacks@ucar.edu > - 2016-07-07 11:35:59 -0600 To summarize the outstanding problems: (1) EFLX_GRND_LAKE has fill pattern differences upon restart (2) NFIRE had different values upon restart; this was fixed, but I think in the wrong way |
From clm-cmt discussion: it looks like the cases where nfire isn't set are ones based on landcover (
I think we should do this - i.e., ensuring nfire is set every time step. This may change answers for just the nfire diagnostic field, but not for anything else (and may not change answers even for nfire). I'm adding this to the simple bfb tag with this caveat. (We haven't looked at |
This shouldn't have any impact on the evolution of the model, but it seems needed so that the nfire diagnostic field is correct: Without this, nfire seems to persist from one time step to the next in conditions where it would remain unset and should in fact become 0; this is relevant in transient landcover cases. Partially resolves ESCOMP#31
I fixed the nfire piece of this in 1b6c2ba. Looking into the eflx_grnd_lake piece: eflx_grnd_lake was added to the restart file in clm4_5_1_r105 (cf8a5e0) and (probably as a result of that) no longer appears to have differences in restart (e.g., However, adding this to the restart file may have been overkill... I'm looking into whether we can get this working without the field being on the restart file. |
It looks like this is no longer needed. This was added to the restart file in clm4_5_1_r105 (cf8a5e0), presumably to fix the different fill patterns upon restart that are mentioned in ESCOMP#31. However, there was a later change that seems to fix this issue the correct way, by ensuring that eflx_grnd_lake is set in every time step, rather than potentially persisting at its previous value (in clm4_5_13_r204 - ce9e407; see also the discussion in http://bugs.cgd.ucar.edu/show_bug.cgi?id=1717). Note that eflx_grnd_lake is just a diagnostic field: it doesn't appear on the right-hand side of any equations in the model.
From some analysis of eflx_grnd_lake, it looks like this can now be removed from the restart file, so I have done that in 1f7a25f. Here is the message from that commit:
(Note that the bugzilla site is now only accessible from the internal NCAR network.) |
So to summarize: all remaining outstanding aspects of this issue are now resolved on a branch that will soon come to master. |
It looks like this is no longer needed. This was added to the restart file in clm4_5_1_r105 (cf8a5e0), presumably to fix the different fill patterns upon restart that are mentioned in ESCOMP#31. However, there was a later change that seems to fix this issue the correct way, by ensuring that eflx_grnd_lake is set in every time step, rather than potentially persisting at its previous value (in clm4_5_13_r204 - ce9e407; see also the discussion in http://bugs.cgd.ucar.edu/show_bug.cgi?id=1717). Note that eflx_grnd_lake is just a diagnostic field: it doesn't appear on the right-hand side of any equations in the model.
import_export can force fields to be non-negative
Bring updates needed for NUOPC
* change cdeps data component module names when a CPP macro named CESMCOUPLED is not defined. Co-authored-by: Jun Wang <jun.wang@noaa.gov> Co-authored-by: Jim Edwards <jedwards@ucar.edu>
Key commits: * 5d2345e Explicitly set MPIFC in MCT configure step; Disabled -fallow-argument-mismatch flag * 583734a Temporary fix for arg mismatch error by adding -fallow-argument-mismatch * 9a05700 CI: Trigger on any branch and enabled compiler warnings
…794fd5a25bd8f71f83a7364d3ff8ace984d68c2' into eclm
Bill Sacks < sacks@ucar.edu > - 2014-11-30 20:12:04 -0700
Bugzilla Id: 2093
Bugzilla CC: andre@ucar.edu, erik@ucar.edu, muszala@ucar.edu, rfisher@ucar.edu,
Mariana found that some CLM history fields don't restart properly. This was documented in bug 2091, but I'm moving this here, because it's really a separate (and less critical) problem from 2091.
The text was updated successfully, but these errors were encountered: