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

Fully remove the CRU datm forcing option #323

Open
ekluzek opened this issue Feb 11, 2025 · 0 comments
Open

Fully remove the CRU datm forcing option #323

ekluzek opened this issue Feb 11, 2025 · 0 comments
Assignees
Labels
answers are bfb CESM Only enhancement New feature or request Responsibility: CTSM Responsibility to manage and accomplish this issue is the CTSM Software group

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Feb 11, 2025

The DATM%CRU_ option still has a few vestiges in place, and should be removed to remove uneeded complexity. I don't think it's fully specified and at this point if you really want the old CRU data you should use the slightly newer CRUv7 version.

Looking in cesm3_0_beta05 it's not in testing, so there's no reason to keep it around. The only relevant references I see for it are in datm/cime_config/config_component.xml

cd datm/cime_config
git grep -w CRU
config_component.xml:    <desc atm="DATM[%QIA][%WISOQIA][%CRU][%CRUv7][%GSWP3v1][%MOSARTTEST][%NLDAS2][%CPLHIST][%1PT][%NYF][%IAF][%JRA][%JRA-1p4-2018][%JRA-1p5-2023][%JRA-RYF8485][%JRA-RYF9091][%JRA-RYF0304][%SIMPLE]"> Data driven ATM </desc>
config_component.xml:    <desc option="CRU"> CRUNCEP data set </desc>
config_component.xml:    <desc option="CRUv7"> CLM CRU NCEP v7 data set </desc>
config_component.xml:      <value compset="1850.*_DATM%CRU">1</value>
config_component.xml:      <value compset="HIST.*_DATM%CRU">1901</value>
config_component.xml:      <value compset="20TR.*_DATM%CRU">1901</value>
config_component.xml:      <value compset="SSP.*_DATM%CRU">$DATM_YR_START</value>
config_component.xml:      <value compset="1850.*_DATM%CRU">1</value>
config_component.xml:      <value compset="1850.*_DATM%CRU">1901</value>
config_component.xml:      <value compset="HIST.*_DATM%CRU">1901</value>
config_component.xml:      <value compset="20TR.*_DATM%CRU">1901</value>
config_component.xml:      <value compset="SSP.*_DATM%CRU" >2001</value>
config_component.xml:      <value compset="1850.*_DATM%CRU">1901</value>
config_component.xml:      <value compset="2000.*_DATM%CRU">1991</value>
config_component.xml:      <value compset="2003.*_DATM%CRU">2002</value>
config_component.xml:      <value compset="2010.*_DATM%CRU">2005</value>
config_component.xml:      <value   compset="1850.*_DATM%CRU">1920</value>
config_component.xml:      <value   compset="HIST.*_DATM%CRU">1920</value>
config_component.xml:      <value   compset="20TR.*_DATM%CRU">1920</value>
config_component.xml:      <value   compset="SSP.*_DATM%CRU">2016</value>
config_component.xml:      <value   compset="1850.*_DATM%CRU">1920</value>
config_component.xml:      <value   compset="2000.*_DATM%CRU">2010</value>
config_component.xml:      <value   compset="2003.*_DATM%CRU">2003</value>
config_component.xml:      <value   compset="2010.*_DATM%CRU">2014</value>
@ekluzek ekluzek added answers are bfb CESM Only enhancement New feature or request Responsibility: CTSM Responsibility to manage and accomplish this issue is the CTSM Software group labels Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answers are bfb CESM Only enhancement New feature or request Responsibility: CTSM Responsibility to manage and accomplish this issue is the CTSM Software group
Projects
None yet
Development

No branches or pull requests

2 participants