dynamic PFT's (setting flanduse_timeseries) are incompatible with dynamic vegetation (use_cndv=.true)

[zhangguangzhi]

I would like to simulate dynamic changes in vegetation based on climate variability, rather than following the specifications in the "flanduse_timeseries" file.
When using CLM5, it seems that I can only achieve this by enabling the FATES module, but it significantly increases the computation time. Therefore, I am considering using the CNDV module from CLM4.

Thus, I enabled CNDV for clm4.5. However, during the build process, an error appears indicating that 'flanduse_timeseries' is not set. (err=ERROR : CLM build-namelist::CLMBuildNamelist::add_default() : No default value found for flanduse_timeseries. Are defaults provided for this resolution and land mask?).

Q1: If I provide the 'flanduse_timeseries' file at this point, will the simulated vegetation changes still be based on climate data?

However, when I set the 'flanduse_timeseries' file, an error occurs: err=ERROR : CLM build-namelist::CLMBuildNamelist::setup_logic_surface_dataset() : dynamic PFT's (setting flanduse_timeseries) are incompatible with dynamic vegetation (use_cndv=.true).

Q2: The solution I am considering is to use compset 1850_DATM%GSWP3v1_CLM45%CNDV_SICE_SOCN_RTM_SGLC_SWAV. However, the forcing varies. This way, I wouldn't need the 'flanduse_timeseries' file, and I could obtain vegetation distribution changing with climate.However, if fixed to a specific year, dynamic vegetation cannot be enabled (do_transient_pfts = true) (err=ERROR: CLM build-namelist::CLMBuildNamelist::setup_logic_do_transient_pfts(): do_transient_pfts can only be set to true when running a transient case (flanduse_timeseries non-blank)). In this way, is it possible to simulate the dynamic changes of vegetation? Is this setup correct?

The follow is my setting：
./xmlchange CLM_CO2_TYPE=diagnostic
./xmlchange DATM_CO2_TSERIES=20tr
#./xmlchange CCSM_CO2_PPMV=279.27

./xmlchange RUN_TYPE=hybrid
./xmlchange RUN_STARTDATE=0001-01-01
./xmlchange RUN_REFDATE=0041-01-01
./xmlchange RUN_REFCASE=R01_CLM45CNDV_finalspinup

./xmlchange STOP_N=1250
./xmlchange STOP_OPTION=nyears
./xmlchange DATM_CLMNCEP_YR_START=1000
./xmlchange DATM_CLMNCEP_YR_END=2249
./xmlchange DATM_CLMNCEP_YR_ALIGN=1
./xmlchange REST_N=10
Q3 When I run this case, no log file is displayed in the run path, the following is an error
-------------------------------------------------------------------------
2023-08-13 21:33:40 MODEL EXECUTION BEGINS HERE
run command is bsub -q q_x86_share -n 375 */bld/cesm.exe >> cesm.log.$LID 2>&1
2023-08-13 21:33:40 MODEL EXECUTION HAS FINISHED
ERROR: Model did not complete - see */run/cpl.log.230813-213339

only cesm.log shows ‘Job <55016623> has been submitted to queue <q_x86_share>’. l cant find cpl.log.

Do you have any suggestions, experts?

 

[slevis]

It's difficult to help you without an error log. Can you see other log files with error messages in them?

Also, I wonder about the "REFCASE" that you show above. Is the REFCASE a CNDV case that ran successfully? Could be interesting to know the exact setup differences between the case that ran and the case that failed. Is it just the xmlchange commands above? If so, it may help to try one change at-a-time, to try isolating the problem.

 

[zhangguangzhi]

Dear staff, an error occurred when I was running the normal run (-compset 20TR_DATM%CRU_CLM45%BGCDV_SICE_SOCN_RTM_SGLC_SWAV) after spinup: ERROR: CO2 is outside of an expected range in CLM45BGCDV. Below are my log files, stream files and CO2 files made by myself. Do you know why there is this error?

 

[zhangguangzhi]

It's difficult to help you without an error log. Can you see other log files with error messages in them?

Also, I wonder about the "REFCASE" that you show above. Is the REFCASE a CNDV case that ran successfully? Could be interesting to know the exact setup differences between the case that ran and the case that failed. Is it just the xmlchange commands above? If so, it may help to try one change at-a-time, to try isolating the problem.

This seems to have been a build problem, and now the new error is that CO2 is outside of an expected range

 

[slevis]

With the information that I have and assuming that I understood correctly, I suspect the reason for the CO2 error is that you are using your own CO2 and stream files. My usual recommendation is to first confirm that you can run successfully with provided files rather than your own. Then you can compare your files to the provided files and determine what you have done wrong.