Fates with future forcing

[brendanclark]

I am using ctsm5.3.063 and I am trying to run FATES with SSP585 forcing initialized from a spinup simulation I did. When I use the compset starting with I (no anomaly forcing enabled) "ISSP585_DATM%GSWP3v1_CLM50%FATES_SICE_SOCN_MOSART_CISM2%NOEVOLVE_SWAV" the model runs without any problems. But, when I switch to the same compset, without the I "SSP585_DATM%GSWP3v1_CLM50%FATES_SICE_SOCN_MOSART_CISM2%NOEVOLVE_SWAV" (anomaly forcing enabled), then the run fails with no errors in the log files. This can be confirmed (I think) in CaseDocs/datm.streams.xml in the two cases below, this is also somewhat confusing since it seems to contradict the naming convention outlined in the user guide. I am able to successfully specify future forcing in CPLHIST mode with FATES, but I am not able to use anomaly forcing with FATES. Is FATES able to be used with a compset that enables future forcing? Am I misunderstanding something about anomaly forcing (I've only ever used CPLHIST mode before) or am I doing something wrong? The two case paths are below, the only difference is the compset used ("I" vs. no "I" at beginning):

Case that works: /glade/work/brendanc/CTSMcases/300725ctsm5.3.063_fates_ISSP585
Case that doesnt work: /glade/work/brendanc/CTSMcases/300725ctsm5.3.063_fates_SSP585_v3

 

[slevis]

I do not have answers to your questions, but let me start with a troubleshooting idea:

I searched ctsm's github issues

ESCOMP/CTSM

Community Terrestrial Systems Model (includes the Community Land Model of CESM) - ESCOMP/CTSM

github.com

for "fates ssp anomaly" and ended up here:

Add a transient FATES compset alias and make sure do_transient settings are correct by default for FATES · Issue #1617 · ESCOMP/CTSM

Transient simulations are started to be done for FATES. We should add an alias for this and also make sure the namelist is setup to work by default so that do_transient_pfts is FALSE. Definiton of ...

github.com

where I read a comment stating that this compset (similar to yours) worked:
SSP585_DATM%GSWP3v1_CLM50%FATES_SICE_SOCN_RTM_SGLC_SWAV

If this doesn't help, another troubleshooting idea may be to experiment with non-fates anomaly compsets until you find a compset that works. Then you might compare the cases that work against the ones that do not, and manually modify the former or the latter until you have all the options that you want included.

 

[slevis]

@afoster do you have direct answers to @brendanclark's questions?

 

[brendanclark]

The compset you listed also does not work, but when I add an "I" to beginning of the compset (no anomaly forcing) the case runs. I will keep trying to use other compsets to see if I can get anomaly forcing to work with fates with the version of ctsm I am using.

 

[brendanclark]

Also, all of these anomaly forcing compsets work when I am using CLM50%BGC-CROP, it is only when I switch to CLM50%FATES that it does not work.

 

[slevis]

Please post any resolution here for our reference.

If you find that you are unable to resolve this, please post a comment in the issue that I mentioned above, in case you get feedback from one of the fates developers there.