RadApp

These instructions pertain to checking out, building, and using the RadApp tool, and offline instance of the GEOS-5 radiative transfer module written by Ben Auer.

How to Check Out and Build the Code

RadApp works with Ganymed and later versions of the GEOS-5 modeling system, and presumes access to an existing build of that system. Please see instructions at (link to Ganymed build section) for how to check out and build your own version of GEOS-5. You can also (see below) link to another existing build of GEOS-5 to set up the RadApp tool.

In this example I will use a build of the GEOS-5 tag prc+Ganymed-4_0_BETA1.

Check Out and Build the RadApp Code

Somewhere (probably your nobackup space on discover) you will check out the code:

% cvs co -d RadApp GEOSdiag_App

This will create a directory called RadApp and check out the module GEOSdiag_App into it. To build, set an environment variable ESMADIR to point to the existing build of GEOS-5. For example:

% setenv ESMADIR /discover/nobackup/pcolarco/Ganymed-4_0/GEOSagcm

and then:

% source $ESMADIR/Linux/bin/g5_modules

to set up the compiler and modules. And then in your RadApp directory just:

% gmake install

The GEOS-5 (AGCM) source code checks out at about 55 MB of space. Once compiled, the complete package is about 1.3 GB. Your home space on discover may not be sufficient for checking out and building the code. You should consider either 1) requesting a larger quota in your home space (call the tag x6-9120 and ask, telling them you are doing GEOS-5 development work) or 2) building in your (larger) nobackup space (recommended). But consider, nobackup is not backed up. So be careful...

One strategy I like is to check the code out to my nobackup space, but then make symlink from him home space back to that. For example, if I have my code stored at $NOBACKUP/GEOSagcm, I would make a symlink in my home space to point to that like:

% ln -s $NOBACKUP/GEOSagcm GEOSagcm