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

Mapping between FATES PFTs and CLM PFTs

robbert02

Robbert Kouwenhoven
New Member
Hi all! I have a question regarding the 'mapping' or 'translation' between FATES PFTs from the fates_params_default.nc file and the CLM PFTs from the surface data input file. The PFT indices of FATES' parameter file is different than CLM's PFT indices in the surfdata. For example, in the parameter file pft=0 corresponds to tropical evergreen tree, whereas pft=0 in the surfdata corresponds to not vegetated. Where in the model does this mapping happen? Is there a specific file that translates / matches the FATES pfts with the corresponding CLM pft? And is this hard-coded or based on long name?
Thanks in advance!
 

samrabin

Sam Rabin
Member
My sense from a look at the code is that these are just completely separate things with no mapping at all. CLM has a bunch of places where plant behavior is determined based on the name of the PFT, which we should avoid doing in favor of what FATES does, which is to have everything about a PFT defined as a parameter. A search through the code shows that the fates_pftname variable from the parameter file isn't even read anywhere.

I'm not sure what happens if you try to save a CLM history variable with the pft dimension during a FATES run, but I'd assume any such output to be nonsense. Instead, you'd want to save the equivalent FATES variable with the PF suffix.
 
Vote Upvote 0 Downvote
Top