In this chapter we give some guidance on what to do when you encounter some of the most common problems. We can't cover all the problems that a user could potentially have, but we will try to help you recognize some of the most common situations. And we'll give you some suggestions on how to approach the problem to come up with a solution.
In general you will run into one of three type of problems:
The first type of problem happens when you invoke the configure -case command. This indicates there is something wrong with your template files, or input datasets, or the details of what you are trying to configure the model to do. There's also a trouble-shooting chapter in the CESM1.0.4 Scripts User's Guide. Many of the problems with configuration can be resolved with the guidelines given there. Here we will restrict ourselves to problems from the CLM or DATM templates or input files.
Example 7-1. Example of configure problem with missing datasets
> ./create_newcase -case T31rcp6 -res T31_g37 -compset IRCP60CN \ -mach bluefire > ./configure -case
The following is what is displayed to the screen.
Generating resolved namelist, prestage, and build scripts configure done. adding use_case 1850-2100_rcp6_transient defaults for var clm_demand with val fpftdyn adding use_case 1850-2100_rcp6_transient defaults for var clm_start_type with val startup adding use_case 1850-2100_rcp6_transient defaults for var model_year_align_ndep with val 1850 adding use_case 1850-2100_rcp6_transient defaults for var rcp with val 6 adding use_case 1850-2100_rcp6_transient defaults for var sim_year with val 1850 adding use_case 1850-2100_rcp6_transient defaults for var sim_year_range with val 1850-2100 adding use_case 1850-2100_rcp6_transient defaults for var stream_year_first_ndep with val 1850 adding use_case 1850-2100_rcp6_transient defaults for var stream_year_last_ndep with val 2100 adding use_case 1850-2100_rcp6_transient defaults for var use_case_desc with val Simulate transient land-use, aerosol and Nitrogen deposition changes with historical data from 1850 to 2005 and then with the RCP6 scenario from AIM build-namelist - No default value found for fpftdyn. Are defaults provided for this resolution and land mask? ERROR: generate_resolved.csh error for lnd template configure error: configure generated error in attempting to created resolved scripts
ERROR: generate_resolved.csh error for lnd template
In the example above, it's obvious that the problem is coming from the CLM build-namelist, in other situations it might not be so obvious where the problem is occurring. In such cases it might be useful to add a "set echo" command to the top of the template file so that each command in the template will be echoed to the screen and you can see what is happening and where the error is occurring.
In the example, the error is that the CLM XML database does NOT have a fpftdyn for the given resolution, rcp scenario and ocean mask. That means you will need to create the file and then supply the file into your case. See Chapter 2 for more information on creating files, and see Chapter 3 for more information on adding files to the XML database. Alternatively, you can provide the file to your case by creating a user namelist as shown in the Section called Configure time User Namelist in Chapter 1.
Note: The two most common problems from your CLM template will be errors from the CLM configure or build-namelist. For more information on these scripts see: the Section called More information on the CLM configure script in Chapter 1 and the section on