next up previous contents
Next: 3 Creating and Running Up: UsersGuide Previous: 1 Introduction   Contents

2 Obtaining the Source Code and Datasets

The source code and datasets required to run the Community Land Model version 3.0 (CLM3.0) in offline mode (uncoupled from other components of the Community Climate System Model version 3 (CCSM3.0)) can be obtained via the web from:


http://www.cgd.ucar.edu/tss/clm.


The user should refer to the CAM3.0 User's Guide or the CCSM3.0 User's Guide for instructions on obtaining code and datasets to run CLM3.0 coupled to other CCSM3.0 components.

It is assumed that the user has access to the utilities tar, Free Software Foundation gunzip and gmake (GNU gmake).

The CLM3.0 distribution consists of two tar files:


CLM3.0_code.tar.gz


and


CLM3.0_inputdata.tar.gz.


The file CLM3.0_code.tar.gz contains code, documentation, and scripts. This file must first be uncompressed with the gunzip utility and then "untarred" as follows:


gunzip -c CLM3.0_code.tar.gz | tar xvf -


The above command both uncompresses and "untars" the code into the following subdirectory hierarchy containing clm3/ as the root:


Table 1: Source Code Directory Structure
Directory Name Description
src/ Directory of FORTRAN and "C" source code
src/biogeophys/ Biogeophysics routines (e.g., surface fluxes)
src/biogeochem/ Ecosystem and biogeochemistry routines (e.g., DGVM and VOCs)
src/csm_share/ Code shared by all the geophysical model components of the Community
  Climate System Model (CCSM). Contains code for CCSM
  message passing, orbital calculations, and system utilities.
src/main/ Control (driver) routines
src/mksrfdata/ Routines for generating surface datasets
src/riverroute/ River routing (RTM) routines
src/utils/ Independent utility routines
src/utils/esmf/ Earth System Modeling Framework utilities
src/utils/timing/ General purpose timing library
bld/ Directory of build, test and run scripts
bld/offline/ Script to build and execute the model on various platforms
tools/ Directory of tools for input dataset manipulation (these tools are used independent of running the model)
tools/convert_ascii/ Routines for converting user-generated ascii surface dataset files to netCDF format suitable for use by the model
tools/interpinic Tool for creating new initial CLM3.0 datasets from existing CLM3.0 datasets at another model resolution and/or landmask
tools/newcprnc/ Tool for comparing model netCDF history files


The file CLM3.0_inputdata.tar.gz contains surface and offline atmospheric forcing datasets. This file must first be uncompressed with the gunzip utility and then "untarred" as follows:


gunzip -c CLM3.0_inputdata.tar.gz | tar xvf -


The above command results in a directory hierarchy containing inputdata/lnd/clm2/ as the root. This directory hierarchy is outlined below.


Table 2: Input Data Directory Structure
Directory Name Synopsis
NCEPDATA/ One year's worth of atmospheric forcing variables in monthly netCDF format suitable for running the model in offline mode (uncoupled from the atmospheric model)
pftdata/ Plant functional type (PFT) physiological constants dataset (ascii format)
rawdata/ "Raw" (highest provided resolution) datasets (netCDF format)
  (used by CLM3.0 to generate surface datasets at model resolution)
rtmdata/ River direction map for RTM in ascii format
srfdata/ Directory containing netCDF CLM3.0 surface and "fgrid" datasets
  The surface datasets include new-format ("allpfts") and old-format datasets for running CLM3.0 in offline mode
  NOTE that surface datasets used in any CAM or CCSM run can also be used to run CLM3.0 in offline mode
  For "fgrid" datasets see section 4.2 and Example 6
output/ Model netcdf history files provided for the user to validate their port of CLM3.0
  This data was generated using the file, jobscript.csh (see section 3.1) which was run on the NCAR IBM SP for 1 year using the data in directory NCEPDATA/.


Note that we are currently providing eight surface datasets for running offline CLM3.0. These datasets are located in inputdata/lnd/clm2/srfdata. A brief synopsis of each of these datasets is given below. It is important to keep in mind that any surface dataset used for a CAM or CCSM run can also be used for running offline CLM. We are providing these datasets as a way for the user to quickly begin using offline CLM3.0.


+


next up previous contents
Next: 3 Creating and Running Up: UsersGuide Previous: 1 Introduction   Contents
csm@ucar.edu