GEOS GCM Documentation and Access

This page describes the minimum steps required to checkout GEOS GCM.

NOTE NOTE NOTE: This is only to get the code for the GEOS GCM. If you wish to use the production output from GEOS as run at the GMAO, please refer to the GMAO page on GEOS products.

Checking Out GEOS GCM using Git

The commands below assume that you have git 2.x installed on your machine.

The first thing you need to do is to register in the GEOS trac system using the following link:

https://github.com/GEOS-ESM/GEOSgcm

The code is publicly available, but in order to contribute to the GEOS GCM development, you will need to be added as a collaborator with the GEOS-ESM organization. Please send an email to GEOS Support with your GitHub username. You can create tickets through the GitHub issue system and contribute to the code.

Building GEOS

NOTE: GMAO does not generally support building or running GEOS on systems other than on NASA Supercomputers.

GEOS GCM can be built, but you will need a variety of programs. An F90 compiler (Intel and GCC are supported and tested) and an MPI stack (Open MPI, Intel MPI, MVAPICH2, and SGI MPT have been tested). Beyond that, you'll also need the ESMA Baselibs, a collection of base libraries for GEOS which include HDF5, netCDF-C, netCDF-Fortran, ESMF, and more. Note that while these can be built individually, GEOS at present expects the libraries to be bundled in a specific way (directory-wise) to work.

Boundary Conditions

Boundary conditions are available at NCCS, NAS, and on GMAO Desktops (limited to very low-res).

A minimal, small set of boundary conditions of approximately 300 MB (4-degree resolution or coarser, probably could only run a few model days) have been made and could possibly be distributed if needed. Contact Matthew Thompson for further inquiries.