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-3_0 and later versions of the GEOS-5 modeling system, and presumes access to an existing build of that system. (I suggest Ganymed-4 or later because updates made to MAPL in Ganymed-3 mean not all versions of Ganymed-3 work.) 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

That's it, we've built the code!

What is Needed to Run the Module?

The RadApp tool utilizes much of the underlying GEOS-5 infrastructure to function. For example, you use the usual HISTORY structure to generate output files. Additionally, RadApp requires inputs. These inputs use EXTDATA. So we need to provide certain resource files and input data in order to actually run the calculation.