Skip to content
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

Update "What's New in CTSM 5.3" #2789

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
63 changes: 29 additions & 34 deletions WhatsNewInCTSM5.3.md
Original file line number Diff line number Diff line change
@@ -1,53 +1,48 @@
Purpose and description of changes since ctsm5.2.005
----------------------------------------------------
# What's new in CTSM 5.3 (tag `ctsm5.3.0`)

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.
## Purpose and description of changes since CTSM 5.2 (tag `ctsm5.2.005`)
- Adds CN Matrix method to speed up spinup for the BGC model.
- Updates surface datasets.
- Brings in new Leung 2023 dust emissions.
- Adds explicit air conditioning for the urban model.
- Updates crop calendars.
- Updates fire model with various improvements, including default parameterization against climate reanalysis from CRU-JRA instead of GSWP.
- FATES compsets can now be run with transient land use.

Changes to CTSM Infrastructure:
===============================
These changes were needed ahead of the CESM3 capability/functionality "chill". For `clm6_0` physics these options are now turned on by default, in addition to Sturm snow and excess ice.

- manage_externals removed and replaced by git-fleximod
- Ability to handle CAM7 in LND_TUNING_MODE
## 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 CTSM answers

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section should mention new surface datasets and land-use timeseries files. Are those only used in clm6_0 physics or all physics versions?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All physics versions.

Changes to defaults for clm6_0 physics:
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
- Snow thermal conductivity method is now `Sturm_1997`
- New initial conditions file for f09 ("1-degree") 1850, with more in progress
- New crop calendars
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“with more in progress”—yes?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, correct.

- Dust emissions is now Leung_2023
- Dust emissions method is now `Leung_2023`
- Excess ice is turned on
- Updates to MEGAN for BVOC's
- Updates to MEGAN for BVOCs
- 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
Copy link
Collaborator Author

@samsrabin samsrabin Sep 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Glacier region 1 is now undefined": What does this mean in terms of answer changes? Why should users care?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is something I need to look at more carefully to describe accurately. We also might want to get Bill to help make sure we are accurate.

- 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
- Add the option for using Matrix CN method for Carbon/Nitrogen BGC spinup

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since CN Matrix is an option, does it really fit in the “answer changes” section?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, it only changes answers when turned on, which normally is just for spinup.

New surface datasets:
=====================
## New surface datasets

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this section title also mention land-use timeseries files?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. I think of "surface datasets" describing both, but for clarity you could spell out both fsurdat and flanduse_timeseries files.

- 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
- 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.
Copy link
Collaborator Author

@samsrabin samsrabin Sep 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"With new surface datasets the following GLC fields...": What does this mean in terms of answer changes? Why should users care?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above.

This is a good way to frame it by the way "why should users care"?. That's a good way to handle everything here.

- 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.
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So mksurfdata_esmf can now make land-use timeseries files back to 1700. Have any of those actually been made?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We did make 1700 for f09. I'm pretty sure we have them in the namelist defaults. Although I'd have to check.

- 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.
- Fix an important bug on soil fields that was there since `ctsm5.2.0`. This has the side effect of `mksurfdata_esmf` now giving identical answers with a change in number of processors, as it should.
- Surface datasets now provided for the `ne0np4.POLARCAP.ne30x4` grid.
- Surface datasets now have their version number embedded to prevent mismatch of surface dataset and CTSM version.
- Remove the `--hires_pft` option from `mksurfdata_esmf` as we don't have the datasets for it.
- Remove `VIC` fields from surface datasets.
Copy link
Collaborator Author

@samsrabin samsrabin Sep 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is --hires_pft removal maybe not worth mentioning? If the datasets aren't available, was anyone using it? Moreover, this tool change doesn’t fit with the substantive changes to surface datasets described in the rest of the section.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. I thought it worth mentioning for users of mksurfdata_esmf because it was a user visible option that we took away. Hence, it's good to explain why. The point is it was an option that wasn't functional so we removed it, and we'll return it when it is functional.

- Updates to input datasets in PFT/LAI/soil-color raw datasets (now from the TRENDY2024 timeseries that ends in 2023), as well as two fire datasets (crop fire peak month, peatland fraction), and the glacier behavior dataset.
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are (were) VIC fields?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VIC is an alternative hydrological parameterization that you could turn on, that we are deprecating. It required a few fields on the surface datasets to be used. This added complexity to both surface datasets as well as testing for it. So removing it simplifies a bunch of things all around.

We could look for what fields were added to the surface datasets, but I think just saying they ware removed is sufficient here.


Loading