ne3np4 to namelist_defaults_ctsm.xml and Makefile for PTS mode #2835
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix unit tests for nstep starting at 1 instead of 0
Add sowing window input files Previously, one could run crops with either (a) sowing windows defined by the hemisphere-specific start and end dates on the paramfile or (b) prescribed sowing dates specified by input file stream_fldFileName_sdate. This PR replaces the latter with two new input files, stream_fldFileName_swindow_start and stream_fldFileName_swindow_end.
Fix RXCROPMATURITY test in zerothtstep branch
...and other mods that I'm preserving from closed PR ESCOMP#2019, such as - changes to long_names and - treating avgflag as a tape (not field) trait for 'I' and 'L' tapes
Update surface datasets, CN Matrix, CLM60: excess ice on, explicit A/C on, crop calendars, Sturm snow, Leung dust emissions, prigent roughness data
Purpose and description of changes since ctsm5.2.005
----------------------------------------------------
Bring in updates needed for the CESM3.0 science capability/functionality "chill". Most importantly bringing
in: CN Matrix to speed up spinup for the BGC model, updated surface datasets, updated Leung 2023 dust emissions,
explicit Air Conditioning for the Urban model, updates to crop calendars. For clm6_0 physics these options are now
default turned on in addition to Sturm snow, and excess ice.
Changes to CTSM Infrastructure:
===============================
- manage_externals removed and replaced by git-fleximod
- Ability to handle CAM7 in LND_TUNING_MODE
Changes to CTSM Answers:
========================
Changes to defaults for clm6_0 physics:
- Urban explicit A/C turned on
- Snow thermal conductivity is now Sturm_1997
- New IC file for f09 1850
- New crop calendars
- Dust emissions is now Leung_2023
- Excess ice is turned on
- Updates to MEGAN for BVOC's
- Updates to BGC fire method
Changes for all physics versions:
- Parameter files updated
- FATES parameter file updated
- Glacier region 1 is now undefined
- Update in FATES transient Land use
- Pass active glacier (CISM) runoff directly to river model (MOSART)
- Add the option for using matrix for Carbon/Nitrogen BGC spinup
New surface datasets:
=====================
- With new surface datasets the following GLC fields have region "1" set to UNSET:
glacier_region_behavior, glacier_region_melt_behavior, glacier_region_ice_runoff_behavior
- Updates to allow creating transient landuse timeseries files going back to 1700.
- Fix an important bug on soil fields that was there since ctsm5.2.0. This results in mksurfdata_esmf now giving identical answers with a change in number of processors, as it should.
- Add in creation of ne0np4.POLARCAP.ne30x4 surface datasets.
- Add version to the surface datasets.
- Remove the --hires_pft option from mksurfdata_esmf as we don't have the datasets for it.
- Remove VIC fields from surface datasets.
New input datasets to mksurfdata_esmf:
======================================
- Updates in PFT/LAI/soil-color raw datasets (now from the TRENDY2024 timeseries that ends in 2023), as well as two fire datasets (AG fire, peatland), and the glacier behavior dataset.
Same as ctsm5.3.001 I made an accidental merge and reverted it.
ctsm5.3.019: Stop running 0th time step
Conflicts: src/main/histFileMod.F90
Delete unused hist_add_subscript method (no references in the CTSM repo)
Conflicts: src/main/histFileMod.F90
doc that masterlist actflag is just h0 in practice, doc that masterlist has all the fields.
…otes Update "What's New in CTSM 5.3"
Useful for redoing tests that failed due to ESCOMP#2916, after having replaced libraries/mpi-serial with a fresh copy.
Minor test suite tweaks.
Includes merge conflicts in src/cpl/lilac/lnd_comp_esmf.F90 due to PR ESCOMP#2912.
These were resolved with PR ESCOMP#2912.
Merge b4b-dev
Merge tag ctsm5.3.020 into b4b-dev
ctsm warm_start mods
|
Update this PR to latest ctsm and run testing. |
ekluzek
approved these changes
Jan 23, 2025
There was a problem hiding this comment.
@slevis-lmwg and I looked at this some. This has the changes from #2333 so that PR will likely become smaller when this comes in. There still might be something there, and I added a couple things to do there also.
I wasn't sure about all of the allow_scm logic with read and read_noscm and the like. But, I've come around to it. I think all of this is required. So the only thing might be changing the names. But, I think it's clear enough that SCM means Single Column Model, although I do think there might be places where some comments around this might be helpful.
I'm adding approve even with the request for a few comments, just so you don't have to have me reapprove. Anything needed to be addressed could go into #2333.
|
derecho izumi |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes
Same as title.
Specific notes
Contributors other than yourself, if any:
@jtruesdal
CTSM Issues Fixed (include github issue #):
Fixes #2768
Are answers expected to change (and if so in what way)?
No.
Any User Interface Changes (namelist or namelist defaults changes)?
New fsurdat/landuse files added to the defaults.
Does this create a need to change or add documentation? Did you do so?
No.
Testing performed, if any:
On derecho
PASS Test the addition of the new fsurdat/landuse files to the Makefile with
PASS ./build-namelist_test.pl (before and after adding ne3np4 tests)
PASS python testing
PASS clm_pymods