Skip to content

No longer need to allow for C/E at end of time period#413

Open
billsacks wants to merge 1 commit into
ESCOMP:mainfrom
billsacks:no_conc_emis_on_time_period
Open

No longer need to allow for C/E at end of time period#413
billsacks wants to merge 1 commit into
ESCOMP:mainfrom
billsacks:no_conc_emis_on_time_period

Conversation

@billsacks

Copy link
Copy Markdown
Member

Description of changes

We are changing the compset specification to no longer have C/E at the end of the time period, so we can remove the parsing of this from compset regexes.

Needs to wait for the compset changes in
ESCOMP/CESM#407 and
ESCOMP/CAM#1584.

Specific notes

Contributors other than yourself, if any: none

CDEPS Issues Fixed (include github issue #): none

Are there dependencies on other component PRs (if so list):

Are changes expected to change answers (bfb, different to roundoff, more substantial): bfb

Any User Interface Changes (namelist or namelist defaults changes): no

Testing performed (e.g. aux_cdeps, CESM prealpha, etc): none yet

Hashes used for testing:

@billsacks billsacks requested a review from fischer-ncar June 17, 2026 00:02
billsacks added a commit to ESCOMP/CESM that referenced this pull request Jul 16, 2026
Change long name specifier for CO2 forcings

### Description of changes

We have decided to use the CESM2 scheme for this.

See ESCOMP/CMEPS#658 for some relevant discussion.

I did this with two regex search & replaces:

(1) Concentration-driven:
- Search for `<lname>([^_]*)C_(.*)</lname>`
- Replace with `<lname>$1_$2_BGC%BDRD</lname>`
- Update 2026-06-18: we later decided to remove the `_BGC%BDRD` from these compsets

(2) Emissions-driven:
- Search for `<lname>([^_]*)E_(.*)</lname>`
- Replace with `<lname>$1_$2_BGC%BPRP</lname>`

**This should be coordinated with the following component changes:**
- **This should come in at the same time as the CAM PR that changes compsets similarly: ESCOMP/CAM#1584
- Ideally, [this CTSM PR](ESCOMP/CTSM#4097) and [this CDEPS PR](ESCOMP/CDEPS#413) would come in at the same time. However, it's safe for either or both of them to come later. (The reason that it's ideal for them to come in at the same time is just to ensure that they are bit-for-bit across a wide range of configurations - so it would be ideal to include them in the bit-for-bit prealpha testing that is planned for this PR.)
- For emissions-driven compsets to work correctly, this also needs the changes in [this CAM PR](ESCOMP/CAM#1581); however, emissions-driven compsets currently aren't tested, so it's safe for that CAM PR to come in later

### Specific notes

Contributors other than yourself, if any: none

Fixes: none

User interface changes?: No

**Expected answer changes:** Bit-for-bit for concentration-driven compsets (which are the only ones currently tested). (`B1850E*` and `BHISTE*` compsets would change answers, but we currently don't test them.)

Testing performed (automated tests and/or manual tests):

Ran these tests; they pass and are bit-for-bit:
- ERS_Ld5.ne30pg3_t232.B1850C_LTso.derecho_intel.allactive-defaultio
- ERS_Ld5.ne30pg3_t232.BHISTC_LTso.derecho_intel.allactive-defaultio
- ERS_D_Ld3.ne30pg3_t232.B1850C_LTso.derecho_intel.allactive-defaultio
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant