CAM+CLM-FATES - AMIP type run?

[rambhari01]

Dear Forum Member,

I am new user with the latest version of CESM code, In the past, I have used CESM1.2 for running the CAM5 using F compset for AMIP type runs.

Now, I am planning to use the CESM2.1.5 or CESM2.2.2 to run the CAM6 standalone (using F compset) by prescribing the SST and Sea-ice, but I also want to include the CLM5.0 with FATES as dynamic vegetation component.

Is it possible to create a compset that can have (CAM6 + CLM-FATES) and prescribed by SST and Sea-ice (AMIP type run)?

OR

Is such a component set already available with CESM?

Thank You

-Ram

 

[slevis]

In the directory /cime/scripts, you can type
./query_config --compsets
to see existing options.

If what you want does not exist, you can modify the long form of an existing compset and possibly end up with the configuration that you want.

 

[rambhari01]

In the directory /cime/scripts, you can type
./query_config --compsets
to see existing options.

If what you want does not exist, you can modify the long form of an existing compset and possibly end up with the configuration that you want.

Hi,
Thank you very much for your answer.

I tried getting some information from the compset. It seems that most of the compsets which include FATES as active component belong to category 'I'.

Atmospheric forcings are prescribed as ATM is data model (DATM).

By saying modify you mean if I take

FHIST : HIST_CAM60_CLM50%SP_CICE%PRES_DOCN%DOM_MOSART_CISM2%NOEVOLVE_SWAV

and change SP with FATES. Should we expect this to work well?

If i try creating my own using some of existing compset (Some used has discused this on Forum), either this gives error due to non-supported grids or warning of non-supported compset. How can we get specific grid information that should be used with FATES?


Thanks
-Ram

 

[rambhari01]

Hi,
Thank you very much for your answer.

I tried getting some information from the compset. It seems that most of the compsets which include FATES as active component belong to category 'I'.

Atmospheric forcings are prescribed as ATM is data model (DATM).

By saying modify you mean if I take

FHIST : HIST_CAM60_CLM50%SP_CICE%PRES_DOCN%DOM_MOSART_CISM2%NOEVOLVE_SWAV

and change SP with FATES. Should we expect this to work well?

If i try creating my own using some of existing compset (Some used has discused this on Forum), either this gives error due to non-supported grids or warning of non-supported compset. How can we get specific grid information that should be used with FATES?


Thanks
-Ram

I just tried this, it fails with the following error


Building case in directory /scratch/rs9552/CESM_2.1.5_JNb/sanbox_case_CAMFTS


sharedlib_only is False


model_only is False


Generating component namelists as part of build


Creating component namelists


Calling /scratch/rs9552/CESM_2.1.5_JNb/components/cam//cime_config/buildnml


...calling cam buildcpp to set build time options


ERROR: Command /scratch/rs9552/CESM_2.1.5_JNb/components/cam/bld/build-namelist -ntasks 768 -csmdata /scratch/rs9552/inputdata -infile /scratch/rs9552/CESM_2.1.5_JNb/sanbox_case_CAMFTS/Buildconf/camconf/namelist -ignore_ic_year -use_case hist_cam6 -inputdata /scratch/rs9552/CESM_2.1.5_JNb/sanbox_case_CAMFTS/Buildconf/cam.input_data_list -namelist " &atmexp /" failed rc=255


out=CAM build-namelist - ERROR: No default value found for ncdata


user defined attributes:


key=ic_md val=19790101


err=Died at /scratch/rs9552/CESM_2.1.5_JNb/components/cam/bld/build-namelist line 4065.

 

[slevis]

Responding to your previous message:

I do not know whether it will work and, if so, whether it will work well, but that's a starting point. There is a similar conversation here:

FATES in CLM5

Dear CTSM/CLM scientists, I was reading the CLM5 paper and it is mentioned that FATES is not active by default which made me look into these links (FATES tutorial + user guide + technical note + initialization) to see how this FATES in turned on in CLM. As far as I have read, FATES can be...

bb.cgd.ucar.edu

Regarding grids that work with FATES, the fsurdat file needs to have 16 pfts (not 78 pfts). I don't know of a way to get a list of all such grids. If you don't have access to derecho where you can look at all the files, then you may need to resort to trial and error.

About the ncdata error, I'm guessing you will have to specify a file in the cam namelist...

 

[slevis]

If you don't know which ncdata to specify, you could first start a case that has a default ncdata associated with it. Then return to your custom case and manually specify the same ncdata in your case's cam namelist.

On the question about fsurdat files, you may also have the option of generating an fsurdat file for your custom case.