Running ADAS: Difference between revisions

(17 intermediate revisions by the same user not shown)

Line 1:

==ADAS ~~assimilation~~ run==

==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 ~~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.

$ cd ~~g591p7~~/src

$ cd g591p8/src

$ ./parallel_build.csh

===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]

Line 23:

EXPID? [u000_C180]

> ~~g591p7~~

> g591p8

OBSERVING SYSTEM CLASSES?

Line 34:

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====

Line 56:

Line 61:

<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====

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

Line 75:

Line 81:

-->

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

===Data Assimilation===

$ cd $FVHOME/run

Line 82:

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

===Forecast===

==Simulating OPS run==

<!--EVERYTHING BELOW IS COMMENTED OUT

~~====Forecast experiment====~~

~~Later.~~

==Simulating DAS forecast run==

Line 166:

Line 173:

-->

[[Category:SI Team]]

[[Category:Running the Model]]

@@ Line 1: / Line 1: @@
-==ADAS assimilation run==
+==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 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.
-  $ cd g591p7/src
+  $ cd g591p8/src
   $ ./parallel_build.csh
 ===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]
@@ Line 23: / Line 23: @@
   EXPID? [u000_C180]
-  > g591p7
+  > g591p8
   OBSERVING SYSTEM CLASSES?
@@ Line 34: / Line 34: @@
      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====
@@ Line 56: / Line 61: @@
 <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====
   $ 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:
@@ Line 75: / Line 81: @@
 -->
-===Data Assimilation experiment===
+===Data Assimilation===
   $ cd $FVHOME/run
@@ Line 82: / 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>.
+===Forecast===
+==Simulating OPS run==
 <!--EVERYTHING BELOW IS COMMENTED OUT
-====Forecast experiment====
-Later.
 ==Simulating DAS forecast run==
@@ Line 166: / Line 173: @@
 -->
 [[Category:SI Team]]
 [[Category:Running the Model]]