Repository navigation
Preparing alpha-ctsm5.2.mksrf.16_ctsm5.1.dev123 tag - #2016
Conversation
- mapping files removed - T31 (48x96) removed - new files found in lnd/clm2/surfdata_esmf/ctsm5.2.0 Also update for consistency: - modify_fsurdat.py to not look for PFTDATA_MASK in new fsurdat - /python/ctsm/test/testinputs fsurdat files - /python/ctsm/test/testinputs .cfg files - tools/mksurfdata_esmf/gen_mksurfdata_jobscript_multi.py
| @@ -1,2 +1,2 @@ | |||
| flanduse_timeseries = '$DIN_LOC_ROOT/lnd/clm2/surfdata_map/landuse.timeseries_4x5_hist_simyr1850-2015_200311.nc' | |||
| flanduse_timeseries = '$DIN_LOC_ROOTlnd/clm2/surfdata_esmf/ctsm5.2.0/landuse.timeseries_10x15_hist_78_CMIP6_1850-2000_c230517.nc' | |||
There was a problem hiding this comment.
Notes to self:
- Typo: Need
/lndinstead oflnd
|
@ekluzek in this morning's Stand-up, you requested info on the new (i.e. ctsm5.2) 1-degree fsurdat and landuse files. I have opened this PR to share all the new fsurdat and landuse files. As we discussed, the list will continue to be updated over the next few weeks as needed. |
In a meeting today with @ekluzek and @wwieder we decided that I should merge this PR as is (after wrapping up with the test-suite), so that @ekluzek may proceed with the makefile.data work. |
|
Two tests still FAIL on cheyenne: The error messages seem to me harder to resolve, though I wonder if they arise from inconsistencies between the surface (new) and initial (old) data. @ekluzek before I spend too much time on these, it would be helpful to discuss, in case you have insights and/or we decide that I should merge the PR without resolving these two. Also, I just submitted the izumi test-suite, so I will look at results tomorrow. |
The test now passes: ERP_P36x2_D_Ld5.f10_f10_mg37.I2000Ctsm50NwpBgcCropGswp.cheyenne_intel.clm-default
|
@ekluzek and I met about the test-suite results and agreed the following:
I see it as least disruptive to add -ignore_warnings to the testmod directory; the test now works. I included a corresponding note in the testmod's README.
To run the izumi test-suite, I rimported necessary datasets, because I do not have appropriate permissions to copy the files to izumi. I added a README in the directory containing the files on cheyenne Izumi test-suite OK |
to get past this error DON'T use the '-fire_emis' option when '-bgc fates' is activated in the test ERP_P72x2_Ld30.f45_f45_mg37.I2000Clm50FatesRs.cheyenne_intel.clm-mimicsFatesCold
Description of changes
Large changes to
namelist_defaults_ctsm.xml.Changes to various other files, mainly for consistency.
Attribution of work:
The original modifications to
namelist_defaults_ctsm.xmlrelated to the development of the new mksurfdata_esmf tool were done by @mvertens, as was the original development of the new mksurfdata_esmf tool itself.Specific notes
Contributors other than yourself, if any:
@ekluzek @mvertens
CTSM Issues Fixed (include github issue #):
Are answers expected to change (and if so in what way)?
Yes, because we are generating new fsurdat and landuse files.
Any User Interface Changes (namelist or namelist defaults changes)?
Large changes to
namelist_defaults_ctsm.xml.Testing performed, if any: