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

SSP cases get rcp45 anomalies #258

Open
samsrabin opened this issue Jan 5, 2024 · 1 comment · May be fixed by #292
Open

SSP cases get rcp45 anomalies #258

samsrabin opened this issue Jan 5, 2024 · 1 comment · May be fixed by #292
Assignees
Labels
bug Something isn't working CESM Only Responsibility: CTSM Responsibility to manage and accomplish this issue is the CTSM Software group

Comments

@samsrabin
Copy link

samsrabin commented Jan 5, 2024

(This was originally filed as ESCOMP/CTSM#2301, but during the SE meeting yesterday it was suggested this might be a CDEPS issue.)

Brief summary of bug

When setting up an SSP case with anomaly forcings requested, by default it gets rcp45 anomalies, regardless of SSP requested.

General bug information

CTSM version you are using: ctsm5.1.dev159
CDEPS version you are using: cdeps1.0.24
See also Externals.cfg.

Does this bug cause significantly incorrect results in the model's science? Yes, if not manually corrected.

Configurations affected: Probably any SSP compset where anomaly forcings are created. Tested with ssp245, ssp370, and ssp585.

Important details of your setup / configuration so we can reproduce the bug

Tested on Derecho with the bash script /glade/u/home/samrabin/ctsm_cdeps_ssp-temperature/setup_case.sh, which

  1. takes one argument, of ssp number (e.g., 245);
  2. sets up a test case with compset using that SSP;
  3. specifies anomaly_forcing = 'Anomaly.Forcing.Temperature' in user_nl_datm;
  4. prints the compset of that case; and
  5. prints the datafile associated with Anomaly.Forcing.Temperature in CaseDocs/datm.streams.xml.

Important output or errors that show the problem

No matter what SSP is specified, datm.streams.xml has this:

  <stream_info name="Anomaly.Forcing.Temperature">
   <taxmode>cycle</taxmode>
   <tintalgo>nearest</tintalgo>
   <readmode>single</readmode>
   <mapalgo>bilinear</mapalgo>
   <dtlimit>1.5</dtlimit>
   <year_first>2006</year_first>
   <year_last>2300</year_last>
   <year_align>2006</year_align>
   <vectors>null</vectors>
   <meshfile>/glade/campaign/cesm/cesmdata/inputdata/atm/datm7/anomaly_forcing/domain.permafrostRCN_P2.c2013.nc</meshfile>
   <lev_dimname>null</lev_dimname>
   <datafiles>
      <file>/glade/campaign/cesm/cesmdata/inputdata/atm/datm7/anomaly_forcing/af.tas.ccsm4.rcp45.2006-2300.nc</file>
   </datafiles>
   <datavars>
      <var>tas   Sa_tbot_af</var>
   </datavars>
   <offset>0</offset>
  </stream_info>
@wwieder
Copy link

wwieder commented Apr 4, 2024

@ekluzek noted that CTSM SEs will do this.
@samsrabin noted this seems like an easy fix, but a bad bug. Can we do sooner, rather than later?

@ekluzek ekluzek added bug Something isn't working CESM Only Responsibility: CTSM Responsibility to manage and accomplish this issue is the CTSM Software group labels Apr 4, 2024
@samsrabin samsrabin linked a pull request Aug 9, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CESM Only Responsibility: CTSM Responsibility to manage and accomplish this issue is the CTSM Software group
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants