GEOS-5

Running ADAS: Difference between revisions

← Older edit
Pchakrab (talk | contribs)
1,048 edits
Pchakrab (talk | contribs)
1,048 edits
 
(37 intermediate revisions by the same user not shown)
Line 1: Line 1:
==DAS assimilation and forecast runs==
==ADAS run==
===Select DAS experiment to run===


First, we choose a DAS run to simulate. For a list of runs
===Build model===
$ ls ~dao_ops
First, choose a model tag to build. For this example, we choose GEOSadas-5_9_1_p7.
on NCCS discover. As an example, we choose the run <tt>d591_fpit</tt> (for more about GMAO products, please see https://gmao.gsfc.nasa.gov/products)
 
Look for ATAG in file <tt>~dao_ops/d591_fpit/run/FVDAS_Run_Config</tt>
$ grep ATAG ~dao_ops/d591_fpit/run/FVDAS_Run_Config
setenv ATAG    GEOSadas-5_9_1_p7


This gives us the model tag.
$ cvs co -P -r GEOSadas-5_9_1_p7 -d g591p8 GEOSadas-5_9


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


$ cvs co -P -r GEOSadas-5_9_1_p7 -d g591p7 GEOSadas-5_9
  $ cd g591p8/src
  $ cd g591p7/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):
[For now we choose the default value for FVICS as well]
[we choose the default value for the initial conditions (FVICS) as well]
 
  AGCM Resolution? [b72]
  AGCM Resolution? [b72]
  > C180
  > C180
Line 30: Line 23:
   
   
  EXPID? [u000_C180]
  EXPID? [u000_C180]
  > g591p7ops
  > g591p8
   
   
  OBSERVING SYSTEM CLASSES?
  OBSERVING SYSTEM CLASSES?
  > ncep_prep_bufr
  > "ncep_prep_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,
    disc_airs_bufr,disc_amsua_bufr,ncep_mhs_bufr,ncep_1bhrs4_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"
-->
Do Aerosol Analysis (y/n)? [y]
> n
 
One can, of course, turn on Aerosol Analysis and AOD assimilation here.


A pdf of the entire <tt>fvsetup</tt> session is provided here: [[File: Fvsetup_session.pdf]].
A pdf of an example <tt>fvsetup</tt> session is provided here: [[Media:Fvsetup_session.pdf|fvsetup_session]].


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


Line 54: Line 59:
  run/        resource files
  run/        resource files


Some of these directories are stored in the archive. After running one cycle look in <tt>$ARCHIVE/g591p7ops</tt> (where <tt>g591p7ops</tt> is the experiment ID).
<tt>$FVHOME/.FVROOT</tt> gives the location of the installation <tt>bin</tt> directory.


Move to the experiment directory
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).
$ cd $NOBACKUP/g591p4_d72/run


At this point, one can edit CAP.rc.tmpl to run 12-hour experiment. Also, one can turn on MAPL timers and memutils
====Run directory====
$ cd $FVHOME/run


JOB_SGMT:    0 120000
<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'.
NUM_SGMT:    1
<!--
To simulate the OPS run d591_fpit, we make a few changes:
MAPL_ENABLE_TIMERS: YES
# NX, NY in AGCM.rc.tmpl and AGCM.BOOTSTRAP.rc.tmpl have the same values (8, 48) as in the OPS run
MAPL_ENABLE_MEMUTILS: YES
# Copy HISTORY.rc.tmpl over from the OPS run
 
# Copy obsys.rc over from the OPT run
To run one segment each of <tt>GSIsa.x</tt> and <tt>GEOSgcm.x</tt> add '<tt>exit</tt>' before 'PART IV - Next PBS Job Segment' in <tt>g5das.j</tt>.
# 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
# <tt>g5das.j</tt>
## PBS -l select=32
## <tt>setenv NCPUS    384</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'
-->


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


  $ cd $NOBACKUP/g591p4_d72/run
  $ cd $FVHOME/run
  $ qsub g5das.j
  $ qsub g5das.j


<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===
====Forecast experiment====
 
Later.
==Simulating OPS run==
<!--EVERYTHING BELOW IS COMMENTED OUT


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


-->
-->


[[Category:SI Team]]
[[Category:SI Team]]
[[Category:Running the Model]]
[[Category:Running the Model]]
Retrieved from "https://geos5.org/wiki/index.php?title=Running_ADAS"