Running ADAS: Difference between revisions

From GEOS-5
Jump to navigation Jump to search
Pchakrab (talk | contribs)
Pchakrab (talk | contribs)
No edit summary
Line 4: Line 4:
First, choose a model tag to build. For this example, we choose GEOSadas-5_9_1_p7.
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 g591p7 GEOSadas-5_9
  $ cvs co -P -r GEOSadas-5_9_1_p7 -d g591p8 GEOSadas-5_9


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


  $ cd g591p7/src
  $ cd g591p8/src
  $ ./parallel_build.csh
  $ ./parallel_build.csh


===Setup experiment (Run <tt>fvsetup</tt>)===
===Setup experiment (Run <tt>fvsetup</tt>)===


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


Line 23: Line 23:
   
   
  EXPID? [u000_C180]
  EXPID? [u000_C180]
  > g591p7
  > g591p8
   
   
  OBSERVING SYSTEM CLASSES?
  OBSERVING SYSTEM CLASSES?
Line 59: Line 59:
<tt>$FVHOME/.FVROOT</tt> gives the location of the installation <tt>bin</tt> directory.
<tt>$FVHOME/.FVROOT</tt> gives the location of the installation <tt>bin</tt> directory.


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


====Run directory====
====Run directory====

Revision as of 08:13, 29 March 2013

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

A pdf of the entire fvsetup session is provided here: File:Fvsetup session.pdf.

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.