<p><b>xinzhang</b> 2009-04-05 23:32:31 -0600 (Sun, 05 Apr 2009)</p><p>Close to release V3.1, Chap 6 updated.<br>
</p><hr noshade><pre><font color="gray">Modified: trunk/wrf/UsersGuide/users_guide_chap6.doc
===================================================================
--- trunk/wrf/UsersGuide/users_guide_chap6.doc 2009-04-06 01:00:35 UTC (rev 179)
+++ trunk/wrf/UsersGuide/users_guide_chap6.doc 2009-04-06 05:32:31 UTC (rev 180)
@@ -1,5 +1,5 @@
-ࡱ
-
+
xlbc: lateral boundary from WPS/real output.
xa: analysis from WRF-Var data assimilation system.
xf: WRF forecast output.
-yo: observations processed by OBSPROC.
+yo: observations processed by OBSPROC. (note: Radar and Radiance data dont go through OBSPROC)
B0: background error statistics from generic be.data/gen_be.
R: observational and representativeness data error statistics.
In this chapter, you will learn how to run the various components of WRF-Var system. For the training purpose, you are supplied with a test case including the following input data: a) observation file (in the format prior to OBSPROC), b) WRF NetCDF background file (WPS/real output used as a first guess of the analysis), and c) Background error statistics (estimate of errors in the background file). You can download the test dataset from HYPERLINK "http://www.mmm.ucar.edu/wrf/users/wrfda/download/testdata.html" http://www.mmm.ucar.edu/wrf/users/wrfda/download/testdata.html. In yo
ur own work, you have to create all these input files yourselves. See the section HYPERLINK \l "_Running_Observation_Preprocessor_1" Running Observation Preprocessor for creating your observation files. See section HYPERLINK \l "_Running_gen_be_1" Running gen_be for generating your background error statistics file if you want to use cv_options=5.
Before using your own data, we suggest that you start by running through the WRF-Var related programs at least once using the supplied test case. This serves two purposes: First, you can learn how to run the programs with data we have tested ourselves, and second you can test whether your computer is adequate to run the entire modeling system. After you have done the tutorial, you can try running other, more computationally intensive, case studies and experimenting with some of the many namelist variables.
-WARNING: It is impossible to test every code upgrade with every permutation of computer, co
mpiler, number of processors, case, namelist option, etc. Th!
e namel
ist options that are supported are indicated in the WRFDA/Registry/Registry.wrfvar and these are the default options.
+WARNING: It is impossible to test every code upgrade with every permutation of computer, compiler, number of processors, case, namelist option, etc. The namelist options that are supported are indicated in the WRFDA/var/README.namelist and these are the default options.
Running with your own domain. Hopefully, our test cases will have prepared you for the variety of ways in which you may wish to run WRF-Var. Please let us know your experiences.
As a professional courtesy, we request that you include the following reference in any publications that makes use of any component of the community WRF-Var system:
@@ -116,15 +116,16 @@
-rwxr-xr-x 1 noname users 1752352 Mar 23 09:29 var/obsproc/src/obsproc.exe
da_wrfvar.exe is the main executable for running WRF-Var. Make sure it is created after the compilation. Sometimes (unfortunately) it is possible that other utilities get successfully compiled, while the main da_wrfvar.exe fails; please check the compilation log file carefully to figure out the problem.
The basic gen_be utility for regional model consists of gen_be_stage0_wrf.exe, gen_be_stage1.exe, gen_be_stage2.exe, gen_be_stage2a.exe, gen_be_stage3.exe, gen_be_stage4_regional.exe, and gen_be_diags.exe.
-da_updated_bc.exe is used for updating WRF boundary condition after a new WRF-Var analysis is done.
+da_updated_bc.exe is used for updating WRF boundary condition after a new WRF-Var analysis is generated.
da_advance_time.exe is a very handy and useful tool for date/time manipulation. Type da_advance_time.exe to see its usage instruction.
-In addition to the executables for running WRF-Var,
gen_be, obsproc.exe is compiled too, which is used for preparing conventional data for WRF-Var.
+In addition to the executables for running WRF-Var and gen_be, obsproc.exe (the executable for preparing conventional data for WRF-Var) compilation is also included in ./compile all_wrfvar.
Installing WRFNL and WRFPLUS (For 4D-Var only)
If you intend to run WRF 4D-Var, it is necessary to have installed the WRFNL (WRF nonlinear model) and WRFPLUS (WRF adjoint and tangent linear model). WRFNL is a modified version of WRF V3.1 and can only be used for 4D-Var purposes. WRFPLUS contains the adjoint and tangent linear models based on a simplified WRF model, which only includes some simple physical processes such as vertical diffusion and large-scale condensation.
To install WRFNL:
Get the WRF zipped tar file from:
HYPERLINK "http://www.mmm.ucar.edu/wrf/users/download/get_source.html" http://www.mmm.ucar.edu/wrf/users/download/get_source.html
Unzip and untar
the file , name the directory WRFNL
+> cd WRFNL
> gzi!
p -cd WR
FV3.TAR.gz | tar -xf - ; mv WRFV3 WRFNL
Get the WRFNL patch zipped tar file from:
HYPERLINK "http://www.mmm.ucar.edu/wrf/users/wrfda/download/wrfnl.html" http://www.mmm.ucar.edu/wrf/users/wrfda/download/wrfnl.html
@@ -161,15 +162,14 @@
You should see wrfplus.exe
Running Observation Preprocessor (OBSPROC)
-The OBSPROC program reads observations in LITTLE_R format (a legendary ASCII format, in use since MM5 era). Please refer to the documentation at HYPERLINK "http://www.mmm.ucar.edu/mm5/mm5v3/data/how_to_get_rawdata.html" http://www.mmm.ucar.edu/mm5/mm5v3/data/how_to_get_rawdata.html for LITTLE_R format description. For your applications, you will have to prepare your own observation files. Please see HYPERLINK "http://www.mmm.ucar.edu/mm5/mm5v3/data/free_data.html" http://www.mmm.ucar.edu/mm5/mm5v3/data/free_data.html for the sources of some freely available observations and the program for converting the observations to LITTLE_R format. If you have observations in other various formats, a sample program (LITTLE_R/util/upa.f) for writing out data in LITTLE_R format can be obtained from HYPERLINK "ftp://ftp.ucar.edu/mesouser/MM5V3/V3-7-0/LITTLE_R.TAR.gz" ftp:
//ftp.ucar.edu/mesouser/MM5V3/V3-7-0/LITTLE_R.TAR.gz
-The basic operations performed by OBSPROC are:
+The OBSPROC program reads observations in LITTLE_R format (a legendary ASCII format, in use since MM5 era). Please refer to the documentation at HYPERLINK "http://www.mmm.ucar.edu/mm5/mm5v3/data/how_to_get_rawdata.html" http://www.mmm.ucar.edu/mm5/mm5v3/data/how_to_get_rawdata.html for LITTLE_R format description. For your applications, you will have to prepare your own observation files. Please see HYPERLINK "http://www.mmm.ucar.edu/mm5/mm5v3/data/free_data.html" http://www.mmm.ucar.edu/mm5/mm5v3/data/free_data.html for the sources of some freely available observations and the program for converting the observations to LITTLE_R format. Because the raw observation data files could be in any of formats, such as ASCII, BUFR, PREPBUFR, MADIS, HDF, etc. Further more, for each of formats, there may be the different versions. To make WRF-Var system a
s general as possible, the LITTLE_R format ASCII file was ad!
opted as
an intermediate observation data format for WRF-Var system. Some extensions were made in the LITTLE_R format for WRF-Var applications. More complete description of LITTLE_R format and conventional observation data sources for WRF-Var could be found from the web page: HYPERLINK "http://www.mmm.ucar.edu/wrf/users/wrfda/Tutorials/2009_Jan/tutorial_presentation_winter_2009.html" http://www.mmm.ucar.edu/wrf/users/wrfda/Tutorials/2009_Jan/tutorial_presentation_winter_2009.html by click Observation Pre-processing. The conversion of the user-specific-source data to the LITTLE_R format observation data file is a users task.
+The purposes of OBSPROC are:
Remove observations outside the time range and domain (horizontal and top).
Re-order and merge duplicate (in time and location) data reports.
Retrieve pressure or height based on observed information using the hydrostatic assumption.
Check vertical consistency and super adiabatic for multi-level observations.
As
sign observational errors based on a pre-specified error file.
Write out the observation file to be used by WRF-Var in ASCII or BUFR format.
-Plot the distribution of each observation type.
The OBSPROC programobsproc.exe should be found under the directory WRFDA/var/obsproc/src if compile all_wrfvar was completed successfully.
a. Prepare observational data for 3D-Var
To prepare the observation file, for example, at the analysis time 0h for 3D-Var, all the observations between 1h (or 1.5h) will be processed, as illustrated in following figure, which means that the observations between 23h and 1h are treated as the observations at 0h.
@@ -209,7 +209,7 @@
EACH_FMT = (3(F12.3,I4,F7.2),11X,3(F12.3,I4,F7.2),11X,3(F12.3,I4,F7.2))
#------------------------------------------------------------------------------#
observations
-Before running WRF-Var, you may like to learn more about various types of data that will be assimilated for this case, for example, their geographical distribution, etc. This file is in ASCII format and so you can easily view it. To have a graphical view about the content of this file, there is a MAP_plot utility to look at the data distribution for each type of observations. To use this utility, proceed as follows.
+Before running WRF-Var, you may like to learn more about various types of data that will be passed to WRF-Var for this case, for example, their geographical distribution, etc. This file is in ASCII format and so you can easily view it. To have a graphical view about the content of this file, there is a MAP_plot utility to look at the data distribution for each type of observations. T
o use this utility, proceed as follows.
> cd MAP_plot
> make
We have prepared some configure.user.ibm/linux/mac/ files for some platforms, when make is typed, the Makefile will use one of them to determine the compiler and compiler option. Please modify the Makefile and configure.user.xxx to accommodate the complier on your platform. Successful compilation will produce Map.exe. Note: The successful compilation of Map.exe requires pre-installed NCARG Graphics libraries under $(NCARG_ROOT)/lib.
@@ -224,13 +224,15 @@
> idt gmeta.2008020512
It will display (panel by panel) geographical distribution of various types of data. Following is the geographic distribution of sonde observations for this case.
+There is an alternative way to plot the observation by using ncl script: WRFDA/var/graphics/ncl/plot_ob_ascii_loc.ncl. However, with this way, you need to provide the first guess file to the ncl script, and have ncl installed in your system.
+
b. Prepare observational data for 4D-Var
-To prepare the observation file, for example, at the analysis time 0h for 4D-Var, all observations from 0h to 6h will be processed and grouped in 7 sub-windows from slot1 to slot7, as illustrated in following figure. NOTE: The Analysis time in the figure is not the actual analysis time (0h), it is only used for time_analysis in the namelist file, and is set to three hours later than the actual analysis time. The actual analysis time is still 0h.
+To prepare the observation file, for example, at th
e analysis time 0h for 4D-Var, all observations from 0h to 6h will be processed and grouped in 7 sub-windows from slot1 to slot7, as illustrated in following figure. NOTE: The Analysis time in the figure below is not the actual analysis time (0h), it just indicates the time_analysis setting in the namelist file, and is set to three hours later than the actual analysis time. The actual analysis time is still 0h.
An example file named namelist_obsproc.4dvar.wrfvar-tut has already been created in the var/obsproc directory. Thus, proceed as follows:
> cp namelist.obsproc.4dvar.wrfvar-tut namelist.obsproc
-In the namelist file, you need to change the following variables to accommodate your experiments. In this test case, the actual analysis time is 2008-02-05_12:00:00, but in namelist, the time_analysis should be set to 3 hours later.
+In the namelist file, you need to change the following variables to accommodate your experiments. In this test case, the actual an
alysis time is 2008-02-05_12:00:00, but in namelist, the tim!
e_analys
is should be set to 3 hours later. The different value of time_analysis will make the different number of time slots before and after time_analysis. For example, if you set time_analysis = 2008-02-05_16:00:00, and set the num_slots_past = 4 and time_slots_ahead=2. The final results will be same as before.
obs_gts_filename='obs.2008020512'
time_window_min = '2008-02-05_12:00:00',: The earliest time edge as ccyy-mm-dd_hh:mn:ss
time_analysis = '2008-02-05_15:00:00', : The analysis time as ccyy-mm-dd_hh:mn:ss
@@ -254,7 +256,7 @@
Running WRF-Var
a. Download Test Data
-The WRF-Var system requires three input files to run: a) A WRF first guess/boudary input format files output from either WPS/real (cold-start) or WRF (warm-start), b) Observations (in ASCII format or PREBUFR), and c) A background error statistics file (containing background error covariance).
+The WRF-Var system requires three input files to run: a) A WRF first guess/boudary input format files output from either WPS/real (cold-start) or WRF (warm-start), b) Observations (in ASCII format, PREBUFR or BUFR for radiance), and c) A background error statistics file (containing background error covariance).
The following table summarizes the above info:
Input DataFormatCreated ByFirst Guess
NETCDFWRF Preprocessing System (WPS) and real.exe
@@ -282,14 +284,14 @@
At this pont you have three of the input files (first guess, observation and background error statistics files in directory $DAT_DIR) required to run WRF-Var, and have successfully downloaded and compiled the WRF-Var code. If this is correct, we are ready to learn how to run WRF-Var.
b. Run The Case3D-Var
The data for this case is valid at 12 UTC 5th February 2008. The first guess comes from the NCEP global final analysis system (FNL), passed through the WRF-WPS and real programs.
-To run WRF-3D-Var, first create a working directory such as WRFDA/var/test/tutorial, and then follow the steps below:
+To run WRF-3D-Var, first create and cd to a working directory, for example, WRFDA/var/test/tutorial, and then follow the steps below:
> cd WRFDA/var/test/tutorial
> ln -sf WRFDA/run/LANDUSE.TBL ./LANDUSE.TBL
> ln -sf $DAT_DIR/rc/2008020512/wrfinput_d01 ./fg (link first guess file as fg)
> ln -sf WRFDA/var/obsproc/obs_gts_2008-02-05_12:00:00.3DVAR ./ob.ascii (l
ink OBSPROC processed observation file as ob.ascii)
> ln -sf $DAT_DIR/be/be.dat ./be.dat (link background error statistics as be.dat)
> ln -sf WRFDA/var/da/da_wrfvar.exe ./da_wrfvar.exe (link executable)
-We will begin by editing the file, namelist.input, which is a very basic namelist.input for running the tutorial test case is shown below. Only the time and domain settings need to be specified in this case, if we are using the default settings provided in WRFDA/Registry/Registry.wrfvar)
+We will begin by editing the file, namelist.input, which is a very basic namelist.input for running the tutorial test case is shown below and provided as WRFDA/var/test/tutorial/namelist.input. Only the time and domain settings need to be specified in this case, if we are using the default settings provided in WRFDA/Registry/Registry.wrfvar)
&wrfvar1
print_detail_grad=false, / &wrfvar2 /
&wrfvar3
@@ -305,7 +307,6 @@
&wrfvar8
/
&wrfvar9
-trace_use=false, (Note: if not specified, default trace_use=true is applied. A subdirectory trace has to be created in your working directory before running da_wrfvar.exe)
/
&wrfvar10
/
@@ -331,10 +332,10 @@
&wrfvar20
/
&wrfvar21
-time_window_min="2008-02-05_12:00:00.0000",
+time_window_min="2008-02-05_11:00:00.0000",
/
&wrfvar22
-time_window_max="2008-02-05_12:00:00.0000",
+time_window_max="2008-02-05_13:00:00.0000",
/
&wrfvar23
/
@@ -492,9 +493,9 @@
A file called namelist.output (which contains the complete namelist settings) will be generated after a successful da_wrfvar.exe run. Those settings that appear in namelist.output that are not specified in your namelist.input are the default values from WRFDA/Registry/Registry.wrfvar.
After successful completion of job, wrfvar_output (the WRF-Var analysis file, i.e. the new initial condition for WRF) should appear in the working directory along with a number of diagnostic files. Various text diagnostics output files will be explained in the next section (HYPERLINK \l "_WRF-Var_Diagnostics_1"WRF-Var Diagnostics).
-In order to understand the role of various important WRF-Var options, try re-running WRF-Var by changing different namelist options. Such as making WRF-Var convergence criteria more stringent. This is achieved by reducing the value of the convergence criteria EPS to e.g. 0.0001 by adding "EPS=0.0001" in the namelist.input record &w
rfvar6. Last section of this tutorial deals with many such WRF-Var additional exercises.
+In order to understand the role of various important WRF-Var options, try re-running WRF-Var by changing different namelist options. Such as making WRF-Var convergence criteria more stringent. This is achieved by reducing the value of the convergence criteria EPS to e.g. 0.0001 by adding "EPS=0.0001" in the namelist.input record &wrfvar6. See section ( HYPERLINK \l "_Additional_WRF-Var_Exercises:" WRF-Var additional exercises) for more namelist options
b. Run the Case4D-Var
-To run WRF-4DVar, first create a working directory, WRFDA/var/test/4dvar is a sample; next assuming that we are using the C-shell, set the working directories for the three WRF-4DVar components WRFDA, WRFNL and WRFPLUS thusly
+To run WRF-4DVar, first create and cd to a working directory, for example, WRFDA/var/test/4dvar; next assuming that we are using the C-shell, set the working
directories for the three WRF-4DVar components WRFDA, WRFNL !
and WRFP
LUS thusly
> setenv WRFDA_DIR /ptmp/$user/WRFDA
> setenv WRFNL_DIR /ptmp/$user/WRFNL
> setenv WRFPLUS_DIR /ptmp/$user/WRFPLUS
@@ -605,7 +606,7 @@
Edit $WORK_DIR/ad/namelist.input and $WORK_DIR/tl/namelist.input to match your experiment settings.
Currently, parallel WRF 4D-Var is a MPMD (Multiple Program Multiple Data) application. Because there are so many parallel configurations across the platforms, it is very difficult to define a generic way to run the WRF 4D-Var parallel. As an example, to launch the three WRF 4D-Var executables as a concurrent parallel job on a 16 processor cluster, use:
> mpirun np 4 da_wrfvar.exe: -np 8 ad/wrfplus.exe: -np 4 nl/wrf.exe
-There are 4 processors are assigned to run WRFDA, 4 processors are assigned to run WRFNL and 8 processors for WRFPLUS due to high computational cost in adjoint code.
+In the above example, 4 processors are assigned to run WRFDA, 4 processors are assigned to run WRFNL and 8 processors for WRFPLUS due to high computational cost in adjoint code.
The file wrfda.log (or rsl.out.0000 if running in parallel mode) contains important WRF-4DVar runtime log informa
tion. Always check the log after a WRF-4DVar run.
Radiance Data Assimilations in WRF-Var
@@ -682,7 +683,7 @@
To use VarBC, set namelist option USE_VARBC to TRUE and have a VARBC.in file in the working directory. VARBC.in is a VarBC setup file in ASCII format. A template is provided with the WRF-Var package (WRFDA/var/run/VARBC.in).
Input and Output files
-All VarBC input is passed through one single ASCII file called VARBC.in file. Once WRF-Var has run with the VarBC option switched on, it will produce a VARBC.out file file which looks very much like the VARBC.in file you provided. This output file will then be used as input file for the next assimilation cycle.
+All VarBC input is passed through one single ASCII file called VARBC.in file. Once WRF-Var has run with the VarBC option switched on, it will produce a VARBC.out file which looks very much like the VARBC.in file you provided. This output file will then be used as input file for the next assimilation cycle.
Coldstart
Coldstarting means starting the VarBC from scratch i.e. when you do not know the values of the bias p
arameters.
@@ -859,8 +860,9 @@
Note: Larger analysis increments indicate a larger data impact in the corresponding region of the domain.
Updating WRF boundary conditions
-Before running NWP forecast using WRF-model, you must modify the tendencies within the lateral boundary condition file to make them consistent with the new WRF-Var initial condition (analysis). It is essential to update the tendencies since the previously generated the tendencies for the lateral boundary condition (in wrfbdy_d01 file), are only consistent with the previous initial condition. The updated by WRF-Var has changed the initial value (at t=0), and the initial tendencies in the file (wrfbdy_d01) need to be adjusted to the new initial condition. Moreover, in the cycling run mode (warm-start), the low boundary in the WRF-Var anaylsis file also needs to be updated based on the information of the wrfinput file, which is generated by WPS/real.exe at the analysis time.
-There are three input files: WRF-Var analysis, wrfinput and w
rfbdy files from WPS/real.exe, and a namelist file: param.in for running update_bc.exe. This procedure is performed by the WRF-Var utility called da_updated_bc.exe.
+Before running NWP forecast using WRF-model with WRF-Var analysis, the values and tendencies for each of predicted variables for the first time period in the lateral boundary condition file for domain-1 (wrfbdy_d01) must be updated to be consistent with the new WRF-Var initial condition (analysis). This is absolutely essential. Moreover, in the cycling run mode (warm-start), the low boundary in the WRF-Var anaylsis file also need to be updated based on the information of the wrfinput file generated by WPS/real.exe at the analysis time. So there are three input files: WRF-Var analysis, wrfinput and wrfbdy files from WPS/real.exe, and a namelist file: param.in for running da_update_bc.exe for domain-1.
+For the nested domains, domain-2, domain-3, the lateral boundaries are provided by their parent domains, so no
lateral boundary update needed for these domains, But the l!
ow bound
aries in each of the nested domains WRF-Var analysis files are still need to be updated. In these cases, you must set the namelist variable, domain_id > 1 (default is 1 for domain-1), and no wrfbdy_d01file need to be provided to the namelist variable: wrf_bdy_file.
+This procedure is performed by the WRF-Var utility called da_updated_bc.exe.
Note: Make sure that you have da_update_bc.exe in WRFDA/var/build directory. This executable should be created when you compiled WRF-Var code,
To run da_update_bc.exe, follow the steps below:
> cd WRFDA/var/test/update_bc
@@ -881,7 +883,7 @@
At this stage, you should have the files wrfvar_output and wrfbdy_d01 in your WRF-Var working directory. They are the WRF-Var updated initial condition and boundary condition for any subsequent WRF model runs. To use, just link a copy of wrfvar_output and wrfbdy_d01 to wrfinput_d01 and wrfbdy_d01, respectively, in your WRF working directory.
Running gen_be
-Starting with WRFDA version 3.1, the users have two choices to define the background error covariance (BE). We call them CV3 and CV5 respectively. There is no clear cut indication which BE. The impact on analysis varies case by case.
+Starting with WRFDA version 3.1, the users have two choices to define the background error covariance (BE). We call them CV3 and CV5 respectively. Both are applied the same set of the control variables, stream function, unbalanced potential velocity, unbalanced temperature, unbalanced surface pressure, and pseudo relative humidity. With CV3, the control variables are in physical space whi
le with CV5 the control variables are in eigenvector space. So the major differences between these two kinds of BE are the vertical covariance. CV3 used the vertical recursive filter to model the vertical covariance but CV5 used the empirical orthogonal function (EOF) to represent the vertical covariance. The recursive filters to model the horizontal covariance are also different in these two BEs. We have not conducted the systematic comparison of the analyses based on these two BEs. However, CV3 (a BE file provided with our WRF-Var system) is a global BE and can be used for any regional domains while CV5 is a domain-dependent BE, which should be generated based in the forecasts data from the same domain. At this moment, it is hard to tell which BE is better; the impact on analysis may be varying case by case.
CV3 is the NCEP background error covariance, it is estimated in grid space by what has become known as the NMC method (Parrish and Derber 1992) . The statistics ar
e estimated with the differences of 24 and 48-hour GFS forec!
asts wit
h T170 resolution valid at the same time for 357 cases distributed over a period of one year. Both the amplitudes and the scales of the background error have to be tuned to represent the forecast error in the guess fields. The statistics that project multivariate relations among variables are also derived from the NMC method.
@@ -937,8 +939,8 @@
Additional WRF-Var Exercises:
(a) Single Observation response in WRF-Var:
-Single observation test is done in WRF-Var by setting num_pseudo=1 along with other pre-specified values in record &wrfvar15 and &wrfvar19 of namelist.input,
-With the settings shown below, WRF-Var generates a single observation with pre-specified innovation Observation First Guess) value at desired location e.g at (in terms of grid coordinate) 23x23, level 14 for U observation with error characteristics 1 m/s, innovation size = 1.0 m/s.
+With the single observation test, you may get the ideas how the background and observation error statistics working in the model variable space. Single observation test is done in WRF-Var by setting num_pseudo=1 along with other pre-specified values in record &wrfvar15 and &wrfvar19 of namelist.input,
+With the settings shown below, WRF-Var generates a single observation with pre-specified innovation (Observation First Guess) value at de
sired location e.g. at (in terms of grid coordinate) 23x23, level 14 for U observation with error characteristics 1 m/s, innovation size = 1.0 m/s.
&wrfvar15
num_pseudo = 1,
pseudo_x = 23.0
@@ -1088,10 +1090,10 @@
-WRF-ARW V3: Users Guide 6- PAGE 22
+WRF-ARW V3: Users Guide 6- PAGE 34
-WRF-ARW V3: Users Guide 6- PAGE 21
+WRF-ARW V3: Users Guide 6- PAGE 35
@@ -1112,11 +1114,11 @@
-
-
-&
+
+
+&
@@ -1126,1620 +1128,1595 @@
-h+'
+h~
-h+'
-h+'
+
+h~
+h~
-Px 4 #\'*.25@9
-h+'
-h+'
-h+'
-/
-h+'
-8
-& F
-&
-&
+Px 4 #\'*.25@9
+h~
+h~
+h~
++
+h~
+&
+&
&
+hhd
&
+
& F
-&
-
+hhd
&
+hhd
&
-& F
+
& F
h(
Hd
-`Hgd+'
-h+'
-L
-L
+`Hgd~
+& F
+h~
+h~
&
-
-h+'
-\
-5
-h+'
-i
-h+'
-h+'
+
+h~
xx
+h~
+h~
+h~
l
-l
+l
l
-l
+l
+h~
l
-l
+l
l
-l
-h+'
-h+'
-h+'
-h+'
-h+'
-h+'
-h+'
-
-&
-&
-&
-
+l
+h~
+h~
+h~
+
+h~
+h~
+&
+&
+&
+h~
+
t
-l
+l
+
t
-l
+l
t
l
+
+
t
-l
-t
l
+
t
+l
+t
l
+
t
-l
-
-
-
-h+'
+l
+
+
+h~
t
-l
+l
t
-l
+l
t
-l
+l
t
-l
+l
t
-l
+l
t
-l
+l
t
-l
+l
t
-l
+l
t
-l
-
+l
t
-l
+l
t
-l
+l
t
-l
-h+'
-h+'
-
-
-
-
-
-
-
-
-
-h+'
-
-
-
-h+'
-h+'
-.
-h+'
-&
-h+'
-h+'
+l
+h~
+h~
+
+
+
+
+h~
+h~
+
+h~
+h~
+h~
+h~
+h~
+h~
+&
+h~
+h~
l
-
+
,#
-l
+l
,#
-l
-h+'
-h+'
+l
+H
+h~
+h~
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
+H
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
l
+
,#
-l
+l
,#
l
-f
+
+f
,#
l
+
+h~
+h~
l
+
,#
-l
-h+'
-h+'
-f
-f
+l
+f
+f
,#
-l
+l
,#
l
-f
+
+f
,#
l
+
,#
l
+
l
-
+
,#
l
+
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
+Q
+T
+h~
,#
-l
-h+'
+l
,#
-l
+l
,#
-l
-G
+l
,#
-l
+l
,#
-l
+l
+Q
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
l
+
l
-
+
,#
l
+
+T
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
-h+'
-h+'
+l
+h~
+h~
,#
-l
+l
,#
-l
+l
l
+
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
l
+
,#
-l
-R
-h+'
+l
+h~
,#
l
+
,#
-l
+l
l
+
,#
-l
+l
,#
l
+
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
-h+'
-h+'
+l
+c
+h~
+h~
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
l
+
,#
-l
+l
,#
l
+
,#
-l
+l
,#
-l
-`
-h+'
+l
+h~
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
-`
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
l
+
,#
-l
+l
,#
l
+
l
-
+
,#
l
-h
-h+'
-h+'
+
+h~
+h~
,#
-l
-f
-f
+l
+f
+f
,#
-l
+l
l
+
,#
-l
+l
l
-
+
,#
l
+
,#
l
+
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
-h+'
-h+'
+l
+h~
+h~
,#
-l
+l
,#
-l
+l
l
+
,#
-l
+l
#
l
+
l
-
+
#
l
+
#
-l
+l
#
-l
+l
#
l
+
#
l
+
#
-l
+l
#
-l
-h+'
-h+'
+l
+h~
+h~
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
l
+
#
l
+
#
l
+
#
-l
+l
#
l
+
l
+
#
-l
+l
,#
l
-h+'
-h+'
+
+h~
+h~
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
l
+
l
+
,#
-l
+l
,#
l
+
,#
l
+
,#
-l
+l
l
+
,#
-l
+l
,#
l
+
l
+
l
+
,#
-l
-
-h+'
+l
+h~
,#
l
+
,#
l
+
l
-
-
-
+
l
+
l
+
,#
-l
+l
l
-
+
,#
l
+
,#
l
+
,#
-l
+l
,#
-l
+l
,#
-l
-h+'
-h+'
+l
+h~
+h~
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
l
+
#
-l
+l
#
l
+
#
-l
+l
+
#
l
+
l
+
#
-l
+l
#
l
+
#
-l
+l
l
-
+
#
l
+
#
l
+
#
-l
-h+'
-h+'
+l
+h~
+h~
#
-l
+l
l
+
#
l
+
#
-l
+l
#
-l
+l
#
l
+
#
l
+
#
l
+
#
-l
+l
#
-l
+l
l
+
#
l
+
#
-l
+l
#
-l
+l
#
l
+
#
l
+
#
l
+
#
-l
+l
#
-l
+l
#
l
+
l
-
+
#
l
-h+'
+
+h~
#
l
+
#
-l
+l
#
-l
+l
#
l
+
#
l
+
#
l
+
#
-l
+l
#
-l
+l
#
l
+
#
l
+
#
l
+
#
-l
+l
#
-l
+l
#
l
+
l
-
+
#
l
+
#
l
+
#
-l
+l
#
-l
+l
#
l
-
+
#
l
+
#
l
+
#
-l
+l
#
-l
+l
#
l
-
-
-h+'
+
+
+
+h~
#
l
-
+
#
l
+
#
-l
-
+l
#
-l
+l
#
l
+
#
l
+
+
#
l
+
#
-l
+l
#
-l
+l
+
#
l
+
+
#
l
+
#
l
+
#
-l
+l
#
-l
+l
#
l
+
#
l
+
#
l
+
#
-l
+l
#
-l
+l
#
l
+
#
l
-
-
-
-h+'
-h+'
+
+
+
+
+h~
+h~
#
l
+
#
-l
+l
#
-l
+l
#
l
+
#
l
+
#
l
+
#
-l
+l
#
-l
+l
#
l
+
#
l
+
#
l
+
#
-l
+l
#
-l
+l
#
l
+
#
l
-
+
+
-
-#
+
+#
Zcd
@@ -3234,9 +3211,10 @@
a oq[;kw}SO >ؖ*''f:S~0`]^yUZ73nEc~Wн>
'=)|L9/f}%io}]>h|O)~.K闯_>w~տ~:[w;yoH s|]H90;X'5/4H OvwH 2쬬D
-
-
+n/I
t
+
+
+
aߗ!,3@E
hA [^Ql^*Q,Z@*(KAKā0@ 3d 94ɽI$|2mړON}r\2bKթ+-b 8WZ,o˯[ZܮMGK8KX3X?秶,"c Ϛ>bv
UW]U|̇
@@ -3380,8 +3358,8 @@
^AݔV6#*
pg^%
31
-
-
+
+
bWV
g0a@ >Dž>gz_ V:\n~{Iu>f{a {y®k'\"ᠰ~hǵʰ. kk~c})l6#쨰^:n|6ʰ&8=, Wk1[aͣքa;;̵f2,õo? ,d-m؛5apͰz0 eް^kXcusV=VxG(߾{X ~a{a
;2l]ذ0o ~a&
@@ -3948,8 +3926,8 @@
%
%Ez @63r/
-
-
+
+
)wsCO>c8㚚j-ղQ9{>3f}
&lM
@@ -4164,7 +4142,7 @@
l
l
-
+
t
t
t
@@ -4196,9 +4174,9 @@
6`6
t
-
-
-{{
+
+
+{{
{{2?
c?7
gݾ(C+0sb!}Q1
E<f߿s <{B;wjhw9 ҥK 9hK/˗/GkQ|MKV㵠;Wx5|Chaq,1D /믑=v<)RP:tH`,1ܹ3]#iY0&ؘ _!1<mǥ>$B!B!B!$qpps?_R###C4O 320{ͺ8_>up8~|;/"|v:zOxx7 <<nAᥝG8Cq~z%qջ&ײU|);鴤XNh9G>ϥPWy%]GHIߙ;_onSs]2YZοw⳿8.ۧs>Gο+v 7չN/pݶw(ک_Ia[!\ pT ܿ? "W ,οE])ty1V#k dohp(p}HZ9}vA^!!?8 v@v]EYcG gi,sק+G οUw$yq"u}{wWv һ ɜ%MxMftz}nР߬#Q4} 8ȓQv Wѽkj8Tdʖ~Y7!
-
-
-
+
+
\)QTD"tOHG/ET^"T] WyO}f7l3g flyg9sεq"E%Y#vw6 ( ɰZF;۱3qE5߶Wi#E9UH """"""r^^}UiѢmVL".\s >|X (.]RȲe9}[2k,[7Ȅ \? 6LVZe> ?>S_۷-{zwd~_ʊDtϟ
HDD(QBy]KN
.,۷os^Z=S2eȀ,Aɮ]|L
@@ -4422,8 +4399,9 @@
c]onف84'"]j> *X :S!1/E!q#C5
)EE){0eRRSSRSJSSJ22
2KJRN20lRg ^
-
-
+
?uXMLLDFtO>EҥƘ?^oٳnkطoҏ# #Z-n߾m'OF``sPK} X`cbԨQ4+WD߾}z
@@ -4898,8 +4876,8 @@
Om=ttzfZFv=+ Mӝݺgieͷ,-(}-Ag +<ϙEd^Kd;}vV4Rn|>GLw-ޒlD&r;˱ =^܀d,`+tgY~/F >;rc Zoko,?bmW3hvU &j ~z-B嗷DJm_ R_DuDsay=kM|3J}D%-'vh&z8AT>gu-,)ҢJlÈuٲcٺqOkrΞΊVNv+y=+zW~PT2eLYdNu+7XSOtwOv88{k 5+[qr_)ЎroN8Ф jn>h )ښm+
y)
v2\ˠ[PZ\_r XF!(U!/55%5E$_85U$#X 3(U:DM
-
-
+
+
J&H(yA@(( >φ4@(zoRAJhUx"|o ܒ{M9Aٹ͙9sf !3'J̓
Jߙ7gdct#H6\FoY!1N)#*zUS
GN]fݝ1bdy7qڬU ԝR?u
y)
-1\ˠ[PZ\_r4XF!(U!/55%5E$_85U$#X 3(UlM
-
-
+1\ˠ[PZ\_r4XF!(U!/55%5E$_85U$#X 3(UlM
+
+
,(K,1(DDD9xL0Avk֬u+WdDDD9rX,={E!""2̬Ytz͚5 >|8KFDDDݻwɓٞ "u߾}%<<\bbbdDDDDDDD)5 |DEEɭ[dȐ!{|7ސ+W J:u$oC[jo^oߞ !N:%ӦM#F3QFɤIuqٳgܾ}EGG{v ڑ#GkDDDd,ժU5kBѢEH"Æ
sپ[nz}̙rRL *˖-slDD 4H2d *r _~l۶˶ҥ7 ~x
<^t~
@@ -7660,9 +7637,9 @@
-
+
& F
-l
Px 4 #\'*.25@9
-
+
+
+
+
+
+
+
+
+
+
-
-
+
+
@d
-@t
-2
-F
-c
-
-
-
-
-A
-Z
-
-
-
+
+%
+{
+
+
+
+
+
+B
+K
+N
<font color="red">
+
+
+
0
0
0
0
0
- 0
- 0
0
0
P
p
-2
-F
-c
-
-
-
-
-A
-Z
-
-
-
"
quot;
uot;
ot;
-
d
"
"
quot;
4d
`t0
+ 0
0
0
T
p
+
+%
+{
+
+
+
+
+
+B
+K
+N
<font color="gray">
+
+
+
uot;
/
+
d
"
"
quot;
4d
@
@@ -7825,119 +7789,96 @@
-
z
-
-
+
z
+
+
+
+
-
-
-
-
-
-
-
--
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+.
+M
+y
+
+
-
-
-
-
-
-
-
-
-0
j
--
-Q
-x
-y
-
-
-
-
-7
-<
-L
-Z
-g
-r
+
+
+
+
+
+K
+f
+
+
+
+
+
ot;
+y
+}
+
+
+
+
+
+
+
+
+B
+K
+L
+N
+k
<font color="gray">
+x
+z
^Zp;K`|$~
@@ -7947,34 +7888,37 @@
-^Z
+^Z
-`GT^5bBJ>*N
-c
-A
-Z
-
-
-
+
+B
+K
+N
<font color="red">
+
+
+
-
+
+
-
-
+
+
+
+
+
-
-
\ No newline at end of file
+
+
+
\ No newline at end of file
</font>
</pre>