Running ADAS: Difference between revisions

From GEOS-5
Jump to navigation Jump to search
Pchakrab (talk | contribs)
Pchakrab (talk | contribs)
 
(19 intermediate revisions by the same user not shown)
Line 1: Line 1:
==ADAS assimilation run==
==ADAS run==


===Build model===
===Build model===
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?
  > "ncep_1bamua_bufr"
  > "ncep_prep_bufr"
<!--
<!--
  > "ncep_1bamua_bufr,ncep_1bamub_bufr,ncep_1bhrs2_bufr,ncep_1bhrs3_bufr,
  > "ncep_1bamua_bufr,ncep_1bamub_bufr,ncep_1bhrs2_bufr,ncep_1bhrs3_bufr,
Line 34: Line 34:
     aura_omi_bufr,ncep_satwnd_bufr,ncep_atms_bufr,ncep_sevcsr_bufr"
     aura_omi_bufr,ncep_satwnd_bufr,ncep_atms_bufr,ncep_sevcsr_bufr"
-->
-->
Do Aerosol Analysis (y/n)? [y]
> n


A pdf of the entire <tt>fvsetup</tt> session is provided here: [[File: Fvsetup_session.pdf]].
One can, of course, turn on Aerosol Analysis and AOD assimilation here.
 
A pdf of an example <tt>fvsetup</tt> session is provided here: [[Media:Fvsetup_session.pdf|fvsetup_session]].


====FVHOME====
====FVHOME====
Line 56: Line 61:
<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 (<tt>ana/</tt>, <tt>chem/</tt>, <tt>diag/</tt>, <tt>etc/</tt>, <tt>obs/</tt>, <tt>rs/</tt>) 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====
  $ cd $FVHOME/run
  $ cd $FVHOME/run


<tt>g5das.j</tt> is the job submission script. The number of cpus etc. can be changed here (if they haven't already been changed during setup). Also, if you want to run a single cycle of <tt>GSIsa.x</tt> & <tt>GEOSgcm.x</tt> add <tt>exit</tt> right before 'PART IV'.
<!--
To simulate the OPS run d591_fpit, we make a few changes:
To simulate the OPS run d591_fpit, we make a few changes:
# NX, NY in AGCM.rc.tmpl and AGCM.BOOTSTRAP.rc.tmpl have the same values (8, 48) as in the OPS run
# NX, NY in AGCM.rc.tmpl and AGCM.BOOTSTRAP.rc.tmpl have the same values (8, 48) as in the OPS run
Line 72: Line 79:
## <tt>setenv NCPUS_GSI 216</tt>
## <tt>setenv NCPUS_GSI 216</tt>
## '''One cycle''': To run one segment each of GSIsa.x and GEOSgcm.x add '<tt>exit</tt>' before 'PART IV'
## '''One cycle''': To run one segment each of GSIsa.x and GEOSgcm.x add '<tt>exit</tt>' before 'PART IV'
-->


===Data Assimilation experiment===
===Data Assimilation===


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


===Forecast===
==Simulating OPS run==
<!--EVERYTHING BELOW IS COMMENTED OUT
<!--EVERYTHING BELOW IS COMMENTED OUT
====Forecast experiment====
Later.


==Simulating DAS forecast run==
==Simulating DAS forecast run==
Line 164: Line 173:


-->
-->


[[Category:SI Team]]
[[Category:SI Team]]
[[Category:Running the Model]]
[[Category:Running the Model]]

Latest revision as of 09:38, 29 March 2013

ADAS 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.

A pdf of an example fvsetup session is provided here: fvsetup_session.

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 (ana/, chem/, diag/, etc/, obs/, rs/) are stored in the archive. After completing the experiment, look in $ARCHIVE/g591p8 (where g591p8 is the experiment ID).

Run directory

$ cd $FVHOME/run

g5das.j is the job submission script. The number of cpus etc. can be changed here (if they haven't already been changed during setup). Also, if you want to run a single cycle of GSIsa.x & GEOSgcm.x add exit right before 'PART IV'.

Data Assimilation

$ 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.

Forecast

Simulating OPS run