Running ADAS

ADAS assimilation run

Build model

First, choose a model tag to build. For this example, we choose GEOSadas-5_9_1_p7.

$ cvs co -P -r GEOSadas-5_9_1_p7 -d g591p8 GEOSadas-5_9

Not the module name GEOSadas-5_9. Unlike AGCM, all ADAS tags have a corresponding module.

$ cd g591p8/src
$ ./parallel_build.csh

Setup experiment (Run fvsetup)

Run fvsetup from the bin directory (g591p8/Linux/bin) with the following options (default value chosen for ones not mentioned): [we choose the default value for the initial conditions (FVICS) as well]

AGCM Resolution? [b72]
> C180

OGCM Resolution? [c34]
> f34

EXPID? [u000_C180]
> g591p8

OBSERVING SYSTEM CLASSES?
> "ncep_prep_bufr"

Do Aerosol Analysis (y/n)? [y]
> n

One can, of course, turn on Aerosol Analysis and AOD assimilation here.

FVHOME

FVHOME is the home directory for fvDAS experiment. Resource files, restarts and system output will be stored under this directory. Usually it contains subdiretories:

ana/        first guess/analysis output
anasa/      job script to run stand-alone analysis
daotovs/    daotovs field output
diag/       diagnostic field output
etc/        listings and other odds & ends
fcst/       forecast run directory
fvInput/    process required inputs
obs/        post-analysis ODS files
prog/       prognostic field output
recycle/    latest restart files
rs/         restart files
run/        resource files

$FVHOME/.FVROOT gives the location of the installation bin directory.

Some of these directories are stored in the archive. After completing the experiment, look in $ARCHIVE/g591p8 (where g591p8 is the experiment ID).

Run directory

$ cd $FVHOME/run

Data Assimilation experiment

$ cd $FVHOME/run
$ qsub g5das.j

g5das creates a scratch directory $NOBACKUP/fvwork.xxxx and runs the experiment there. After the initial setup, GSIsa.x is run with output written to ana.log followed by GEOSgcm.x which writes its output to stdout and fvpsas.log.