Hey there,
You can increase the number of PFTs, or you can modify the existing PFTs to chose only the ones of interest. Running with fewer PFTs will be faster!
But actually, in FATES the 12th PFT is a C4 grass. The default PFTs in FATES are:
[1] "broadleaf_evergreen_tropical_tree"
[2] "needleleaf_evergreen_extratrop_tree"
[3] "needleleaf_colddecid_extratrop_tree"
[4] "broadleaf_evergreen_extratrop_tree"
[5] "broadleaf_hydrodecid_tropical_tree"
[6] "broadleaf_colddecid_extratrop_tree"
[7] "broadleaf_evergreen_extratrop_shrub"
[8] "broadleaf_hydrodecid_extratrop_shrub"
[9] "broadleaf_colddecid_extratrop_shrub"
[10] "arctic_c3_grass"
[11] "cool_c3_grass"
[12] "c4_grass"
BUT, in FATES you can fairly easily define your own set of PFTs using the fates parameter file (from the CTSM source code directory it is located in CTSM/src/fates/parameter_files/fates_params_default.cdl). You'll need to convert this .cdl file into a .nc file, which you can do using the command ncgen:
Code:
ncgen -o my_param_file.nc CTSM/src/fates/parameter_files/fates_params_default.cdl
Once you have this .nc file you can make modifications to it using the scripts CTSM/src/fates/tools/FatesPFTIndexSwapper.py and CTSM/src/fates/tools/modify_fates_paramfile.py.
FatesPFTIndexSwapper.py can be used to grab only the PFTs of interest (e.g. if you only wanted a C4 grass in your file):
Code:
FatesPFTIndexSwapper.py --fin my_param_file.nc --fout param_file_justC4.nc --pft-indices 12
This will create a parameter file (param_file_justC4.nc) with ONLY the default FATES C4 grass PFT - the index for which will now be 1 in this parameter file.
You can then modify parameter values for this PFT using modify_fates_paramfile.py, e.g.:
Code:
modify_fates_paramfile.py --fin param_file_justC4.nc --fout param_file_justC4.nc --O --var fates_leaf_vcmax25top --val 70 --PFT 1
If you run with this parameter file (by setting fates_paramfile='/path/to/my/parameter/file.nc' in the user_nl_clm file in your case directory) FATES will
ONLY run with the PFTs specified in your parameter file (regardless of what is on the input surface file), with the parameters set up in that parameter file.
In this way, you can create your own parameter file with multiple user-defined PFTs.
Let me know if you have any further questions!