<p><b>xinzhang</b> 2009-04-03 17:09:34 -0600 (Fri, 03 Apr 2009)</p><p>Save with Don Stark's proof reading.<br>
</p><hr noshade><pre><font color="gray">Modified: trunk/wrf/UsersGuide/users_guide_chap2.doc
===================================================================
(Binary files differ)
Modified: trunk/wrf/UsersGuide/users_guide_chap6.doc
===================================================================
--- trunk/wrf/UsersGuide/users_guide_chap6.doc 2009-04-03 20:58:03 UTC (rev 173)
+++ trunk/wrf/UsersGuide/users_guide_chap6.doc 2009-04-03 23:09:34 UTC (rev 174)
@@ -1,5 +1,5 @@
-ࡱ
-
+
Barker, D.M., W. Huang, Y. R. Guo, and Q. N. Xiao., 2004: A Three-Dimensional (3DVAR) Data Assimilation System For Use With MM5: Implementation and Initial Results. Mon. Wea. Rev., 132, 897-914.
Huang, X.Y., Q. Xiao, D.M. Barker, X. Zhang, J. Michalakes, W. Huang, T. Henderson, J. Bray, Y. Chen, Z. Ma, J. Dudhia, Y. Guo, X. Zhang, D.J. Won, H.C. Lin, and Y.H. Kuo, 2009: Four-Dimensional Variational Data Assimilation for WRF: Formulation and Preliminary Results. Mon. Wea. Rev., 137, 299314.
-Running WRF-Var requires a Fortran 90 compiler. We currently had tested the WRF-Var on the following platforms: IBM (XLF), SGI Altix (INTEL), PC/Linux (PGI, INTEL, GFORTRAN), and Apple (G95/PGI). 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 c
onfigure file used to compile WRF-Var.
+Running WRF-Var requires a Fortran 90 compiler. We currently have currently tested the WRF-Var on the following platforms: IBM (XLF), SGI Altix (INTEL), PC/Linux (PGI, INTEL, GFORTRAN), and Apple (G95/PGI). 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 the WRF-Var code, it is necessary to have at least installed the NetCDF, BLAS and LAPACK libraries. If any of the BLAS and LAPACK libraries are not available on the computer, they need to be installed first. The source code for these libraries can be freely downloaded from HYPERLINK "http://netlib.org/blas/" http://netlib.org/blas/ and HYPERLINK "
;http://netlib.org/lapack/" http://netlib.org/lapack/!
. Assum
ing, 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 at least installed the NetCDF, BLAS and LAPACK libraries. If any of the BLAS and LAPACK libraries are not available on the computer, they need to be installed first. The source code for these libraries can be freely downloaded from HYPERLINK "http://netlib.org/blas/" http://netlib.org/blas/ and HYPERLINK "http://netlib.org/lapack/" http://netlib.org/lapack/. Assuming, for example, that these libraries have been installed in subdirectories of /usr/local, the necessary environment variables in C-shell would be set by the commands looking something like
> setenv BLAS /usr/local/blas > setenv LAPACK /usr/local/lapack
-If only conventional observational data from LITTLE_R format file was used, then the NETCDF, BLAS and LAPACK libraries are
mandatory. If you intend to use observational data with PREPBUFR format, the BUFR library has to be installed too and can be downloaded from HYPERLINK "http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/" http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/. If you intend to assimilate satellite radiance data, in addition to BUFR library, either CRTM (V1.2) or RTTOV (8.7) have to be installed and they can be downloaded from HYPERLINK "ftp://ftp.emc.ncep.noaa.gov/jcsda/CRTM/"ftp://ftp.emc.ncep.noaa.gov/jcsda/CRTM/ and HYPERLINK "http://www.metoffice.gov.uk/science/creating/working_together/nwpsaf_public.html" http://www.metoffice.gov.uk/science/creating/working_together/nwpsaf_public.html, the additional necessary environment variables might be set with
+If only conventional observational data from LITTLE_R format file is to be used, then only the NETCDF, BLAS and LAPACK libraries are mandatory. If you intend to use observational data
with PREPBUFR format, the BUFR library has to be installed t!
oo and c
an be downloaded from HYPERLINK "http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/" http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/. If you intend to assimilate satellite radiance data, in addition to BUFR library, either CRTM (V1.2) or RTTOV (8.7) have to be installed and they can be downloaded from HYPERLINK "ftp://ftp.emc.ncep.noaa.gov/jcsda/CRTM/"ftp://ftp.emc.ncep.noaa.gov/jcsda/CRTM/ and HYPERLINK "http://www.metoffice.gov.uk/science/creating/working_together/nwpsaf_public.html" http://www.metoffice.gov.uk/science/creating/working_together/nwpsaf_public.html. The additional necessary environment variables needed are set (again using the C-shell), by commands looking something like
> setenv BUFR /usr/local/bufr
> setenv RTTOV /usr/local/rttov87 > setenv CRTM /usr/local/crtm
Note: Make sure the required libraries were all compiled using the same compiler that will be used to build WRF-Var, since the libraries p
roduced by one compiler may not be compatible with code compiled with another. For BLAS, LAPACK and BUFR libraries compilation, they have to be compiled with the size of real variable = 8, which required by WRF-Var.
@@ -120,11 +120,11 @@
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.
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 WRF V3.1 and can only be used for 4D-Var purposes. WRFPLUS is the adjoint and tangent linear model based on a simplified WRF model, which only include some simple physical processes such as vertical diffusion and large-scale condensation.
+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 , rename the directory name to WRFNL
+Unzip and untar the file , name the directory WRFNL
> gzip -cd WRFV3.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
@@ -134,15 +134,15 @@
serial means single processor
dmpar means Distributed Memory Parallel (MPI)
smpar is not supported for 4D-Var
-please select 0 for the second option for no nesting
+Please select 0 for the second option for no nesting
Compile the WRFNL
> ./compile em_real
> ls -ls main/*.exe
-if you built a real-data case, you should see wrf.exe
+If you built the real-data case, you should see wrf.exe
To install WRFPLUS:
Get the WRFPLUS zipped tar file from:
HYPERLINK "http://www.mmm.ucar.edu/wrf/users/wrfda/download/wrfplus.html" http://www.mmm.ucar.edu/wrf/users/wrfda/download/wrfplus.html
-unzip and untar the file to WRFPLUS
+Unzip and untar the file to WRFPLUS
> gzip -cd WRFPLUS3.1.tar.gz | tar -xf -
> cd WRFPLUS
> ./configure wrfplus
@@ -158,7 +158,7 @@
Compile WRFPLUS
> ./compile wrf
> ls -ls main/*.exe
-you should see wrfplus.exe
+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
@@ -177,7 +177,7 @@
Before running obsproc.exe, create the required namelist file namelist.obsproc (see WRFDA/var/obsproc/README.namelist, or the section HYPERLINK \l "_Description_of_Namelist_1" Description of Namelist Variables for details).
For your reference, an example file named namelist_obsproc.3dvar.wrfvar-tut has already been created in the var/obsproc directory. Thus, proceed as follows.
> cp namelist.obsproc.3dvar.wrfvar-tut namelist.obsproc
-Next, edit namelist.obsproc. in this namelist file, you need to change the following variables to accommodate your experiments.
+Next, edit the namelist file namelist.obsproc by changing the following variables to accommodate your experiments.
obs_gts_filename='obs.2008020512'
time_window_min = '2008-02-05_11:00:00',: The earliest time edge as ccyy-mm-dd_hh:mn:ss
time_analysis = '2008-02-05_12:00:00', : The analysis time as ccyy-mm-dd_hh:mn:ss
@@ -212,7 +212,7 @@
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.
> 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 compilation of Map.exe needs pre-installed NCARG Graphics libraries under $(NCARG_ROOT)/lib.
+We have prepared some configure.user.ibm/linux/mac/ files for some platforms, when make is typed, the Ma
kefile 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.
Modify the script Map.csh to set the time window and full path of input observation file (obs_gts_2008-02-05_12:00:00.3DVAR). You will need to set the following strings in this script as follows:
Map_plot = /users/noname/WRFDA/var/obsproc/MAP_plot
TIME_WINDOW_MIN = 2008020511
@@ -225,12 +225,12 @@
It will display (panel by panel) geographical distribution of various types of data. Following is the geographic distribution of sonde observations for this case.
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 figure is not the actual analysis time (0h), it is just used in namelist for time_analysis, the actually time is still 0h.
+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.
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 this 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 analysis time is 2008-02-05_12:00:00, but in namelist, the time_analysis should be set to 3 hours later.
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
@@ -262,7 +262,7 @@
(PREPBUFR also possible) HYPERLINK \l "_Running_Observation_Preprocessor" Observation Preprocessor (OBSPROC)Background Error StatisticsBinary HYPERLINK \l "_Running_gen_be" WRF-Var gen_be utility
/Default CV3In the test case, you will store data in a directory defined by the environment variable $DAT_DIR. This directory can be at any location and it should have read access. Type
> setenv DAT_DIR your_choice_of_dat_dir
-Here, "your_choice_of_dat_dir" is the directory where you aim to store the WRF-Var input data. Create this directory if it does not exist, and type
+Here, "your_choice_of_dat_dir" is the directory where the WRF-Var input data is stored. Create this directory if it does not exist, and type
> cd $DAT_DIR
Download the test data for a Tutorial case valid at 12 UTC 5th February 2008 from HYPERLINK "http://www.mmm.ucar.edu/wrf/users/wrfda/download/testdata.html" http://www.mmm.ucar
.edu/wrf/users/wrfda/download/testdata.html
Once you have downloaded WRFV3.1-Var-testdata.tar.gz file to $DAT_DIR, extract it by typing
@@ -279,17 +279,17 @@
> mv obs_gts_2008-02-05_16:00:00.4DVAR $DAT_DIR/ob/2008020516/ob.ascii
> mv obs_gts_2008-02-05_17:00:00.4DVAR $DAT_DIR/ob/2008020517/ob.ascii
> mv obs_gts_2008-02-05_18:00:00.4DVAR $DAT_DIR/ob/2008020518/ob.ascii-
-Now you have all the three input files (first guess, observation and background error statistics files in directory $DAT_DIR) required to run WRF-Var. Also, you have successfully downloaded and compiled the WRF-Var code. If this is correct, we are ready to learn how to run WRF-Var.
+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, WRFDA/var/test/tutorial is a sample, then follow the steps below:
+To run WRF-3D-Var, first create a working directory such as 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 (link 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)
-vi namelist.input (a very basic namelist.input for running the tutorial test case is shown below. Only time and domain settings need to be specified for a certain case if using default settings provided in WRFDA/Registry/Registry.wrfvar)
+We will begin by editing the file, n
amelist.input, which is a very basic namelist.input for runn!
ing 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)
&wrfvar1
print_detail_grad=false, / &wrfvar2 /
&wrfvar3
@@ -382,7 +382,7 @@
&namelist_quilt
/
> da_wrfvar.exe >&! wrfda.log
-wrfda.log (or rsl.out.0000 if running in distributed-memory mode) contains important WRF-Var runtime log. Always check the log after a WRF-Var run:
+The file wrfda.log (or rsl.out.0000 if running in distributed-memory mode) contains important WRF-Var runtime log information. Always check the log after a WRF-Var run:
*** VARIATIONAL ANALYSIS ***
DYNAMICS OPTION: Eulerian Mass Coordinate
WRF NUMBER OF TILES = 1
@@ -490,13 +490,11 @@
*** WRF-Var completed successfully ***
-A file called namelist.output (which contains the complete namelist settings) will be generated after a successful da_wrfvar.exe run. Those settings appear in namelist.output that are not specified in your namelist.input are the default values from WRFDA/Registry/Registry.wrfvar.
+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 t
he role of various important WRF-Var options, try re-running WRF-Var by changing different namelist options. For example, making WRF-Var convergence criteria more stringent by reducing the value of EPS to e.g. 0.0001 by adding "EPS=0.0001" in namelist.input record &wrfvar6. 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. Last section of this tutorial deals with many such WRF-Var additional exercises.
b. Run the Case4D-Var
-To run WRF-4DVar, create a working directory, WRFDA/var/test/4dvar is a sample,
-Assume the working shell is C shell;
-Assume the directories for WRFD
A , WRFNL and WRFPLUS are :
+To run WRF-4DVar, first create !
a workin
g 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
> setenv WRFDA_DIR /ptmp/$user/WRFDA
> setenv WRFNL_DIR /ptmp/$user/WRFNL
> setenv WRFPLUS_DIR /ptmp/$user/WRFPLUS
@@ -512,7 +510,7 @@
ob/2008020518
rc/2008020512
be
-Note: Currently, WRF-4DVar can only run with the observation data processed by OBSPROC, not work with PREPBUFR format data; WRF-4DVar is able to assimilate satellite radiance BUFR data, but this capability is still under testing.
+Note: Currently, WRF-4DVar can only run with the observation data processed by OBSPROC, and cannot work with PREPBUFR format data; Although WRF-4DVar is able to assimilate satellite radiance BUFR data, but this capability is still under testing.
Assume the working directory is:
> setenv WORK_DIR $WRFDA_DIR/var/test/4dvar
Then follow the steps below:
@@ -568,7 +566,7 @@
> ln -fs ../af05 auxinput3_d01_2008-02-05_16:00:00
> ln -fs ../af06 auxinput3_d01_2008-02-05_17:00:00
> ln -fs ../af07 auxinput3_d01_2008-02-05_18:00:00
-4) Run with 1 processor (serial compilation required for WRFDA, WRFNL and WRFPLUS)
+4) Run in single processor mode (serial compilation required for WRFDA, WRFNL and WRFPLUS)
Edit $WORK_DIR/namelist.input to match your experiment settings.
> cp $WORK_DIR/nl/namelist.input.serial $WORK_DIR/nl/namelist.input
Edit $WORK_DIR/nl/namelist.input to match your experiment settings.
@@ -605,13 +603,13 @@
> cp $WORK_DIR/ad/namelist.input.parallel $WORK_DIR/ad/namelist.input
> cp $WORK_DIR/tl/namelist.input.parallel $WORK_DIR/tl/namelist.input
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. Here, an example command to run WRF 4D-Var on a cluster with 16 processors is:
+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.
-wrfda.log (or rsl.out.0000 if running in parallel mode) contains important WRF-4DVar runtime log. Always check the log after a WRF-4DVar run.
+The file wrfda.log (or rsl.out.0000 if running in parallel mode) contains important WRF-4DVar runtime log information. Always check the log after a WRF-4DVar run.
Radiance Data Assimilations in WRF-Var
-This section gives brief description for various aspects related to radiance assimilation in WRF-Var. Each aspect is described mainly from the viewpoint of usage rather than more technical and scientific details, which will appear in separated technical report and scientific paper. Namelist parameters controlling different aspects of radiance assimilation will be detailed in the following sections. Note that this section does not cover general aspects of WRF-Var a
ssimilation which can be found in other sections of this use!
rs guide
chapter 6 or other WRF-Var documentation.
+This section gives brief description for various aspects related to radiance assimilation in WRF-Var. Each aspect is described mainly from the viewpoint of usage rather than more technical and scientific details, which will appear in separated technical report and scientific paper. Namelist parameters controlling different aspects of radiance assimilation will be detailed in the following sections. . It should be noted that this section does not cover general aspects of the WRF-Var assimilation. These can be found in other sections of chapter 6 of this users guide or other WRF-Var documentation.
a. Running WRF-Var with radiances
@@ -631,20 +629,20 @@
Currently, the ingest interface for NCEP BUFR radiance data is implemented in WRF-Var. The radiance data are available through NCEPs public ftp server ftp://ftp.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/gdas.${yyyymmddhh} in near real-time (with 6-hour delay) and can meet requirements both for research purposes and some real-time applications.
-So far, WRF-Var can read data from the NOAA ATOVS instruments (HIRS, AMSU-A, AMSU-B and MHS), the EOS Aqua instruments (AIRS, AMSU-A) and DMSP instruments (SSMIS). Note that NCEP radiance BUFR files are separated by instrument names (i.e., each file for one type instrument) and each file contains global radiance (generally converted to brightness temperature) within 6-hour assimilation window from multi-platforms. For running WRF-Var, users need to rename NCEP corresponding BUFR files (table 1) to hirs3.bufr (including HIRS data from NOAA-15/16/17), hirs4.bufr (including HIRS data from NOAA-18, METOP-2), amsua.bufr (including AMSU
-A data from NOAA-15/16/18, METOP-2), amsub.bufr (including AMSU-B data from NOAA-15/16/17), mhs.bufr (including MHS data from NOAA-18 and METOP-2), airs.bufr (including AIRS and AMSU-A data from EOS-AQUA) and ssmis.bufr (SSMIS data from DMSP-16, AFWA provided) for WRF-Var filename convention. Note that airs.bufr file contains not only AIRS data but also AMSU-A, which is collocated with AIRS pixels (1 AMSU-A pixels collocated with 9 AIRS pixels). Users also have to place these files in the working directory where WRF-Var executable is located. Should be mentioned that WRF-Var reads directly these BUFR radiance files and no separate pre-processing program is used. All processing of radiance data, such as quality control, thinning and bias correction and so on, is carried out inside WRF-Var. This is different from conventional observation assimilation, which requires a pre-processing package (OBSPROC) to generate WRF-Var readable ASCII files. For reading radiance BUFR files, W
RF-Var must be compiled with NCEP BUFR library (see http://w!
ww.nco.n
cep.noaa.gov/sib/decoders/BUFRLIB/ ).
+So far, WRF-Var can read data from the NOAA ATOVS instruments (HIRS, AMSU-A, AMSU-B and MHS), the EOS Aqua instruments (AIRS, AMSU-A) and DMSP instruments (SSMIS). Note that NCEP radiance BUFR files are separated by instrument names (i.e., each file for one type instrument) and each file contains global radiance (generally converted to brightness temperature) within 6-hour assimilation window from multi-platforms. For running WRF-Var, users need to rename NCEP corresponding BUFR files (table 1) to hirs3.bufr (including HIRS data from NOAA-15/16/17), hirs4.bufr (including HIRS data from NOAA-18, METOP-2), amsua.bufr (including AMSU-A data from NOAA-15/16/18, METOP-2), amsub.bufr (including AMSU-B data from NOAA-15/16/17), mhs.bufr (including MHS data from NOAA-18 and METOP-2), airs.bufr (including AIRS and AMSU-A data from EOS-AQUA) and ssmis.bufr (SSMIS data from DMSP-16, AFWA provided) for WRF-Var filename convention. Note that airs.buf
r file contains not only AIRS data but also AMSU-A, which is collocated with AIRS pixels (1 AMSU-A pixels collocated with 9 AIRS pixels). Users must place these files in the working directory where WRF-Var executable is located. It should also be mentioned that WRF-Var reads these BUFR radiance files directly without use if any separate pre-processing program is used. All processing of radiance data, such as quality control, thinning and bias correction and so on, is carried out inside WRF-Var. This is different from conventional observation assimilation, which requires a pre-processing package (OBSPROC) to generate WRF-Var readable ASCII files. For reading the radiance BUFR files, WRF-Var must be compiled with the NCEP BUFR library (see http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/ ).
Table 1: NCEP and WRF-Var radiance BUFR file naming convention
NCEP BUFR file namesWRF-Var naming conventiongdas1.t00z.1bamua.tm00.bufr_damsua.bufrgdas1.t00z.1bamub.tm00.bufr_d
amsub.bufrgdas1.t00z.1bhrs3.tm00.bufr_dhirs3.bufrgdas1.!
t00z.1bh
rs4.tm00.bufr_dhirs4.bufrgdas1.t00z.1bmhs.tm00.bufr_dmhs.bufrgdas1.t00z.airsev.tm00.bufr_dairs.bufr
-A few namelist parameters are used to control if reading in corresponding BUFR files into WRF-Var or not. For instance, USE_AMSUAOBS, USE_AMSUBOBS, USE_HIRS3OBS, USE_HIRS4OBS, USE_MHSOBS, USE_AIRSOBS, USE_EOS_AMSUAOBS and USE_SSMISOBS control respectively to read the corresponding files or not. These are logical parameters and are assigned to FALSE by default (means that you must switch them to TRUE for reading in these data). Notice also that these parameters only control whether read in the data or not, but not control whether assimilate the data included in the files, which is controlled by other namelist parameters explained in the next section.
+Namelist parameters are used to control the reading of corresponding BUFR files into WRF-Var. For instance, USE_AMSUAOBS, USE_AMSUBOBS, USE_HIRS3OBS, USE_HIRS4OBS, USE_MHSOBS, USE_AIRSOBS, USE_EOS_AMSUAOBS and USE_SSMISOB
S control whether or not the respective file is read. These are logical parameters that are assigned to FALSE by default; therefore they must be set to true to read the respective observation file. Also note that these parameters only control whether the data is read, not whether the data included in the files is to be assimilated. This is controlled by other namelist parameters explained in the next section.
-NCEP BUFR files downloaded from NCEPs public ftp server ftp://ftp.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/gdas.${yyyymmddhh} are Fortran-blocked on big-endian machine and can be directly used on big-endian machines (for example, IBM). For most Linux clusters with Intel platforms, users need to first unblock the BUFR files, then block them. The utility for blocking/unblocking is available from http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/toc/cwordsh
+NCEP BUFR files downloaded from NCEPs public ftp server ftp://ftp.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/gda
s.${yyyymmddhh} are Fortran-blocked on big-endian machine an!
d can be
directly used on big-endian machines (for example, IBM). For most Linux clusters with Intel platforms, users need to first unblock the BUFR files, and then reblock them. The utility for blocking/unblocking is available from http://www.nco.ncep.noaa.gov/sib/decoders/BUFRLIB/toc/cwordsh
c. Radiative Transfer Model
-The core component for direct radiance assimilation is to incorporate radiative transfer model (RTM, should be accurate enough yet fast) into WRF-Var system as one part of observation operators. Two widely used RTMs in NWP community, RTTOV8* developed by EUMETSAT in Europe and CRTM developed by the Joint Center for Satellite Data Assimilation (JCSDA) in US, are already implemented in WRF-Var system with flexible and consistent user interface. Which RTM to use is controlled by a simple namelist parameter RTM_OPTION (1 for RTTOV by default, 2 for CRTM). WRF-Var is designed to be able to compile with only one of two RTM libraries or without RTM libraries (for
those not interested in radiance assimilation) by simple setup of environment variables CRTM and RTTOV (see Installing WRF-Var section).
+The core component for direct radiance assimilation is to incorporate a radiative transfer model (RTM, should be accurate enough yet fast) into the WRF-Var system as one part of observation operators. Two widely used RTMs in NWP community, RTTOV8* (developed by EUMETSAT in Europe), and CRTM (developed by the Joint Center for Satellite Data Assimilation (JCSDA) in US), are already implemented in WRF-Var system with a flexible and consistent user interface. Selecting which RTM to be used is controlled by a simple namelist parameter RTM_OPTION (1 for RTTOV, the default, and 2 for CRTM). WRF-Var is designed to be able to compile with only one of two RTM libraries or without RTM libraries (for those not interested in radiance assimilation) by the definition of environment variables CRTM and RTTOV (see Installing WRF-Var section).
-Bot
h RTMs can calculate radiances for almost all available inst!
ruments
aboard various satellite platforms in orbit. An important feature of WRF-Var design is that all data structures related to radiance assimilation are dynamically allocated during running time according to simple namelist setup. The instruments to be assimilated are controlled by 4 integer namelist parameters in running time: RTMINIT_NSENSOR (total number of sensors to be assimilated), RTMINIT_PLATFORM (platforms IDs array to be assimilated with dimension RTMINIT_NSENSOR, e.g., 1 for NOAA, 9 for EOS, 10 for METOP and 2 for DMSP), RTMINIT_SATID (satellite IDs array) and RTMINIT_SENSOR (sensor IDs array, e.g., 0 for HIRS, 3 for AMSU-A, 4 for AMSU-B, 15 for MHS, 10 for SSMIS, 11 for AIRS). For instance, configuration for assimilating 12 sensors from 7 satellites (what WRF-Var can assimilated currently) will be
+Both RTMs can calculate radiances for almost all available instruments aboard various satellite platforms in orbit. An important feature of WRF-Var design is that all data
structures related to radiance assimilation are dynamically allocated during running time according to simple namelist setup. The instruments to be assimilated are controlled at run time by four integer namelist parameters: RTMINIT_NSENSOR (the total number of sensors to be assimilated), RTMINIT_PLATFORM (the platforms IDs array to be assimilated with dimension RTMINIT_NSENSOR, e.g., 1 for NOAA, 9 for EOS, 10 for METOP and 2 for DMSP), RTMINIT_SATID (satellite IDs array) and RTMINIT_SENSOR (sensor IDs array, e.g., 0 for HIRS, 3 for AMSU-A, 4 for AMSU-B, 15 for MHS, 10 for SSMIS, 11 for AIRS). For instance, the configuration for assimilating 12 sensors from 7 satellites (what WRF-Var can assimilated currently) will be
RTMINIT_NSENSOR = 12 # 5 AMSUA; 3 AMSUB; 2 MHS; 1 AIRS; 1 SSMIS
RTMINIT_PLATFORM = 1,1,1,9,10, 1,1,1, 1,10, 9, 2
@@ -655,7 +653,7 @@
CRTM uses different instrument naming method. A convert routine inside WRF-Var is already created to make CRTM use the same instrument triplet as RTTOV such that the user interface remains the same for RTTOV and CRTM.
-When running WRF-Var with radiance assimilation switched on (RTTOV or CRTM), a set of RTM coefficient files need to be loaded. For RTTOV option, RTTOV coefficient files are to be directly copied or linked under the working directory; for CRTM option, CRTM coefficient files are to be copied or linked to a sub-directory crtm_coeffs under the working directory. Only coefficients listed in namelist are needed. Potentially WRF-Var can assimilate all sensors as long as the corresponding coefficient files are provided with RTTOV and CRTM. In addition, necessary developments on corresponding data interface, quality control and bias correction are also important to make radiance data assimilated properly. However, a modulized design of radiance relevant routines
already facilitates much to add more instruments in WRF-Var.
+When running WRF-Var with radiance assimilation switched on (RTTOV or CRTM), a set of RTM coefficient files need to be loaded. For RTTOV option, RTTOV coefficient files are to be directly copied or linked under the working directory; for CRTM option, CRTM coefficient files are to be copied or linked to a sub-directory crtm_coeffs under the working directory. Only coefficients listed in namelist are needed. Potentially WRF-Var can assimilate all sensors as long as the corresponding coefficient files are provided with RTTOV and CRTM. In addition, necessary developments on corresponding data interface, quality control and bias correction are also important to make radiance data assimilated properly. However, a modular design of radiance relevant routines already facilitates much to add more instruments in WRF-Var.
RTTOV and CRTM packages are not distributed with WRF-Var due to license and support issues. Users
are encouraged to contact the corresponding team for obtaini!
ng RTMs.
See following links for more information.
http://www.metoffice.gov.uk/research/interproj/nwpsaf/rtm/index.html for RTTOV,
@@ -664,7 +662,7 @@
d. Channel Selection
-Channel selection in WRF-Var is controlled by some radiance info files located in the sub-directory radiance_info under the working directory. These files are separated by satellites and sensors, e.g., noaa-15-amsua.info, noaa-16-amsub.info, dmsp-16-ssmis.info and so on. An example for 5 channels from noaa-15-amsub.info is shown below. The fourth column is used by WRF-Var to control if assimilating corresponding channel. Channels with the value -1 indicates not assimilated (channels 1, 2 and 4 in this case), with the value 1 means assimilated (channels 3 and 5). The sixth column is used by WRF-Var to set the observation error for each channel. Other columns are not used by WRF-Var. It should be mentioned that these error values are not necessarily optimal for your applications; it is users responsibility to obtain the optimal error statistics for your own applications.
+Channel selection in WRF-Var is controlled by radiance info files
located in the sub-directory radiance_info under the working directory. These files are separated by satellites and sensors, e.g., noaa-15-amsua.info, noaa-16-amsub.info, dmsp-16-ssmis.info and so on. An example for 5 channels from noaa-15-amsub.info is shown below. The fourth column is used by WRF-Var to control if assimilating corresponding channel. Channels with the value -1 indicates that the channel is not assimilated (channels 1, 2 and 4 in this case), with the value 1 means assimilated (channels 3 and 5). The sixth column is used by WRF-Var to set the observation error for each channel. Other columns are not used by WRF-Var. It should be mentioned that these error values might not necessarily be optimal for your applications; It is users responsibility to obtain the optimal error statistics for your own applications.
sensor channel IR/MW use idum varch polarisation(0:vertical;1:horizontal)
415 1 1 -1 0 0.5500000000E+01 0.0000000000E+
00
@@ -687,7 +685,7 @@
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.
Coldstart
-Coldstarting means starting the VarBC from scratch... i.e. when you do not know the values of the bias parameters.
+Coldstarting means starting the VarBC from scratch i.e. when you do not know the values of the bias parameters.
The Coldstart is a routine in WRF-Var. The bias predictor statistics (mean and standard deviation) are computed automatically and will be used to normalize the bias parameters. All coldstarted bias parameters are set to zero, except the first bias parameter (= simple offset), which is set to the mode (=peak) of the distribution of the (uncorrected) innovations for the given channel.
@@ -699,7 +697,7 @@
It is defined through an integer number in the VARBC.in file. This number is related to a number of observations: the bigger the number, the more inertia constraint. If these numbers are set to zero, the predictors can evolve without any constraint.
Scaling factor
-The VarBC uses a specific preconditioning, which can be scale through a namelist option VARBC_FACTOR (default = 1.0).
+The VarBC uses a specific preconditioning, which can be scaled through a namelist option VARBC_FACTOR (default = 1.0).
Offline bias correction
The analysis of the VarBC parameters can be performed "offline", i.e. independently from the main WRF-Var analysis. No extra code is needed, just set the following MAX_VERT_VAR* namelist variables to be 0, which will disable the standard control variable and only keep the VarBC control variable.
@@ -722,7 +720,7 @@
g. Other namelist variables to control radiance assimilation
RAD_MONITORING (30)
-Integer array with dimension RTMINIT_NSENSER, where 0 for assimilating mode, 1 for monitoring mode (only calculate innovation).
+Integer array of dimension RTMINIT_NSENSER, where 0 for assimilating mode, 1 for monitoring mode (only calculate innovation).
THINNING
Logical, TRUE will perform thinning on radiance data.
@@ -740,10 +738,10 @@
Logical, control if output Observation minus Analysis files (including also O minus B) which are ASCII format and separated by sensors and processors.
USE_ERROR_FACTOR_RAD
-Logical, control if use a radiance error tuning factor file radiance_error.factor, which is created with empirical values or generated using variational tunning method (Desroziers and Ivanov, 2001)
+Logical, controls use of a radiance error tuning factor file radiance_error.factor, which is created with empirical values or generated using variational tunning method (Desroziers and Ivanov, 2001)
ONLY_SEA_RAD
-Logical, control if only assimilating radiance over water.
+Logical, controls whether only assimilating radiance over water.
TIME_WINDOW_MIN
String, e.g., "2007-08-15_03:00:00.0000", start time of assimilation time window
@@ -765,7 +763,7 @@
Logical array with dimension RTMINIT_NSENSER, control if performing Antenna Correction in CRTM.
AIRS_WARMEST_FOV
-Logical, control if using the observation brightness temperature for AIRS Window channel #914 as criterium for GSI thinning.
+Logical, controls whether using the observation brightness temperature for AIRS Window channel #914 as criterium for GSI thinning.
h. Diagnostics and Monitoring
@@ -777,7 +775,7 @@
0 means assimilating mode, innovations (O minus B) are calculated and data are used in minimization.
1 means monitoring mode: innovations are calculated for diagnostics and monitoring. Data are not used in minimization.
-Numbers of rad_monitoring should correspond to number of rtminit_nsensor. If rad_monitoring is not set, then default value of 0 will be used for all sensors.
+Number of rad_monitoring should correspond to number of rtminit_nsensor. If rad_monitoring is not set, then default value of 0 will be used for all sensors.
(2) Outputing radiance diagnostics from WRF-Var
@@ -799,9 +797,9 @@
NCL scripts (WRFDA/var/graphics/ncl/plot_rad_diags.ncl and WRFDA/var/graphics/ncl/advance_cymdh.ncl) are used for plotting. The NCL script can be run from a shell script, or run stand-alone with interactive ncl command (need to edit the NCL script and set the plot options. Also the path of advance_cymdh.ncl, a date advancing script loaded in the main NCL plotting script, may need to be modified).
-Step (3) and (4) can be done by running a single ksh (WRFDA/var/scripts/da_rad_diags.ksh) with proper settings. In addition to the settings of directories and what instruments to plot, there are some useful plotting options, explained below.
+Step (3) and (4) can be done by running a single ksh script (WRFDA/var/scripts/da_rad_diags.ksh) with proper settings. In addition to the settings of directories and what instruments to plot, there are some useful plotting options, explained below.
export OUT_TYPE=ncgmncgm or pdf
-pdf will be much slower than ncgm and generate huge outpu
t if plots are not splitted. But pdf has higher resolution than ncgm.export PLOT_STATS_ONLY=falsetrue or false
+pdf will be much slower than ncgm and generate huge output if plots are not split. But pdf has higher resolution than ncgm.export PLOT_STATS_ONLY=falsetrue or false
true: only statistics of OMB/OMA vs channels and OMB/OMA vs dates will be plotted.
false: data coverage, scatter plots (before and after bias correction), histograms (before and after bias correction), and statistics will be plotted.export PLOT_OPT=sea_onlyall, sea_only, land_onlyexport PLOT_QCED=false
true or false
@@ -822,16 +820,16 @@
WRF-Var Diagnostics
WRF-Var produces a number of diagnostic files that contain useful information on how the data assimilation has performed. This section will introduce you to some of these files, and what to look for.
-Having run WRF-Var, it is important to check a number of output files to see if the assimilation appears sensible. Please download a complimentary WRF-Var package which includes lots of useful scripts from HYPERLINK "http://www.mmm.ucar.edu/wrf/src/data/WRFV3.1-Var-testdata.tar.gz" http://www.mmm.ucar.edu/wrf/src/data/WRFV3.1-Var-testdata.tar.gz
+Having run WRF-Var, it is important to check a number of output files to see if the assimilation appears sensible. The WRF-Var package, which includes lots of useful scripts may be downloaded from HYPERLINK "http://www.mmm.ucar.edu/wrf/users/wrfda/download/tools.html" http://www.mmm.ucar.edu/wrf/users/wrfda/download/tools.html
The content of some useful diagnostic files are as follo
ws:
cost_fn and grad_fn: These files hold (in ASCII format) WRF-Var cost and gradient function values, respectively, for the first and last iterations. However, if you run with PRINT_DETAIL_GRAD=true, these values will be listed for each iteration; this can be helpful for visualization purposes. The NCL script WRFDA/var/graphcs/ncl/plot_cost_grad_fn.ncl may be used to plot the content of cost_fn and grad_fn, if these files are generated with PRINT_DETAIL_GRAD=true.
Note: Make sure that you removed first two 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_01: It holds (in ASCII format) information of all observations that got passed in WRF-Var. Each observation has its observed value, 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.
-name
list.input: WRF-Var input namelist file. It displays all th!
e non-de
fault 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.
+gts_omb_oma_01: It contains (in ASCII format) information on all of the observations used by the WRF-Var run. Each observation has its observed value, quality flag, observation error, observation minus background (OMB), and observation minus analysis (OMA). This information is very useful for both analysis and forecasts verification purposes.
+namelist.input: This is the WRF-Var input namelist file, which contains all the user defined non-default options. Any namelist defined options that do not appear in this file, should have their names checked against values in WRFDA/Registry/Registry.wrfvar.
+namelist.output: A consolidated list of all the namelist options used.
rsl*: Files containing informa
tion 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 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 analysis, and where they are in the WRF-model grid space.
-The WRF-Var ana
lysis file is wrfvar_output. It is in WRF (NetCDF) format. I!
t will b
e 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 boundary conditions).
+The WRF-Var analysis file is wrfvar_output. It is in WRF (NetCDF) format. It will become the input file wrfinput_d01 of any subsequent WRF runs after lateral boundary and/or low boundary conditions are updated by another WRF-Var utility (See section Updating WRF boundary conditions).
A NCL script WRFDA/var/graphics/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 details.
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:
var = "U"
@@ -840,9 +838,9 @@
plot_data = an
When you execute the following command from WRFDA/var/graphics/ncl.
> ncl WRF-Var_plot.ncl
-It will display like:
+The plot should look like:
-You may like to change the variable name, level etc in this script to display the variable of your choice at the desired eta level.
+You may change the variable name, level etc in this script to display the variable of your choice at the desired eta level.
Take time to look through the text output files to ensure you understand how WRF-Var has performed. For example,
How closely has WRF-Var fitted individual observation types? Look at the statistics file to compare the O-B and O-A statistics.
How big are the analysis increments? Again, look in the statistics file to see minimum/maximum values of A-B for each variable at various levels. It will give you a feel of the impact of input observation data you assimilated via WRF-Var by modifying the input analysis first guess.
@@ -861,8 +859,8 @@
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 it consistent with the new WRF-Var initial condition (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 WP
S/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.
+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 wrfbdy files from WPS/real.exe, and a namelist !
file: pa
ram.in for running update_bc.exe. 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
@@ -880,10 +878,10 @@
/
> 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 a copy of wrfvar_output and wrfbdy_d01 to wrfinput_d01 and wrfbdy_d01, respectively, in your WRF working directory.
+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
-From WRFDA version 3.1, the users have two choices to define the background error covariance (BE). We call them CV3 and CV5 respectively. It is difficulty to tell which BE is better; 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. There is no clear cut indication which BE. The impact on analysis varies 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 are estimated with the differences of 24 and 48-hour GFS forecasts with 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.
@@ -1090,10 +1088,10 @@
-WRF-ARW V3: Users Guide 6- PAGE 40
+WRF-ARW V3: Users Guide 6- PAGE 22
-WRF-ARW V3: Users Guide 6- PAGE 41
+WRF-ARW V3: Users Guide 6- PAGE 21
@@ -1114,11 +1112,11 @@
-
-
-&
+
+
+&
@@ -1128,1626 +1126,1620 @@
-h:Tg
+h+'
-h:Tg
-h:Tg
-
+h+'
+h+'
-Px 4 #\'*.25@9
-h:Tg
-h:Tg
-h:Tg
-h:Tg
+Px 4 #\'*.25@9
+h+'
+h+'
+h+'
+/
+h+'
+8
& F
-&
-&
+hhd
+&
+&
&
+hhd
&
+
& F
+hhd
&
-
+
&
+hhd
&
+
& F
+hhd
& F
h(
Hd
-`Hgd:Tg
-H
-h:Tg
+`Hgd+'
+h+'
+L
+L
&
-
-N
-h:Tg
-h:Tg
-h:Tg
-h:Tg
-h:Tg
+
+h+'
+\
+5
+h+'
+i
+h+'
+h+'
l
-l
+l
l
-l
+l
l
-l
+l
l
-l
-
-h:Tg
-h:Tg
-}
-
-h:Tg
-h:Tg
-
-&
-&
-
-h:Tg
+l
+h+'
+h+'
+h+'
+h+'
+h+'
+h+'
+h+'
+
+&
+&
+&
+
t
-l
+l
t
-l
+l
t
l
+
t
-l
+l
t
l
+
t
-l
-
+l
t
-l
-
-
h
-
-h:Tg
-
+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:Tg
-h:Tg
-
-
-
-
-
-
-
-
-
-h:Tg
-
-
-
-
-
-
-
-h:Tg
-h:Tg
-h:Tg
--
--
-&
-h:Tg
-h:Tg
+l
+h+'
+h+'
+
+
+
+
+
+
+
+
+
+h+'
+
+
+
+h+'
+h+'
+.
+h+'
+&
+h+'
+h+'
l
+
,#
-l
+l
,#
-l
+l
+h+'
+h+'
,#
-l
+l
,#
-l
+l
,#
-l
->
-h:Tg
-h:Tg
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
l
+
,#
-l
->
+l
,#
l
-f
+
+f
,#
l
+
l
+
,#
-l
-f
-f
+l
+h+'
+h+'
+f
+f
,#
-l
+l
,#
l
-f
+
+f
,#
l
-D
-h:Tg
-h:Tg
+
,#
l
+
l
-
+
,#
l
+
,#
-l
+l
,#
-l
+l
,#
-l
-D
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
+h+'
,#
-l
+l
,#
-l
+l
+G
,#
-l
+l
,#
-l
-E
-h:Tg
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
-E
+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
-h:Tg
-h:Tg
+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
+
,#
-l
-h:Tg
+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
-h:Tg
-h:Tg
+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
-\
-h:Tg
-h:Tg
+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+'
,#
-l
-f
-h:Tg
-h:Tg
-f
+l
+f
+f
,#
-l
+l
l
+
,#
-l
+l
l
-
+
,#
l
+
,#
l
+
,#
-l
+l
,#
-l
+l
,#
-l
+l
,#
-l
+l
+h+'
+h+'
,#
-l
-h:Tg
-h:Tg
+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
-r
-h:Tg
-h:Tg
+l
#
-l
+l
#
-l
+l
#
-l
+l
#
l
+
#
l
+
#
l
+
#
-l
+l
#
l
+
l
+
#
-l
+l
,#
l
+
+h+'
+h+'
,#
-l
+l
,#
-l
-u
-z
-h:Tg
-h:Tg
+l
,#
-l
+l
,#
l
+
l
+
,#
-l
+l
,#
l
+
,#
l
+
,#
-l
+l
l
+
,#
-l
+l
,#
l
-z
+
l
-z
+
l
+
,#
-l
+l
+
+h+'
,#
l
+
,#
l
+
l
-
-~
-h:Tg
-
-
+
l
+
l
+
,#
-l
+l
l
-
+
,#
l
+
,#
l
+
,#
-l
+l
,#
-l
+l
,#
-l
+l
+h+'
+h+'
,#
-l
+l
,#
-l
+l
,#
-l
-h:Tg
-h:Tg
-h:Tg
+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
-h:Tg
+
#
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
-h:Tg
+
#
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
-h:Tg
+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
-
-
-
-h:Tg
-h:Tg
+l
#
-l
-
+l
#
l
+
#
l
+
#
l
+
#
-l
+l
#
-l
+l
#
l
+
#
l
-
+
+
-
-#
+
+#
Zcd
@@ -3242,9 +3234,9 @@
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
y
+n/I
y
PU0
-
+
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|̇
@@ -3387,10 +3379,9 @@
>.$vܜR @̓ ';;$qU~PvVVW
pg^%
-31
+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&
@@ -3956,9 +3947,9 @@
ũ
%
%Ez @63r/
+
-
+
)wsCO>c8㚚j-ղQ9{>3f}
&lM
@@ -4204,10 +4195,10 @@
t
t
-
-
-{{
+6`6
+
+
+{{
{{2?
qxX_{N? f1_q3
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!
-
-
+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
@@ -4429,9 +4421,9 @@
&Zm=f kTЊMɳ8m6-ШW_uIUQr7廫%r< 7@|',+.K⛮܉Q . }QJw/ߓ_~մWځVy"MiWI
)EE){0eRRSSRSJSSJ22
-2KJRN20lRg ^
-
-
+
+
?uXMLLDFtO>EҥƘ?^oٳnkطoҏ# #Z-n߾m'OF``sPK} X`cbԨQ4+WD߾}z
@@ -4905,9 +4897,9 @@
ZoTZnc\<qR`Y CZn, %TG >VF@OA
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
-
-
+v2\ˠ[PZ\_r XF!(U!/55%5E$_85U$#X 3(U:DM
+
+
J&H(yA@(( >φ4@(zoRAJhUx"|o ܒ{M9Aٹ͙9sf !3'J̓
-
+
& F
l
@@ -7709,13 +7701,13 @@
+
+
+
-
-
+
-
-
+
@d
-@t
-
-w
-
-
-
-
-
-
-
-
-'
-8
->
-?
-V
-t
-
- 0
- 0
- 0
- 0
- 0
- 0
- 0
0
0
d
p
-
-w
-
-
-
-
-
-
-
-'
-8
->
-?
-V
-t
-
"
quot;
uot;
ot;
4d
4d
4d
4d
4d
4d
-@
+@t
+2
+F
+c
+
+
+
+
+A
+Z
+
+
+
+ 0
+ 0
+ 0
+ 0
+ 0
+ 0
+ 0
0
0
P
p
+2
+F
+c
+
+
+
+
+A
+Z
+
+
+
"
quot;
uot;
ot;
+
d
"
"
quot;
4d
`t0
+@
@@ -7841,32 +7825,28 @@
-
z
-
-
-z
-
+
z
+
+
-B
+
-
-
+
+
@@ -7877,68 +7857,87 @@
-
-"
->
-u
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
+
+
+0
j
+-
+Q
+x
+y
+
+
+
+
-?
-A
-V
-
-
-
-
-
-
-
-
-
-
-
-
-
->
-?
-A
-J
-V
-
+7
+<
+L
+Z
+g
+r
^Zp;K`|$~
@@ -7948,40 +7947,34 @@
-^Z
+^Z
-`GT^5bBJ>*N
-8
->
-?
-V
-t
-
+c
+A
+Z
+
+
+
-
+
+
+
-
+
+
+
-
-
-
\ No newline at end of file
+
+
+
\ No newline at end of file
</font>
</pre>