Skip to content

Change how CLM_CO2_TYPE is set from the compset longname #4078

@ekluzek

Description

@ekluzek

In CESM2.1 emissions driven scenarios were turned on by using the _BGC flag at the end of the compset name. For concentration driven _BGC%BDRD was used and _BGC%BPRP was used for emissions driven. The "D" corresponds to Diagnostic and "P" to prognostic. And the first B means BGC or BioGeoChemical flow of Carbon through the system and the 3rd "R" means Radiative effect if atmospheric radiation responds to CO2.

See this explaination in the CESM forums:

https://bb.cgd.ucar.edu/cesm/threads/how-the-co2-concentration-is-determined-in-bprp-compset-emission-driven.7933/

In CESM3 it was proposed that compset aliases allow for a C or E at the end of the time period to specify if it was Concentration driven or Emissions driven. That convention is probably fine for the aliases, but it's not very robust or clear when you use it in the compset longnames. The reason for the C or E proposal was because BPRP and BDRD was very cryptic and Concentration or Emissions driven is more clear. But, by triggering it with something even more unclear in the long-name -- is probably worse.

This is something that the CESM project as a whole needs to decide. A few ideas are:

  1. Go back to the use of _BGC%BDRD/_BGC%BPRP -- just use the "C/E" in the aliases (this would require no changes)
  2. Change so that an E at the end of the timeperiod means Emissions
  3. Use _BGC at the end, but either _BGC%CONC or _BGC%EMIS for concentration or Emissions driven
  4. Change the name of _BGC at the end to _CO2 as well as doing "3"

With the exception of "1" they all require about the same amount of work, and require changes to config_component.xml for most CESM components.

Once, CESM as a whole decides on how to handle this we can implement the solution.

Metadata

Metadata

Assignees

Labels

enhancementnew capability or improved behavior of existing capabilitynextthis should get some attention in the next week or two. Normally each Thursday SE meeting.scienceEnhancement to or bug impacting scienceusabilityImprove or clarify user-facing options
No fields configured for Usability.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions