[Dart-dev] DART/releases Revision: 11400
dart at ucar.edu
dart at ucar.edu
Fri Mar 24 16:38:14 MDT 2017
thoar at ucar.edu
2017-03-24 16:38:14 -0600 (Fri, 24 Mar 2017)
230
Referencing things with the proper local syntax.
The index.html has been updated to reflect the files in the Manhattan release.
Removed references to dart_to_model, etc, added new program references
to the list of programs, etc.
Index: DART/releases/Manhattan
===================================================================
--- DART/releases/Manhattan 2017-03-24 22:35:28 UTC (rev 11399)
+++ DART/releases/Manhattan 2017-03-24 22:38:14 UTC (rev 11400)
Property changes on: DART/releases/Manhattan
___________________________________________________________________
Modified: svn:mergeinfo
## -28,7 +28,7 ##
/DART/branches/rma_sprint:8101-8172
/DART/branches/rma_state_structure_test_dir:9478-9682
/DART/branches/rma_state_structure_unit_test:9697-10274
-/DART/branches/rma_trunk:11355-11383
+/DART/branches/rma_trunk:11355-11399
/DART/branches/rma_trunk_clamping:8792-8807
/DART/branches/rma_trunk_filename:8017-8163
/DART/branches/rma_trunk_get_state_fun:8574-8602
Modified: DART/releases/Manhattan/assimilation_code/programs/closest_member_tool/closest_member_tool.html
===================================================================
--- DART/releases/Manhattan/assimilation_code/programs/closest_member_tool/closest_member_tool.html 2017-03-24 22:35:28 UTC (rev 11399)
+++ DART/releases/Manhattan/assimilation_code/programs/closest_member_tool/closest_member_tool.html 2017-03-24 22:38:14 UTC (rev 11400)
@@ -195,7 +195,7 @@
generic kinds, such as QTY_TEMPERATURE, QTY_U_WIND_COMPONENT, QTY_DENSITY,
etc. and not specific types like RADIOSONDE_TEMPERATURE. Consult the model
interface code to determine which possible kinds are returned by the
-<a href="../../models/model_mod.html#get_state_meta_data">get_state_meta_data()</a>
+<a href="../../../models/template/model_mod.html#get_state_meta_data">get_state_meta_data()</a>
routine.
</TD></TR>
Modified: DART/releases/Manhattan/assimilation_code/programs/filter/filter.html
===================================================================
--- DART/releases/Manhattan/assimilation_code/programs/filter/filter.html 2017-03-24 22:35:28 UTC (rev 11399)
+++ DART/releases/Manhattan/assimilation_code/programs/filter/filter.html 2017-03-24 22:38:14 UTC (rev 11400)
@@ -91,12 +91,10 @@
</P>
<UL><LI>Link to an observation sequence file which contains only observation times
within the next assimilation window </LI>
- <LI>Convert the latest model output files to DART format</LI>
<LI>Link any output inflation files from the previous step to be
the input files for this step</LI>
<LI>Run filter, which will exit after doing the assimilation without trying
to advance the model</LI>
- <LI>Convert the filter output to be model input</LI>
<LI>Save the output diagnostic files for later</LI>
<LI>Advance the N copies of the model using the model scripts or whatever
method is appropriate</LI>
@@ -112,15 +110,29 @@
<P>
The same source code is used for all applications of filter.
The code specific to the types of observations and the interface code
- for the computational model is configured at compile time.
- The DART directory structure is arranged slightly differently than usual
- in that the main code is spread across a dozen directories
- at the top level, e.g. the filter source code is in DART/filter/filter.f90.
- Each model has a separate directory under DART/models, and under each model
- is a work directory where the code is compiled and can be run for testing.
- Generally when a full-size experiment is done the executables are copied
- to a different location - e.g. scratch space on a large filesystem - since the
- data files for 10s to 100s of copies of a model can get very large.
+ for the computational model is configured at compile time. The directory
+ has been simplified from previous version to look like :
+
+ <ul><li> <em class=file>README</em> </li>
+ <li> <em class=file>COPYRIGHT</em> </li>
+ <li> <em class=dir >assimilation_code</em> </li>
+ <li> <em class=dir >build_templates</em> </li>
+ <li> <em class=dir >diagnostics</em> </li>
+ <li> <em class=dir >documentation</em> </li>
+ <li> <em class=dir >models</em> </li>
+ <li> <em class=dir >observations</em> </li>
+ </ul>
+
+ the <em class=dir >assimilation_code</em> contains all
+ <em class=dir >module</em> and <em class=dir >program</em> souce code for
+ all of the main programs including filter. Specifically in the modules
+ directory there is a <em class=file >filter_mod.f90</em> which contains the souce for the
+ filter main program. Each model has a separate directory under DART/models,
+ and under each model is a work directory where the code is compiled and
+ can be run for testing. Generally when a full-size experiment is done the
+ executables are copied to a different location - e.g. scratch space on a
+ large filesystem - since the data files for 10s to 100s of copies of a model
+ can get very large.
</P>
<A NAME="FilterTypes"></A>
@@ -151,7 +163,7 @@
you assimilate exactly one observation, with no model advance,
with inflation turned off, with a large cutoff, and with the
outlier threshold off (see below for how to set these namelist
-items). Run an assimilation. Look at the obs_seq.final file
+items). Run an assimilation. Look at the <em class=file>obs_seq.final</em> file
to see what the forward operator computed. Use ncdiff to difference
the Prior and Posterior Diag NetCDF files and look at the changes
(the "innovations") in the various model fields. Is it in the right
@@ -302,7 +314,7 @@
list in the <em class="code">&obs_kind_nml</em>
section of the namelist, and none in the assimilation list.
Run filter as usual, including model advances if needed.
- Run observation diagnostics on the resulting obs_seq.final file to
More information about the Dart-dev
mailing list