-
Notifications
You must be signed in to change notification settings - Fork 315
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
Fix defaults in clm6_0 physics #2492
Comments
@wwieder good job on pointing this out! This looks to be my bad, and was an oversight in bringing in clm6_0 physics. I think I see why this happened, I'm going to review to figure out what process could have prevented it. I also think this applies to a few other things and I'll point them out. We need to fix this for cesm2_3_beta17, so I'm changing the milestone. |
@wwieder the workaround would be to use clm5_1 physics. You can do that by either using a long compset name with CLM51 rather than CLM60, or to change CLM_PHYSICS_VERSION in your case to clm6_0. |
@wwieder I'm thinking the version with the right defaults is ctsm5.1.dev174, with the updated defaults for arctic vegetation health. Does that sound right to you? |
Wondering if we should quickly conduct a simulation or two (spinup, historical?) once this comes to main to see if we get the results we expect, particularly with regard to the deadveg changes? |
@olyson that does make sense. I was thinking that minor version updates should have that done for them. It's possible once this is corrected that you'll get identical results to when you did this in ctsm5.1.dev174 though. So we might not have to do full long simulations. |
In comparing clm5_1 and clm6_0 namelists I see this difference...
the parameter file is a renamed copy for clm6_0, and I reverified that they are identical with cprnc...
I do remember comparing clm5_1 and clm6_0 namelists, so I'm trying to figure out what I did there and why it failed... |
Update to ctsm5.1.dev174 Update to newer tag. Which also includes an externals update which broke the build/run of mksurfdata_esmf. As a result I added some additional unit-testing in order to detect this sort of thing sooner. Conflicts: bld/namelist_files/namelist_defaults_ctsm.xml bld/unit_testers/build-namelist_test.pl
I ran ctsm_sci for ctsm5.1.dev174 so I could compare to ctsm_sci from ctsm5.2.0 and for example with one test I see the above things we talked about along with the ctsm5.2.0 expected changes. But, also irrigate is set to .false.
|
Yes this seems accurate |
In investigating this, I setup a case to reproduce the Arctic health simulations done in preparation for ctsm5.1.dev174 from @olyson, in there I noticed another file that is different the ndep stream file:
It's not clear to me right now where this is coming from, but it's also something to figure out more carefully. |
This is funny. Presumably the first file is for a HIST compset, while the second would be for an 1850 compset, but I'm assuming both cases are for 1850 compsets? |
Yes, both cases are 1850 compsets. And I think I just figured out why this happened and what I need to do to fix it. It's again the common problem of having more than one place where changes need to go. So a traditional software problem. And it's a specific problem we've identified with the namelist defaults where there are several ways of doing it that are mostly duplicative. We discussed this sort of thing in this document: https://docs.google.com/presentation/d/1FIaQmgN35v3tQxd9hpxcUQZ2CJXFpfx991rZgXwMKzA/ I think it's also possible that the HIST version actually has the same date for 1850, but that is another thing to check. If so we likely should just use the HIST version rather than the 1850 one. For issues that cover making this problem less likely: and of course #585 which is bigger... Note also #1166 that had similar namelist problems for clm5.0.001. So there is also likely an issue when a new physics option comes in. There are some changes to process that I think will help for that situation. |
Also I'm not sure it's "funny", at least from my perspective. :-) But, maybe you mean funny in a different way? |
OK, so the problem with the remaining settings are the clm5_1 settings in the bld/namelist_defaults/use_cases directory. #605 would help prevent that. The other problem is that the namelist testing wasn't going over each physics versions for each use-case, that would've also prevented this. This also means that we don't have coverage in aux_clm testing for each physics version with each use-case. The full set would be 16x3=48 and we probably only have a quarter of those. So the namelist testing might suffice, and maybe just add a few for the important cases... |
…clm5_1 and clm6_0 physics options is only the params_file which is what's expected this finishes out issues in ESCOMP#2492
Brief summary of bug
I'm creating cases with CLM5.2 and noticed that
snow_thermal_cond_method
defaults to Jordan1991 in both SP and BGC cases. Is this intended? I thought we switched this to Sturm1997 in #2348?The text was updated successfully, but these errors were encountered: