<p><b>duda</b> 2008-07-01 13:00:46 -0600 (Tue, 01 Jul 2008)</p><p>More formatting changes.<br>
<br>
M users_guide_chap6.doc<br>
</p><hr noshade><pre><font color="gray">Modified: trunk/wrf/UsersGuide/users_guide_chap6.doc
===================================================================
--- trunk/wrf/UsersGuide/users_guide_chap6.doc 2008-07-01 18:27:54 UTC (rev 98)
+++ trunk/wrf/UsersGuide/users_guide_chap6.doc 2008-07-01 19:00:46 UTC (rev 99)
@@ -1,7 +1,6 @@
-ࡱ
xb: first guess either from previous WRF forecast or from WPS/real output.
yo: observations processed by OBSPROC.
PBf0: background error statistics from gen_be.
-In this chapter, you will learn how to run the various components of WRF-Var system. In the online tutorial, 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 (previous forecastWPS/real output used as a first guess of the analysis), and c) Background error statistics (climatological estimate of errors in the background file, generated with one-month 200-km resolution CONUS domain runs). In your own work, you will need tohave to create all these input files yourselves. See section Running Observation Preprocessor for creating your observation files. See section Running gen_be for generating your background error statistics file.
+In this chapter, you will learn how to run the various components of WRF-Var sy!
stem. In the online tutorial, you are supplied with a test case including the following input data: a) observation file (in the format prior to OBSPROC), b) WRF NetETCDF background file (previous forecastWPS/real output used as a first guess of the analysis), and c) Background error statistics (climatological estimate of errors in the background file, generated with one-month 200-km resolution CONUS domain runs). In your own work, you will need tohave 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.
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 secon!
d you ca
n test whether your computer is adequate to run the entire modeling system. After you have done the online tutorial, you can try
Running other, more computationally intensive, case studies.
@@ -39,7 +38,7 @@
Running WRF-Var requires a Fortran 90 compiler. We currently support the following platforms: IBM, DEC, SGI, PC/Linux (with Portland Group compiler), Cray-X1, and Apple G4/G5. Please let us know if this does not meet your requirements, and we will attempt to add other machines to our list of supported architectures as resources allow. Although we are interested to hear of your experiences on modifying compile options, we do not yet recommend making changes to the configure file used to compile WRF-Var.
Installing WRF-Var
-Before compiling WRF-Var code on a computer, in addition to netCDF library, check to see if the BLAS, LAPACK, and BUFR libraries are installed. If any of the BLAS, LAPACK and BUFR libraries is not available on the computer, it needs to be installed first. These softwares can be freely downloaded from HYPERLINK "http://netlib.org/blas/" http://netlib.org/blas/, HYPERLINK "http://netlib.org/lapack/" http://netlib.org/lapack/,!
and HYPERLINK "http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/" http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/. Assuming, for example, that these libraries have been installed in subdirectories of /usr/local, the necessary environment variables might be set with
+Before compiling the WRF-Var code, it is necessary to have installed the NetCDF, BLAS, LAPACK, and BUFR libraries. If any of the BLAS, LAPACK and BUFR libraries are not available on the computer, they needs to be installed first. The source code for these libraries can be freely downloaded from HYPERLINK "http://netlib.org/blas/" http://netlib.org/blas/, HYPERLINK "http://netlib.org/lapack/" http://netlib.org/lapack/, and HYPERLINK "http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/" http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/. Assuming, for example, that these libraries have been installed in subdirectories of /usr/local, the necessary envi!
ronment variables might be set withBefore compiling WRF-Var co!
de on a
computer, in addition to netCDF library, check to see if the BLAS, LAPACK, and BUFR libraries are installed. If any of the BLAS, LAPACK and BUFR libraries is not available on the computer, it needs to be installed first. These softwares can be freely downloaded from HYPERLINK "http://netlib.org/blas/" http://netlib.org/blas/, HYPERLINK "http://netlib.org/lapack/" http://netlib.org/lapack/, and HYPERLINK "http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/" http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/. Assuming, for example, that these libraries have been installed in subdirectories of /usr/local, the necessary environment variables might be set with
setenv BLAS /usr/local/blas
setenv LAPACK /usr/local/lapack
setenv BUFR /usr/local/bufr
@@ -99,11 +98,11 @@
If you have compiled WRF code, you may notice the build mechanism of WRF and WRFDA looks very similar. This is because WRF and WRFDA share the same build mechanism. But caution needs to be paid when compiling WRFDA.
Note: OpenMP, or shared memory, or sm options do not apply to WRF-Var compilecompilation.
Note: nesting does not apply to WRF-Var, please select 1=basicso please select the simplest option. If no-nesting is not available, select basic nesting option is OK.
-Note: WRF compiles with r4 option while WRFDA compiles with r8. That is why WRF and WRFDA can not reside and be compiled under the same directory.
+Note: WRF compiles with r4 option while WRFDA compiles with r8. That is whyFor this reason, WRF and WRFDA can not reside and be compiled under the same directory.
Hint: It is helpful to start with something simple, such as the serial build. If it is successful, move on to build dmpar code. Remember to type clean a between each build.
To compile th!
e code, type
> ./compile all_wrfvar
-Successful compilation of all_wrfvar will produce several executables in var/da directory including da_wrfvar.exe. You can list these executables by issuing the command (from WRFDA directory)
+Successful compilation of all_wrfvar will produce several executables in the var/da directory, including da_wrfvar.exe. You can list these executables by issuing the command (from WRFDA directory)
> ls -l var/da/*exe
-rwxr-xr-x 1 xinzhang users 2450389 Jun 16 11:45 var/da/da_advance_time.exe
@@ -137,16 +136,16 @@
lrwxrwxrwx 1 xinzhang users 27 Jun 16 11:46 var/da/gen_be_stage3.exe -> ../gen_be/gen_be_stage3.exe
lrwxrwxrwx 1 xinzhang users 34 Jun 16 11:46 var/da/gen_be_stage4_global.exe -> ../gen_be/gen_be_stage4_global.exe
lrwxrwxrwx 1 xinzhang users 36 Jun 16 11:46 var/da/gen_be_stage4_regional.exe -> ../gen_be/gen_be_stage4_regional.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.
+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.
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_advance_time.exe is a very handy and useful tool for date manipulation. Type da_advance_time to see its usage instruction.
+da_advance_time.exe is a very handy and useful tool for date manipulation. Type da_advance_time to see its usage instruction.
Executables for running WRF-Var and gen_be are created at this step. Proceed to the next section to learn how to build OBSPROC. After successful compilation of WRF-Var you are ready to run WRF-Var for the test case.
Running Observation Preprocessor (OBSPROC)
-OBSPROC program reads in process decoded observations in LITTLE_R format (a legendary ASCII format since MM5 era)., Please refer to 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 this tutorial, an observation file in LITTLE_R format is !
provided
. 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. such as the ouput of the MM5 "gts_decoder" or the "fetch.csh" utilities for inputing into the WRF-Var system. If you have no idea about the LITTLE_R format, please refer to 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. If you have observations in other various format, 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 !
OBSPROC program reads in process decoded observations in LITTLE_R format (a legendary ASCII format, in use since MM5 era)., Please refer toto 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 this tutorial, an observation file in LITTLE_R format is provided. 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. such as the ouput of the MM5 "gts_decoder" or the "fetch.csh" utilities for inputing into the WRF-Var system. If you have no idea about the LITTLE_R format, please refer to HYPERLINK "http://www!
.mmm.ucar.edu/mm5/mm5v3/data/how_to_get_rawdata.html" h!
ttp://ww
w.mmm.ucar.edu/mm5/mm5v3/data/how_to_get_rawdata.html. If you have observations in other various format, a sample program (LITTLE_R/util/upa.f) for writing out data in little_rLITTLE_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
-BThe basic operations performed by 3dvar_obsOBSPROC are:
+BThe bThe basic operations performed by 3dvar_obsOBSPROC 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.
@@ -154,7 +153,7 @@
Assign 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.
-1) Remove the observations outside the time range and domain (horizontal and top).
+The 1) Remove the observations outside the time range and domain (horizontal and top).
2) Re-order and merge the duplicate (in time and location) data reports.
3) Retrieve the pressure or height based on the observed information using the with the hydrostatic assumption.
4) Check the vertical consistency and super adiabatic for multi-level observations.
@@ -162,19 +161,19 @@
6) Write out the observation file to be usedat the by WRF-Var in ASCII or BUFRinput format.
7) Plot the distribution of for each type of observation types.
-WRF-Var observation preprocessor is residing under WRFDA/var/obsproc directory
+WRF-Var observation preprocessor is residingOBSPROC program is found under the directory WRFDA/var/obsproc directory. To compile the program, issue the following commands.
> cd WRFDA/var/obsproc
> make
-Once this is completed (a minute or less on most machines), you can check for the presence of the OBSPROC executable src/3dvar_obs.exe
-Before running 3dvar_obs.exe, create the desired namelist file namelist.3dvar_obs (see WRFDA/var/obsproc/README.namelist, or section Description of Namelist Variables for details);
-For your reference in var/obsproc directory a file named namelist_3dvar_obs.wrfvar-tut have has already been created. Thus, proceed as follows.
+Once this is completed (a minute or less on most machin!
es), you can check for the presence of the OBSPROC executable, src/3dvar_obs.exe
+Before running 3dvar_obs.exe, create the desired required namelist file namelist.3dvar_obs (see WRFDA/var/obsproc/README.namelist, or the section HYPERLINK \l "_Description_of_Namelist_1" Description of Namelist Variables for details).;
+For your reference, in var/obsproc directory an example file named namelist_3dvar_obs.wrfvar-tut have has already been created in the var/obsproc directory. Thus, proceed as follows.
> cp namelist.3dvar_obs.wrfvar-tut namelist.3dvar_obs
-edit namelist.3dvar_obs
+edit Next, edit namelist.3dvar_obs.
In this namelist file, all you need is to change the full path and name of the observation file (ob.little_r) depending upon where this file is downloaded and where it finally resides.
To run OBSPROC, type
> 3dvar_obs.exe >&! 3dvar_obs.out
-Once 3dvar_obs.exe has completed successfully, you will see an observation data fil!
e: obs_gts_2007-01-02_00:00:00.3DVAR, in obsproc directory. !
This is
the input observation file to WRF-Var.
-obs_gts_2007-01-02_00:00:00.3DVAR is an ASCII file that contains a header section (listed below) followed by observations. The meanings and format of observations in the file are described in the last 6 lines of the header section.
+Once 3dvar_obs.exe has completed successfully, you will see an observation data file,: obs_gts_2007-01-02_00:00:00.3DVAR, in the obsproc directory. This is the input observation file to WRF-Var.
+obs_gts_2007-01-02_00:00:00.3DVAR is an ASCII file that contains a header section (listed below) followed by observations. The meanings and format of observations in the file are described in the last 6six lines of the header section.
TOTAL = 24424, MISS. =-888888.,
SYNOP = 1014, METAR = 2551, SHIP = 270, BUOY = 295, BOGUS = 0, TEMP = 122,
AMDAR = 224, AIREP = 1303, PILOT = 112, SATEM = 204, SATOB = 18216, GPSPW = 113,
@@ -198,14 +197,14 @@
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 you are aiming to assimilate for this case, its 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 exercise this, proceed as follows.
+ Before running WRF-Var, you may like to learn more about various types of data you are aimingthat will be to assimilated for this case, for example, theirits 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 exercise use this utilitythis, proceed as follows.
> cd MAP_plot
-Modify the script Map.csh to set the time window and full path of input observation file (obs_gts_2007-01-02_00:00:00.3DVARobs_gts.3dvar). Precisely, the following string in this script as follows.
+Modify the script Map.csh to set the time window and full path of input observation file (obs_gts_2007-01-02_00:00:00.3DVARobs_gts.3dvar). Precisely,You will need to set the following strings in this script as follows.:
TIME_WINDOW_MIN = 2007010121
TIME_ANALYSIS = 2007010200
TIME_WINDOW_MAX = 2007010203
OBSDATA = ../obs_gts_2007-01-02_00:00:00.3DVARobs_gts.3dvar
-Type
+TNext, type
> Map.csh
When the job has completed, you will have a gmeta file gmeta.{analysis_time} corresponding to analysis_time=2007010200. This contains plots of data distribution for each type of observations contained in the OBS data file: obs_gts_2007-01-02_00:00:00.3DVA!
Robs_gts.3dvar. To view this, type
@@ -214,6 +213,8 @@
It will display (panel by panel) geographical distribution of various types of data which are listed in the header of obs_gts.3dvar. Following is the geographic distribution of sonde observations for this case.
+
+
After creating successfully your own observation file (obs_gts.3dvar), copy it to $DAT_DIR using the command (from obsproc directory)
> mv obs_gts_2007-01-02_00:00:00.3DVAR & $DAT_DIR/ob/2007010200/ob.ascii
@@ -337,7 +338,7 @@
&namelist_quilt
/
da_wrfvar.exe >&! wrfda.log
-wrfda.log (or rsl.out.0000 if running in MPP mode) contains important WRF-Var runtime log. Always check the log after a WRF-Var run:
+wrfda.log (or rsl.out.0000 if running in distributed-memoryMPP mode) contains important WRF-Var runtime log. Always check the log after a WRF-Var run:
*** VARIATIONAL ANALYSIS ***
DYNAMICS OPTION: Eulerian Mass Coordinate
WRF NUMBER OF TILES = 1
@@ -524,15 +525,15 @@
-rw-r--r-- 1 xinzhang 4393186 Jun 18 13:17 unpert_obs
drwxr-xr-x 3 xinzhang 4096 Jun 18 13:17 working-rw-r--r-- 1 xinzhang 3651560 Jun 18 13:17 wrfvar_output
Content of some useful diagnostic files are as follows:
-cost_fn & grad_fn: The twoese files hold (in ASCII format) WRF-Var cost & gradient function values respectively for only the first and last iterations. However, iIf you setrun with NL_CALCULATE_CG_COST_FN=true (in record &WRFVAR11 in namelist.input), it lists thesethe cost function values forof each iteration will be calculateds,. For visualization purpose, sometimes it is good to run WRF-Var with this option, as it will list the cost and gradient function for each iteratihowever, the run time will be significantly increasedon. FollowingA NCL script (WRFDA/var/graphcs/ncl/plot_cost_grad_fn.ncl) may be used tois provided for plotting the content of cont_fn & grad_fn , if these files are generated with NL_CALCULATE_CG_COST_FN=true. I!
t may be visualized using following NCL script: WRFDA/var/graphcs/ncl/plot_cost_grad_fn.ncl as:
+cost_fn & and grad_fn: The twoese files hold (in ASCII format) WRF-Var cost & and gradient function values respectively for only the first and last iterations. However, iIf you setrun with NL_CALCULATE_CG_COST_FN=true (in record &WRFVAR11 in namelist.input), it lists thesethe cost function values forof each iteration will be calculateds,. For visualization purpose, sometimes it is good to run WRF-Var with this option, as it will list the cost and gradient function for each iteratihowever, the run time will be significantly increasedon. FollowingAn NCL script (WRFDA/var/graphcs/ncl/plot_cost_grad_fn.ncl) may be used tois provided for plotting the content of cont_fn & and grad_fn , if these files are generated with NL_CALCULATE_CG_COST_FN=true. It may be visualized using following NCL script: WRFDA/var/graphcs/ncl/plot_cost_grad_fn.ncl as:
- Not!
e: Make sure that you removed first two records lines (header)!
in cos
t_fn & grad_fn before you plot. Also you need to specify the directory name for these two files.
+ Note: Make sure that you removed first two records lines (header) in cost_fn & and grad_fn before you plot. Also you need to specify the directory name for these two files.
gts_omb_oma: It holds (in ASCII format) information of each type ofall observations, that got passed in WRF-Var. like its Each observation has its observed valuevalue, quality flag, observation error, observation minus background (OMB), and & observation minus analysis (OMA). This information is very useful for (both analysis or forecasts) verification purposes.
namelist.input: WRF-Var input namelist file. It displays all the non-default options which user defined. If any of your namelist defined options did not appear in this file, you may like to check its name and match it with the WRFDA/Registry/Registry.wrfvar.
namelist.output: Consolidated list of all the namelist!
options used.
Rslrsl*: Directory Files containing information of standard WRF-Var output from individual processors when multiple processors are used. It contains host of information on number of observations, minimization, timings etc. Additional diagnostics may be printed in these files by including various print WRF-Var namelist options. TO To learn more about these additional print options, search print_ string in WRFDA/Registry/Registry.wrfvar.
statistics: Text file containing OMB (OI), OMA (OA) statistics (minimum, maximum, mean and standard deviation) for each observation type and variable. This information is very useful in diagnosing how WRF-Var has used different components of the observing system. Also contained are the analysis minus background (A-B) statistics i.e. statistics of the analysis increments for each model variable at each model level. This information is very useful in checking the range of analysis increment values found in the an!
alysis, and where they are in the WRF-model grid space.
-The f!
inal WRF
-Var analysis file resides asis ${RUN_DIR}/2007010200/wrfvar /working/wrfvar_output,. also has a copy as $FC_DIR/2007010200/wrfinput_d01. It is in WRF (NETCDF) format. It will be the wrfinput_d01 of your following WRF run after lateral boundary and/or low boundary conditions are updated by another WRF-Var utility (See section Updating WRF lateral boundary conditions).
+The final WRF-Var analysis file resides asis ${RUN_DIR}/2007010200/wrfvar /working/wrfvar_output,. also has a copy as $FC_DIR/2007010200/wrfinput_d01. It is in WRF (NETCDFNetCDF) format. It will be the wrfinput_d01 of your following WRF run after lateral boundary and/or low boundary conditions are updated by another WRF-Var utility (See section Updating WRF lateral boundary conditions).
It may be visualized using followingA NCL script: WRFDA/var/graphcs/ncl/WRF-Var_plot.ncl, is provided for plotting.
You need to specify the analsyis_file name, its full path etc. Please see the in-line!
comments in the script for The details are listed in this script as comments..
As an example, if you are aiming to display U-component of the analysis at level 18, execute following command after modifying the script WRFDA/var/graphcs/ncl/WRF-Var_plot.ncl, make sure following piece of codes are uncommented:
@@ -566,7 +567,7 @@
Updating WRF lateral boundary conditions
Before running NWP forecast using WRF-model, you must modify the tendencies within the lateral boundary condition files to make it consistent with the new WRF-Var initial conditions (analysis). This is absolutely essential because when you initially generated the tendencies for the lateral boundary condition (in wrfbdy_d01 file), it was consistent but subsequently by doing WRF-Var you changed the initial value (at t=0) and so accordingly the initial tendencies needs to be updated in this file (wrfbdy_d01) to adjust the change at the initial time. 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 update_bc.exe.
-This is a simple procedure!
performed by the WRF-Var utility called da_updated_bc.exe.
+This is a simple procedure performed by the WRF-Var utility called da_updated_bc.exe.
Note: Make sure that you have da_update_bc.exe in WRFDA/var/da directory. This executable automatically getsshould be created when you compiled WRF-Var systemcode,
To run da_update_bc.exe, follow the steps below:
cd WRFDA/var/test (the directory where you ran WRF-Var)
@@ -584,7 +585,7 @@
/
ln sf WRFDA/var/da/da_update_bc.exe ./da_update_bc.exe
./da_updatebc.exe
-At this stage, you should have wrfvar_output and wrfbdy_d01 in your WRF-Var working. They are the WRF-Var updated initial condition and boundary condition for your following WRF model run. Link of copy wrfvar_output and wrfbdy_d01 to be wrfinput_d01 and wrfbdy_d01 respectively in your WRF working directory.
+At this stage, you should have wrfvar_output and wrfbdy_d01 in your WRF-Var working. They are the WRF-Var updated initial condition and boundary condition for your following WRF model run. Link a of copy of wrfvar_output and wrfbdy_d01 to be wrfinput_d01 and wrfbdy_d01 , respectively, in your WRF working directory.
The update_bc.exe is run via the same wrapper script, you ran con200 by adding following line in your wrapper script.
export RUN_UPDATE_BC=true
With this option standard script located at WRFDA/var/scripts/da_run_update_bc.ksh will be activated to update the content of !
wrfbdy_d01. The new lateral boundary input file will be located at the $FC_DIR and with the same name. You may like to check its date of creation by issuing the following command
@@ -599,7 +600,7 @@
It is important to include forecast differences from at least 00Z and 12Z through the period, to remove the diurnal cycle (i.e. do not run gen_be using just 00Z or 12Z model perturbations alone).
-The inputs to gen_be are NETCDF WRF forecast output ("wrfout") files at specified forecast ranges. To avoid unnecessary large single data files, it is assumed that all forecast ranges are output to separate files. For example, if we wish to calculate BE statistics using the NMC-method with (T+24)-(T+12) forecast differences (default for regional) then by setting the WRF namelist.input options history_interval=12, and frames_per_outfile=1 we get the necessary output datasets. If Then the forecast output files are thenshould be arranged as follows: directory name is the forecast initial time, time info in the file name is the forecast valid time. 2007010100/wrfout_d01_2007-01-01_12:00:00 mean a 12-hour forecast valid at 2007010112 initialized at 2007010100., the gen_!
be_wrapper.ksh script can be used without significant modification to calculate the necessary "perturbations".
+The inputs to gen_be are NETCDF NetCDF WRF forecast output ("wrfout") files at specified forecast ranges. To avoid unnecessary large single data files, it is assumed that all forecast ranges are output to separate files. For example, if we wish to calculate BE statistics using the NMC-method with (T+24)-(T+12) forecast differences (default for regional) then by setting the WRF namelist.input options history_interval=12, and frames_per_outfile=1 we get the necessary output datasets. If Then the forecast output files are thenshould be arranged as follows: directory name is the forecast initial time, time info in the file name is the forecast valid time. 2007010100/wrfout_d01_2007-01-01_12:00:00 mean a 12-hour forecast valid at 2007010112 initialized at 2007010100., the gen_be_wrapper.ksh script can be used without significant modification to ca!
lculate the necessary "perturbations".
Example !
director
y/files structure for a CON200 domain (45 x 45 x 28 gridpoints):
@@ -850,10 +851,10 @@
-WRF-ARW V3: Users Guide 6- PAGE 6
+WRF-ARW V3: Users Guide 6- PAGE 38
-WRF-ARW V3: Users Guide 6- PAGE 1
+WRF-ARW V3: Users Guide 6- PAGE 37
@@ -874,1846 +875,1825 @@
-
-h@
-
+
+h@}
+
&
-&
+&
&
&
&
-&
+&
&
&
+
&
-Fh@
-F
-Fhsg
+
+Fh@}
+F
+Fhsg
F
-Fhsg
-Fv
+Fhsg
+Fv
Fd&
&
-&
-FH
-&
-&
-F
+&
+Fh@}
+&
+&
F
-F*5
-F* hL
-F*5
-Fh@
-F
-Fd&
-Fh@
-F@
+F*5
+F* hL
+F*5
+Fh@}
+F
+Fd&
+Fh@}
F
F*0J
-
-F%
-F.
-F
+
+F(
+F
+F%
+F.
+F
F
-Fh@
-Fh\
-Fh"6
+Fh@}
+Fh\
+Fh"6
F!H
-Fhk
+Fhk
+F
+#
F%H
-Fh"6
-FhWL
-Fh+o
-Fh@
-Fh+o
-Fh+o
-Fh@
-F2
-F
-F
-Fh"6
-Fh@
-F%
-F/
-F4
-F
-F4
-F/
+FhWL
+Fh+o
+Fh@}
+Fh+o
+Fh+o
+Fh@}
+F2
+F
+F
+Fh"6
+Fh@}
+F%
+F/
+F4
+F
+F4
+Fn%
+F*5
+F
+FH
+Fh@}
+Fh@}
+F
-Px 4 #\'*.25@9
-F
-F*5
-F
-FH
-Fh@
-Fh@
-F
-F
-F
-F%
+Px 4 #\'*.25@9
+F
+F
+F
+F%
F!H
Fh
->
-Fh@
-F(hL
+>
+Fh@}
+F(hL
F*5
-FhL
+FhL
F*5%H
-Fhk
-Fh\{
-FhL
-F
+Fh\{
+FhL
+F
-Px 4 #\'*.25@9
-F
-Fd&
-Fph
-F2
-F
-F
-F3
-F;
-F;
-F2
-F
-F5
-Fhk
-Fhk
-FH
-&
-&
-F)
-F2
-F)
-F%
-Q
-v
-v
-v
-v
-v
-v
-v
-h@
+Px 4 #\'*.25@9
+F
+Fd&
+Fph
+F2
+F
+F
+Fr7
+F;
+F;
+F2
+F
+F 8
+Fhk
+Fhk
J
+O
cH
+O
+O
+&
+FH
+&
+F%
+F2
+F%
+T
+F%
+v
+v
+v
+v
+v
+v
+v
+_
^
+h@}
l
-l
-c
-
+l
+
l
-l
+l
l
-l
-
-
+l
+
+
l
-l
- Fhk
- Fh@
- FH
- F!H
+l
+ Fh@}
+ FH
F
- Fhk
- F
- F%
+ Fhk
+ FH
+ Fhk
+ F
FH
- Fh@
-m
-m
-n
-
-
-fh@
-
-h@
OJ
fYOOE9
-
+ F
+ F
+q
gd@}
+w
}
+
+
+fh@}
+h@}
OJ
+
+
h@}
+
p;
OJ
H
-
-
-
-&
-&
-h@
-h@
+`t
+
}
h F
+i
+
+
+
+
+
+h@}
+h@}
+&
+&
#
-l
+
+h@}
l
-
+
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
-
+l
#
-l
+l
#
-l
+l
#
-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
+
+h@}
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
l
-
+
#
-l
-h@
+l
#
-l
+l
#
-l
l
-
+
#
-l
+l
#
-l
+l
#
-l
+l
+
#
-l
+l
#
-l
+l
#
-l
+l
+
+
+
+
+
+
+
+
+
+h@}
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
+
#
-l
-h@
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
+
+
#
-l
+l
+
+
+
+
+
+
+
#
-l
+l
+
+
+
+
+
#
-l
+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
-
-
-
-
-
-
-
-
-
-
-
-
-h@
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
-
l
-
+
#
-l
+l
#
-l
-
+l
+h@}
#
-l
-
-
-
-
-
+l
#
-l
-
-
-
-
-
-
-
+l
+Y
#
-l
-
-
-
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-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
+l
#
-l
+l
#
-l
+l
+h@}
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
l
-
+
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
-h@
+l
#
-l
<font color="gray">
+l
#
-l
+l
#
-l
l
-
+
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
+h@}
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
l
-
+
#
-l
+l
#
-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
+l
#
-l
+l
+h@}
#
-l
+l
#
-l
+l
#
-l
l
-
+
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
l
-
-h@
+
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
l
-
+
#
-l
l
-
+
+&
+h@}
+&
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
-&
-h@
+l
#
-l
+l
#
-l
-&
l
-
-&
+
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
+h@}
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
-h@
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
+h@}
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
+
d#
-l
--
-h@
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
+l
d#
-l
l
-
+
#
-l
+l
#
-l
+l
#
-l
+l
+h@}
#
-l
+l
#
-l
+l
#
-l
l
-
+
#
-l
+l
#
-l
+l
#
-l
--
+l
#
-l
+l
#
-l
+l
#
-l
-h@
l
-
+
#
-l
l
-
+
#
-l
l
-
+
#
-l
l
-
+
#
-l
-
l
-
+
+h@}
+h@}
#
-l
l
-
+
#
-l
l
-
+
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
-2
-h@
-h@
+l
#
-l
+l
#
-l
+l
#
-l
-&
+l
+&
#
-l
+l
#
-l
-2
+l
#
-l
l
-
+
#
-l
+l
#
-l
l
-
+
#
-l
+l
+=
+h@}
#
-l
+l
#
-l
l
-
+
#
-l
+l
#
-l
l
-
+
#
-l
+l
#
-l
+l
#
-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
+h@}
#
-l
+l
#
-l
l
-
+
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-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
+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
-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
+h@}
+h@}
#
-l
+l
#
-l
+l
#
-l
+l
+
#
-l
+l
+
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
-l
-h@
-
-
-
-
+l
D
+
+
@@ -2815,8 +2795,8 @@
s#
V靗bKbl{3ȇ`B7S L & .vz鏟 n &aFUǀ 'zA+gv3O2 Y}5,< đ\ڑ/_>]&5ꘫq ǣrYX>:fdLYU#bn7/r ݪՄ"M\I0*Vkw֞@YtI&WcY l.{ DV4:R۩c
-
-
+
+
)].w
)].wPNG
@@ -3025,9 +3005,9 @@
eԳw@3]#;b69ώ
=Lw(
-cl t0*V*z2 uq*L2U垧JL
-
-
+cl t0*V*z2 uq*L2U垧JL
+
+
@@ -3419,9 +3399,9 @@
l
l
-
-
-
+
+
+
y**++eUHàl-~:w>~-:W[o%L?PuJJJl6:Hrwf1Xbe?swa_ץ\Ə /SL0a;4={LX{Yw}Okٸq"z|'yY}VȞ|IkC{
u(lH<CX.Ip=#H@6YYY999- _Q*<yIiRHuea{233]+5y;wѣGK"ʦV6_|^xA
t;%ÒȀaIDDd$""2`X0, DDD K"""%ÒȀaIDDd$""2`X0, ?>a
-
-
+Ts+--moo}3gvVuرCwU+WJ0 <x+jy hMt|dOYfu(1&܅eee/Ic|fJJJ筍?AJ:3f#+_[uջwﮩ"EIG싋WU=4
+
+
**g;nU]Fw}欹V[ ? Oa ]Â^~9tG 㿬"
-!Ho dVdE9Ȧ0{,$̓84Em*i2"(=ft}>=1Ҷ2J 3dMNU)O1 K]S[}sdɉt⎔ʊ ~ԫ<Z6/ޑA ~8y@+oL|XD#!HH:`tD0 WLc5?ʫ 8꿴i/f1zDv;!
-
-
+'ys; } <oL8v/S.g5-A<\t0?0t>$sᥦqu A.KR{V0]~>A.X=_'IqHC>;\CgPqga~IK3<a833"ʼnKK`_
+
+
aA@rF$9HI@T% ((~9uzj
$oQ>Ob?5bÂew*QFW+x
p= ~F}3
-
-
-
+Ft#}qnn@O
+
+
+
hmCњi,e
P@W
]^
@@ -5619,10 +5599,10 @@
!"`ؗt_7}V9(@şef
-"'p~ e<|J٣
-
-
+
+
eY8u1̥:+9?8VlwEj6RH˃3 C\KUΡ]A:eanMGݺޝ=(ntxs'a{jB0Nq{=JXFJ %C<}Vߚ2fd9/%t`,
@@ -6708,9 +6688,9 @@
@8W` @1x_
-'蔪
-
-
+'蔪
+
+
L {9_2{{ mU-/W*ϱ3POw2qWͲ p\-gK~GMev.j E_p8rkIScHP a. Ru Mn]/{xF)?~;cpwQM _~}i({fgwtp` % jQ4%$ɐX݊uc 7h6waQ|Գ#+G үx0EC^r
@@ -9601,7 +9581,7 @@
-
+
& F^
l
@@ -9641,7 +9621,7 @@
YU
+
+
-g
+
+
ư
-
-g
-y
-
-
-
-
+
+I
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
-
-
-'
-,
0
0
40
ʀ
(0
0
0
0
lH
-g
-y
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+7
j
f0t
0t
0
x
0t
x
0t
t
+I
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
-
-
-'
-,
О
0
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
-&
+
+
+7
0
0
0
+
+
+O
+
+
+
+
+
+
+
+
-
+
-
-
-&
-K
-
-
-'
-+
-,
-t
3
-
+
+
+
+m
+r
+|
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+7
+B
+)
+s
+u
+w
+
+
+
+
+
+
+
+
-
-
-
-
-
-
-'
-,
-=
Hu
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+(
+6
+7
+>
+J
F
l,6
-
+
+
^Z
-^Z
+^Z
@@ -10370,62 +10480,101 @@
-
-
-
-
-
+
+ 9e
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
-
-
-'
-,
+
+
+
+
+
+
+
+
+
+
+
+
+
+7
-
+
+
-
+
+
wwo~wo~o~ww
ZkZVZkZ^ZcF1^ZcZZg9kZZkZZ^VNsg9kZRVc^ZVco{o{kZRkZJRc^ZR^g9VZ^Vg9R^VkZNsR
swo{wo{o{ww
wwwww
-
-
+
+
r
+
+
+
@@ -10698,5 +10847,5 @@
-
\ No newline at end of file
+
+
\ No newline at end of file
</font>
</pre>