Running ADAS: Difference between revisions
| Line 1: | Line 1: | ||
== | ==ADAS assimilation run== | ||
First, | ===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 g591p7 GEOSadas-5_9 | |||
$ | |||
Not the module name <tt>GEOSadas-5_9</tt>. Unlike AGCM, all ADAS tags have a corresponding module. | |||
$ cd g591p7/src | $ cd g591p7/src | ||
$ ./parallel_build.csh | $ ./parallel_build.csh | ||
| Line 22: | Line 14: | ||
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>g591p7/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] | ||
AGCM Resolution? [b72] | AGCM Resolution? [b72] | ||
> C180 | > C180 | ||
| Line 33: | Line 26: | ||
OBSERVING SYSTEM CLASSES? | OBSERVING SYSTEM CLASSES? | ||
<!-- | |||
> "ncep_1bamua_bufr,ncep_1bamub_bufr,ncep_1bhrs2_bufr,ncep_1bhrs3_bufr, | > "ncep_1bamua_bufr,ncep_1bamub_bufr,ncep_1bhrs2_bufr,ncep_1bhrs3_bufr, | ||
ncep_1bmsu_bufr,ncep_osbuv_bufr,ncep_prep_bufr,ncep_sptrmm_bufr, | ncep_1bmsu_bufr,ncep_osbuv_bufr,ncep_prep_bufr,ncep_sptrmm_bufr, | ||
| Line 38: | Line 32: | ||
ncep_amsre_bufr,ncep_goesfv_bufr,ncep_mtiasi_bufr,ncep_gpsro_bufr, | ncep_amsre_bufr,ncep_goesfv_bufr,ncep_mtiasi_bufr,ncep_gpsro_bufr, | ||
aura_omi_bufr,ncep_satwnd_bufr,ncep_atms_bufr,ncep_sevcsr_bufr" | aura_omi_bufr,ncep_satwnd_bufr,ncep_atms_bufr,ncep_sevcsr_bufr" | ||
--> | |||
A pdf of the entire <tt>fvsetup</tt> session is provided here: [[File: Fvsetup_session.pdf]]. | A pdf of the entire <tt>fvsetup</tt> session is provided here: [[File: Fvsetup_session.pdf]]. | ||
Revision as of 08:05, 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 g591p7 GEOSadas-5_9
Not the module name GEOSadas-5_9. Unlike AGCM, all ADAS tags have a corresponding module.
$ cd g591p7/src $ ./parallel_build.csh
Setup experiment (Run fvsetup)
Run fvsetup from the bin directory (g591p7/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] > g591p7ops OBSERVING SYSTEM CLASSES?
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 running one cycle look in $ARCHIVE/g591p7ops (where g591p7ops is the experiment ID).
Run directory
$ cd $FVHOME/run
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
- Copy HISTORY.rc.tmpl over from the OPS run
- Copy obsys.rc over from the OPT run
- NX, NY in GSI_GridComp.rc.tmpl should match those from the OPS run (6, 36)
- Set NUM_SGMT to 1 in CAP.rc.tmpl
- g5das.j
- PBS -l select=32
- setenv NCPUS 384
- setenv NCPUS_GSI 216
- One cycle: To run one segment each of GSIsa.x and GEOSgcm.x add 'exit' before 'PART IV'
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.