CESM Research Tools: CLM4 in CESM1.0.4 User's Guide Documentation
PrevNext

Chapter 4. How to run some special cases

Table of Contents
Running with the prognostic crop model on
Running with the irrigation model on
Spinning up the Satellite Phenology Model (CLMSP spinup)
Spinning up the biogeochemistry Carbon-Nitrogen Model (CN spinup)
Spinning up the Carbon-Nitrogen Dynamic Global Vegetation Model (CNDV spinup)
Running with MOAR data as atmospheric forcing to spinup the model
Running with your own previous simulation as atmospheric forcing to spinup the model
Doing perturbation error growth tests
Running stand-alone CLM with transient historical CO2 concentration

In this chapter we describe how to run some special cases that take more than one step to do. The straightforward cases have compsets and/or build-namelist use-cases setup for them or require simple editing of a single-case. All of the cases here require you to do at least two simulations with different configurations, or require more complex editing of the case (changing the streams files).

The nine cases we will describe are:

  1. Running with the prognostic crop model on

  2. Running with the irrigation model on

  3. Spinning up the Satellite Phenology Model (CLMSP spinup)

  4. Spinning up the biogeochemistry Carbon-Nitrogen Model (CN spinup)

  5. Spinning up the Carbon-Nitrogen Dynamic Global Vegetation Model (CNDV spinup)

  6. Running with MOAR data as atmospheric forcing to spinup the model

  7. Running with your own previous simulation as atmospheric forcing to spinup the model

  8. Doing perturbation error growth tests

  9. Running stand-alone CLM with transient historical CO2 concentration

Caution

The cases in this chapter are more sophisticated and require more technical knowledge and skill than cases in previous chapters. The user should be very familiar with doing simple cases before moving onto the cases described here.

Running with the prognostic crop model on

In CLM4 in CESM1.0.3 a prognostic crop model was added to CLM4. The prognostic crop model is setup to work with CN for present day conditions and we have surface and initial condition datasets at f19 resolution. In order to use the initial condition file, we need to set the RUN_TYPE to startup rather than hybrid since the compset for f19 sets up to use an initial condition file without crop active. To activate the crop model we simply add "-crop on" to CLM_CONFIG_OPTS.

Example 4-1. Example Crop Simulation


> cd scripts
> ./create_newcase -case CROP -res f19_g16 -compset ICN -mach bluefire
> cd CROP
# Append "-crop on" to CLM_CONFIG_OPTS in env_conf.xml (you could also use an editor)
> ./xmlchange -file env_conf.xml -id CLM_CONFIG_OPTS -val "-crop on" -append
# Change to startup type so uses spunup initial conditions file for crop if it exists
# By default the model will do a hybrid startup with an initial condition file
# incompatible with the crop surface dataset.
> ./xmlchange -file env_conf.xml -id RUN_TYPE -val startup
> ./configure -case
# Now build and run normally
> ./CROP.bluefire.build
> ./CROP.bluefire.submit

PrevHomeNext
Adding or Changing Default Filenames Running with the irrigation model on