Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

Trouble Running CLM-FATES with HIST Compset

K

KumarR

Kumar Roy
New Member
Hello,

I’m attempting to run a transient simulation using CLM-FATES within CESM2.2. Since I couldn’t find an existing compset that supports this directly, I created a custom one:

HIST_DATM%GSWP3v1_CLM50%FATES_SICE_SOCN_MOSART_CISM2%NOEVOLVE_SWAV

However, during model build, I encounter the following error:
###################
ERROR: CLM build-namelist::CLMBuildNamelist::setup_logic_surface_dataset() :
dynamic PFT's (setting flanduse_timeseries) are incompatible with ecosystem dynamics (use_fates=.true.)
####################

Has anyone successfully run FATES with HIST compost?

Is there a recommended way to run transient simulations with FATES? Is this error specific to my custom compset, or is it a known limitation of FATES in CLM?

Any guidance on how to properly configure a transient CLM-FATES simulation or a pointer to a working example would be greatly appreciated.

Thanks,
Kumar
 
Sort by date Sort by votes
slevis

slevis

Moderator
Staff member
@KumarR based on your error message
dynamic PFT's (setting flanduse_timeseries) are incompatible with ecosystem dynamics (use_fates=.true.)

I would change your case's user_nl_clm to say
flanduse_timeseries = ' '

This way you will keep other characteristics of a transient simulation but will not use the transient landuse file.
 
Vote Upvote 0 Downvote
K

KumarR

Kumar Roy
New Member
Thanks for the suggestion @slevis

I had already tried setting flanduse_timeseries = ' ' in my user_nl_clm, but unfortunately, I still encounter the same error during the build process.
It seems like the model still continues to treat this as an incompatible setup between dynamic PFTs and FATES, even with flanduse_timeseries explicitly unset.

Is there another way to disable the dynamic land use internally, or perhaps a different setup I should be using for transient simulations with FATES?

Any further guidance would be much appreciated!

Thanks,
Kumar
 
Vote Upvote 0 Downvote
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I think you will have to try this in a newer development version of CTSM. For example, I tried the following two cases with ctsm5.3.055 and they both ran for one month:

./create_newcase --case Clm60Fates_ctsm53055_1deg_GSWP3V1_hist --res f09_g17 --compset HIST_DATM%GSWP3v1_CLM60%FATES_SICE_SOCN_SROF_SGLC_SWAV_SESP --run-unsupported

./create_newcase --case Clm50Fates_ctsm53055_1deg_GSWP3V1_hist --res f09_g17 --compset HIST_DATM%GSWP3v1_CLM50%FATES_SICE_SOCN_SROF_SGLC_SWAV_SESP --run-unsupported

I'm personally not familiar with the FATES configuration that comes out of the box above, but you can get information on this from the FATES User's Guide:


For example, see the namelist overview section:

 
Vote Upvote 0 Downvote
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
You could also try the "SP" version of FATES, which will be scientifically supported in the CESM3 release:

./create_newcase --case Clm60FatesSP_ctsm53055_1deg_GSWP3V1_hist --res f09_g17 --compset HIST_DATM%GSWP3v1_CLM60%FATES-SP_SICE_SOCN_SROF_SGLC_SWAV_SESP --run-unsupported
 
Vote Upvote 0 Downvote
You must log in or register to reply here.
Top