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 FATES in Fully Coupled CESM Configuration

KumarR

Kumar Roy
New Member
Hello,

I'm trying to run a fully coupled CESM simulation with FATES included in CLM. Since there is no standard compset that includes both FATES and a fully coupled configuration, I created the following custom compset:

1850_CAM60_CLM50%FATES_CICE_POP2%ECO_MOSART_CISM2%NOEVOLVE_WW3_BGC%BDRD

with the resolution f19_g17.

The model builds successfully, but it fails during the run with the following error related to solar radiation balance:
###########################
WARNING:: BalanceCheck, solar radiation balance error (W/m2)
nstep = 98
errsol = 206.567107646436
clm model is stopping - error is greater than 1e-5 (W/m2)
fsa = 589.650018473141
fsr = 58.8546527003309
forc_solad(1) = 109.840006664536
forc_solad(2) = 130.015489733791
forc_solai(1) = 120.094534830304
forc_solai(2) = 81.9875322984055
forc_tot = 441.937563527036
clm model is stopping
...
###############################
The error repeats for several gridcell indices, always stopping due to a large solar radiation imbalance.

Has anyone successfully run FATES in a fully coupled CESM setup? Is there an issue with this specific compset or configuration when using FATES?

Any guidance on how to fix or debug this would be greatly appreciated.

Thanks,
Kumar
 

erik

Erik Kluzek
CSEG and Liaisons
Staff member
This is a known problem with running FATES coupled with CAM, which we know won't work right now. This is something that work is being done to get it going, but we aren't quite there yet. CTSM in NorESM has cases working, but I'm not sure that they have them scientifically vetted yet. So if you can I suggest waiting until we've got this fully figured out and vetted and brought into CESM. I can't really give a timeline for when that will happen, just that it will be a priority after cesm3.0 is released.
 
Vote Upvote 0 Downvote
Top