Chapter 11. Frequently Asked Questions (FAQ)

Table of Contents
What are all these directories and files in my case directory?
How do I modify the value of CCSM env variables?
Why aren't my env variable changes working?
What's the deal with the CCSM4 env variables and env xml files?
Why is there file locking and how does it work?
How do I change processor counts and component layouts on processors?
What is pio?
How do I use pnetcdf?
How do I create my own compset?
How are cice and pop decompositions set and how do I override them?
How do I change history file output frequency and content for CAM and CLM during a run?

What are all these directories and files in my case directory?

The following describes many of the files and directories in the $CASEROOT directory.

Buildconf

is the directory where the buildnml and buildexe component scripts are generated by configure. The input_data_list files are also generated by configure or the buildnml scripts and copied here.

CaseDocs

is a directory where copies of the latest namelist/text input files from the $RUNDIR are stored. These exist only to help document the case setup and run.

LockedFiles

is the directory that holds copies of the locked files.

MachinesHist

is a directory where previous case configurations are stored. In other words, when configure -clean is run, the current configured scripts are copied into this directory, so when configure -case is subsequently run, there is an opportunity to review and compare previous setups.

Macros.$MACH

is the Makefile Macros file for the current configuration. The Makefile is located in the Tools directory and is identical on all machines. The Macros file is a machine and compiler dependent file. This file is locked during the build step.

README.case

provides a summary of the commands used to generate this case.

SourceMods

contains directories for each component where case specific source code modifications can be included. The source files in these directories will always be used in preference to the source code in CCSMROOT. This feature allows users to modify CCSM source code on a case by case basis if that preferable over making modifications in the CCSMROOT sandbox.

$CASE.$MACH.build

is the script that is run interactively to build the CCSM model.

$CASE.$MACH.clean_build

is the script that cleans the CCSM build.

$CASE.$MACH.l_archive

is the script that is submitted to the batch queue to archive CCSM data to the long-term archive disk, like an hpss or mass storage system.

$CASE.$MACH.run

is the script that is submitted to the batch queue to run a CCSM job. This script could also be run interactively if resources allow.

check_input_data

is a tool that checks for missing input datasets and provides a capability for exporting them to local disk.

configure

is the script that is run to generate files in Buildconf and the build and run scripts for a case.

create_production_test

is a tool that generates an exact restart test in a separate directory based on the current case.

env_*.xml files

contain variables used to setup, configure, build, and run CCSM.

logs

is a directory that contains a copy of the component log files from successful case runs.

timing

is a directory that contains timing output from each successful case run.

xmlchange

is a script that supports changing xml variables in the env files.

$CASEROOT/Tools

contains many scripts that are used to setup and configure the CCSM model as well as run it. Some of particular note are