|CESM Research Tools: CLM4 in CESM1.0.4 User's Guide Documentation|
|Prev||Chapter 4. How to run some special cases||Next|
To spinup the CLM CNDV model -- you first follow the procedures above to spinup the CN model.
Then you take the CN initial state file you created for the spinup with just CN, and
run CNDV for 200 more years.
We've provided such spunup files for two resolutions (f09 and f19) and two time-periods
(1850 and 2000), so in this example we will use the files provided to start from.
We've also provided a spinup file at f19 resolution for CNDV, hence the following is
NOT required when running at f19.
If you were to start from your own CLMCN spunup files -- the procedure would require
There are no compsets using CNDV, so in
Example 4-6. Example CNDV Spinup Simulation
> cd scripts > ./create_newcase -case CNDV_spinup -res f09_g16 -compset ICN -mach bluefire > cd CNDV_spinup # Set run type to startup and do a cold start > ./xmlchange -file env_conf.xml -id RUN_TYPE -val startup # The following sets CLM_CONFIG_OPTS to "-bgc cndv" in env_conf.xml (you could also use an editor) > ./xmlchange -file env_conf.xml -id CLM_CONFIG_OPTS -val "-bgc cndv" # Make the default primary history file annual and add an annual 1D vector auxiliary file # By putting the following in a user_nl_clm file. > cat << EOF > user_nl_clm &clm_inparm hist_nhtfrq = -8760, -8760 hist_mfilt = 1, 1 hist_fincl2 = 'TLAI', 'TSAI', 'HTOP', 'HBOT', 'NPP' hist_dov2xy = .true., .false. / > ./configure -case # NOTE: If you were using your own CN spinup files you would edit the namelist to use it # $EDITOR Buildconf/clm.buildnml.csh # # Now build and run as normal > ./CNDV_spinup.bluefire.build # The following sets RESUBMIT to 10 times in env_run.xml (you could also use an editor) > ./xmlchange -file env_run.xml -id RESUBMIT -val 10 # The following sets STOP_OPTION to "nyears" in env_run.xml (you could also use an editor) > ./xmlchange -file env_run.xml -id STOP_OPTION -val nyears # The following sets STOP_N to 20 years in env_run.xml (you could also use an editor) > ./xmlchange -file env_run.xml -id STOP_N -val 20 # Make sure you turn archiving on, so you save your files to long term archival > ./xmlchange -file env_run.xml -id DOUT_L_MS -val TRUE > ./CNDV_spinup.bluefire.submit
In a data analysis tool you should examine the auxiliary file and examine the
pfts1d_wtgcell to see where and what types of vegetation have
been established. See the caution in Example 1-7 for more
information on visualizing and analyzing 1D vector fields.
Note: CNDV also writes out two vector fields to "hv" auxiliary files, on an annual basis by default.
Note: We've provided a spinup file for CNDV at f19 resolution, you could also use interpinic to interpolate this file to other resolutions.