The Community Earth System Model

See the CESM web site for documentation and information:

http://www.cesm.ucar.edu

The CESM Quickstart Guide is available at:

http://escomp.github.io/cesm

This repository provides tools for managing the external components that make up a CESM tag - alpha, beta and release. CESM tag creation should be coordinated through CSEG at NCAR.

This repository is also connected to slack at http://cesm2.slack.com

Contents

• 1   Software requirements
  • 1.1   Software requirements for installing, building and running CESM
  • 1.2   Details on Fortran compiler versions
  • 1.3   More details on porting CESM
• 2   Obtaining the full model code and associated scripting infrastructure
  • 2.1   More details on git fleximod
• 3   Customizing your CESM sandbox
  • 3.1   Switching to a different CESM tag
  • 3.2   Pointing to a different version of a component
    • 3.2.1   Committing your change to .gitmodules
  • 3.3   Modifying a component
• 4   Developer setup

1   Software requirements

1.1   Software requirements for installing, building and running CESM

Installing, building and running CESM requires:

• a Unix-like operating system (Linux, AIX, OS X, etc.)
• git client version 1.8 or newer
• python3 version 3.8 or newer
• perl version 5
• build tools gmake and cmake
• Fortran and C compilers
  • See Details on Fortran compiler versions below for more information
• LAPACK and BLAS libraries
• a NetCDF library version 4.3 or newer built with the same compiler you will use for CESM
  • a PnetCDF library is optional, but recommended
• a functioning MPI environment (unless you plan to run on a single core with the CIME mpi-serial library)

1.2   Details on Fortran compiler versions

The Fortran compiler must support Fortran 2003 features. However, even among mainstream Fortran compilers that claim to support Fortran 2003, we have found numerous bugs. Thus, many compiler versions do not build or run CESM properly (see https://wiki.ucar.edu/display/ccsm/Fortran+Compiler+Bug+List for more details on older Fortran compiler versions).

CESM2 is tested on several different systems with newer Fortran compilers: Please see CESM Compiler/Machine Tests for a spreadsheet of the current results.

1.3   More details on porting CESM

For more details on porting CESM to a new machine, see http://esmci.github.io/cime/users_guide/porting-cime.html

2   Obtaining the full model code and associated scripting infrastructure

CESM is now released via github. You will need some familiarity with git in order to modify the code and commit these changes. However, to simply checkout and run the code, no git knowledge is required other than what is documented in the following steps.

To obtain the CESM code you need to do the following:

1. Clone the repository.

   git clone https://github.com/escomp/cesm.git my_cesm_sandbox
   

   This will create a directory my_cesm_sandbox/ in your current working directory.

2. Go into the newly created CESM repository and determine what version of CESM you want. To see what cesm tags are available, simply issue the git tag command.

   cd my_cesm_sandbox
   git tag
   

3. Do a git checkout of the tag you want. If you want to checkout cesm3_0_beta02, you would issue the following.

   git checkout cesm3_0_beta02
   

   (It is normal and expected to get a message about being in 'detached HEAD' state. For now you can ignore this, but it becomes important if you want to make changes to your Externals.cfg file and commit those changes to a branch.)

4. Run the script bin/git-fleximod update.

   ./bin/git-fleximod update
   

   The git fleximod script is a git extension that will populate the cesm directory with the relevant versions of each of the components along with the CIME infrastructure code.

At this point you have a working version of CESM.

To see full details of how to set up a case, compile and run, see the CIME documentation at http://esmci.github.io/cime/ .

2.1   More details on git fleximod

The file .gitmodules in your top-level CESM directory tells git fleximod which tag/branch of each component should be brought in to generate your sandbox.

NOTE: git fleximod will always attempt to make the working copy exactly match the externals description. For example, if you manually modify an external without updating .gitmodules, (e.g. switch to a different tag), then rerunning git fleximod will warn you and can restore the original version by using the --force option below documentation Customizing your CESM sandbox for more details.

You need to rerun git-fleximod update whenever .gitmodules has changed (unless you have already manually updated the relevant external(s) to have the correct branch/tag checked out). Common times when this is needed are:

• After checking out a new CESM branch/tag
• After merging some other CESM branch/tag into your currently checked-out branch

To see more details of git-fleximod, issue

./bin/git-fleximod --help

3   Customizing your CESM sandbox

There are several use cases to consider when you want to customize or modify your CESM sandbox.

3.1   Switching to a different CESM tag

If you have already checked out a tag and HAVE NOT MADE ANY MODIFICATIONS it is simple to change your sandbox. Say that you checked out cesm3_0_beta01 but really wanted to have cesm3_0_beta02 you would simply do the following:

git checkout cesm3_0_beta02
./bin/git-fleximod update

You should not use this method if you have any ongoing CESM cases that were created from this sandbox. In these cases, it is often easiest to do a second git clone.

3.2   Pointing to a different version of a component

Each entry in .gitmodules has the following form (we use CAM as an example below):

[submodule "cam"]
  path = components/cam
  url = https://www.github.com/ESCOMP/CAM
  fxDONOTUSEurl = https://www.github.com/ESCOMP/CAM
  fxtag = cam6_4_016
  fxrequired = ToplevelRequired

Each entry specifies either a tag or a hash. To point to a new tag:

1. Modify the relevant fxtag entry/entries in .gitmodules (e.g., changing cam6_4_016 to cam6_4_017 above)

2. Checkout the new component(s):

   ./bin/git-fleximod update cam
   

Keep in mind that changing individual components from a tag may result in an invalid model (won't compile, won't run, not scientifically meaningful) and is unsupported.

3.2.1   Committing your change to .gitmodules

After making this change, it's a good idea to commit the change in your local CESM git repository. First create a CESM branch in your local repository, then commit it. For example:

git checkout -b my_cesm_branch
git add .gitmodules components/cam
git commit -m "Update CAM to cam5_4_144"

3.3   Modifying a component

If you'd like to modify a component via a branch and point to that branch in your CESM sandbox, use the following procedure (again, using CAM as an example):

1. Create a CAM branch. Let's assume you have created this branch and called it my_branch.

2. Update .gitmodules to point to a hash on your branch. You can replace the tag entry with a hash entry, as follows, note that we have also changed the url to point to a personal fork:

   [submodule "cam"]
     path = components/cam
     url = https://www.github.com/mycamfork/CAM
     fxDONOTUSEurl = https://www.github.com/ESCOMP/CAM
     fxtag = 94eaf83
     fxrequired = ToplevelRequired
   

3. Checkout your branch:

   ./bin/git-fleximod update cam
   

It's a good idea to commit your .gitmodules file changes. See the above documentation, Committing your change to .gitmodules.

4   Developer setup

Developers who have not already done so should follow the recommended one-time setup directions for git. Developers may also want to set up ssh keys and switch to using the [email protected]:ESCOMP/cesm.git form of the github URLs.