[Mmmdoc-developers] /home/subversion/mmm/doc revision 96
Xiang-Yu Huang
huangx at ucar.edu
Tue Jul 1 11:18:20 MDT 2008
thanks... hans
On Tue, Jul 1, 2008 at 9:55 AM, <mmmdoc-developers at ucar.edu> wrote:
> *duda* 2008-07-01 09:55:28 -0600 (Tue, 01 Jul 2008)
>
> Fix grammar and other wording issues.
> Minor formatting changes.
> Replace first figure with that from the Tech Note.
>
> M users_guide_chap6.doc
> ------------------------------
>
> Modified: trunk/wrf/UsersGuide/users_guide_chap6.doc
> ===================================================================
> --- trunk/wrf/UsersGuide/users_guide_chap6.doc 2008-06-30 22:00:22 UTC (rev 95)
> +++ trunk/wrf/UsersGuide/users_guide_chap6.doc 2008-07-01 15:55:28 UTC (rev 96)
> @@ -1,83 +1,51 @@
> -�Ï ࡱ á
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
> -
>
> +å
> +å
> +å
> sional (4D-Var) data assimilation is the use of a numerical forecast model in the latter.
> -MMM Division of NCAR supports a unified (global/regional, multi-model, 3/4D-Var) model-space variational data assimilation system (WRF-Var) for use by NCAR staff and collaborators, and is also freely available to the general community, together with further documentation, test results, plans etc., from the WRF-Var web-page HYPERLINK "http://www.wrf-model.org/development/group/WG4" http://www.mmm.ucar.edu/wrf/WG4/wrfvar/wrfvar.htm .
> -Various components of the WRF-Var system are shown in blue in the sketch below, together with their relationship with the rest of the WRF system.
> +MMM Division of NCAR supports a unified (global/regional, multi-model, 3/4D-Var) model-space variational data assimilation system (WRF-Var) for use by NCAR staff and collaborators, and is also freely available to the general community, together with further documentation, test results, plans etc., !
> from the WRF-Var web-page HYPERLINK "http://www.wrf-model.org/development/group/WG4" http://www.wrf-model.org/development/group/WG4 .
> +Various components of the WRF-Var system are shown in blue in the sketch below, together with their relationship with rest of the WRF system.
>
> -xb: first guess either from previous WRF forecast or from WPS/real output.
> -yo: observations processed by OBSPROC.
> -Pf: 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 (WPS/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 have to create all these input !
> files yourselves. See section "Running Observation Preprocesso!
> r" for c
> reating your observation files. See section "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 second you can test whether your computer is adequate to run the entire modeling system. After you have done the online tutorial, you can try
> +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, b) WRF NETCDF background file (previous forecast used as a first guess of the analysis), and c) Background error statistics (climatological estimate of errors in the background file). In your own work, you will need to create these input files yourselves.
> +Before using yo!
> ur own data, we suggest that you start by running through the WRF-Var related programs at least once using the supplied test case. This serves two purposes: First, you can learn how to run the programs with data we have tested ourselves, and second, you can test whether your computer is adequate to run the entire modeling system. After you have done the online tutorial, you can try
> Running other, more computationally intensive, case studies.
>
> Experimenting with some of the many namelist variables.
>
> -WARNING: It is impossible to test every code upgrade with every permutation of computer, compiler, number of processors, case, namelist option, etc. The "namelist" options that are supported are indicated in the "WRFDA/Registry/Registry.wrfvar" and these are the default options.
> +WARNING: It is impossible to test every code upgrade with every permutation of computer, compiler, number of processors, case, namelist option, etc. The "namelist" options that are supported are!
> indicated in the "Registry.wrfvar" and these are the default !
> options.
> WRF-Var may be run with options other than the default option by specifying its value via the "wrapper" script. Sample of "wrapper" scripts are included in "var/scripts/wrappers" directory. For running "WRF-Var", you may like to adopt a suitable "wrapper" script in this directory and modify it depending on your case. Note: All scripts are provided for your reference only; we don't have enough resource to support these scripts.
>
> -Running with your own domain. Hopefully, our test cases will have prepared you (and us!) for the variety of ways in which you may wish to run WRF-Var. Please let us know your experiences.
> +Running with your own domain. Hopefully, our test cases will have prepared you for the variety of ways in which you may wish to run WRF-Var. Please let us know your experiences.
>
> As a professional courtesy, we request that you include the following reference in any publications that makes use of any component of the community WRF-Var system:
>
> -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.
> -Running WRF-Var requires a Fortran 90 compiler. We currently support the following platforms: IBM, DEC, SGI, PC/Linux (with HYPERLINK "http://www.pgroup.com/" 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.
> +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.
> +Running WRF-Var requires a Fortran 90 compiler. We!
> currently support the following platforms: IBM, SGI, PC/Linux!
> , Cray-X
> 1, and Apple. 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 in 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, FFTPACK 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/ , HYPERLINK "http://www.cisl.ucar.edu/css/software/fftpack5/" http://www.cisl.ucar.edu/css/software/fftpack5/ and HYPERLINK "http://ww!
> w.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 environment variables might be set w!
> ith
> setenv BLAS /usr/local/blas
> setenv LAPACK /usr/local/lap!
> ack
> set
> env BUFR /usr/local/bufr
> -setenv FFTPACK /usr/local/fftpack
> -Note: If multiple processors will be used to run WRF-Var, MPI-2/MPICH2 should be installed.
> -Hint: for Linux users: If PGI or Intel compiler is used on a Linux computer, makes sure all external libraries are installed using the same compiler.
> -WRF source code tar file can be downloaded from HYPERLINK "http://www.mmm.ucar.edu/wrf/users/download/get_source.html" http://www.mmm.ucar.edu/wrf/users/download/get_source.html . Once the tar file is gunzipped (gunzip WRFDAV3.TAR.gz), and untared (untar WRFDAV3.TAR), and it will create a WRFDA/ directory.
> -Go to WRFDA (top) directory and type
> -./configure wrfda
> -and a list of choices for your computer should appear. These choices range from compiling for a single processor job (serial), to using OpenMP shared-memory (smpar) or distributed-memory parallelization (dmpar) options for multiple processors, or combination of shared-memory and distributed memory optio!
> ns (dm+sm) (see notes below). When a selection is made, a second choice for compiling nesting will appear (see notes below). For example, on a Linux computer, the above steps look like:
> +Hint: Make sure the required libraries were all compiled using the same compiler that will be used to build WRF-Var, since the libraries produced by one compiler may not be compatible with code compiled with another.
> +Assuming all required libraries are available, the WRF-Var Version 3 source code can be downloaded from HYPERLINK "http://www.mmm.ucar.edu/wrf/users/download/get_source.html" http://www.mmm.ucar.edu/wrf/users/download/get_source.html . After the tar file is unzipped (gunzip WRFDAV3.TAR.gz) and untarred (untar WRFDAV3.TAR), the directory WRFDA should be created; this directory contains the WRF-Var source code.
> +To configure WRF-Var, change to the WRFDA directory and type
> > ./configure wrfda
> +A list of configuration options for your computer should appear. Eac!
> h option combines a compiler type and a parallelism option; si!
> nce the
> configuration script doesn't check which compilers are actually available, be sure to only select among the options for compilers that are available on your system. The parallelism option allows for a single-processor (serial) compilation, shared-memory parallel (smpar) compilation, distributed-memory parallel (dmpar) compilation, or a combination of shared-memory and distributed-memory parallel (dm+sm) compilation; for WRF-Var, parallel execution requires a "dm" option (see note below). After a selection from the list of options is made, a second choice for compiling nesting will appear. For example, on a Linux computer, the above steps look like:
> +> ./configure wrfda
> checking for perl5... no
> checking for perl... found /usr/bin/perl (perl)
> Will use NETCDF in dir: /karri/users/xinzhang/external/netcdf/netcdf-3.6.1/pgi_x86_64
> @@ -114,587 +82,351 @@
> Enter selection [1-24] : 3
> ------------------------------------------------------------------------
> Compile for nesting? (1=basic, 2=preset moves, 3=vortex following) [default 1]: 1
> -… …
> -Enter appropriate options that are best for your computer and application.
> -When the return key is hit, a configure.wrf file will be created. Edit compile options/paths, if necessary.
> -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 compilation.
> -Note: nesting does not apply to WRF-Var, so 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.
> -Hint: It i!
> s 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.
> +Note: The WRF-Var system does not make usre of OpenMP, so shared memory (smpar) options do not apply to WRF-Var; parallel execution is only supported through distributed memory (dmpar) options.
> +Note: Nesting does not apply to WRF-Var, please select 1=basic.
> +After running the configure script and choosing a compilation and nesting option, a configure.wrf file will be created. Because of the variety of ways that a computer can be configured, if the WRF-Var build ultimately fails, there is a chance that minor modifications to the configure.wrf file may be needed.
> +Hint: It is helpful to start with a very basic configuration, 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 the code, type
> -./compile all_wrfvar
> -Successful com!
> pilation 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)
> -> ls -l var/da/*exe
> +> ./compile all_wrfvar
> +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 the WRFDA directory)
> +> ls -l var/da/*exe
>
> --rwxr-xr-x 1 2450389 Jun 16 11:45 var/da/da_advance_time.exe
> --rwxr-xr-x 1 2622925 Jun 16 11:46 var/da/da_tune_obs_desroziers.exe
> --rwxr-xr-x 1 2599307 Jun 16 11:46 var/da/da_tune_obs_hollingsworth1.exe
> --rwxr-xr-x 1 2469588 Jun 16 11:46 var/da/da_tune_obs_hollingsworth2.exe
> --rwxr-xr-x 1 2786060 Jun 16 11:46 var/da/da_update_bc.exe
> --rwxr-xr-x 1 3046675 Jun 16 11:46 var/da/da_verif_anal.exe
> --rwxr-xr-x 1 2518174 Jun 16 11:45 var/da/da_verif_obs.exe
> --rwxr-xr-x 1 23928871 Jun 16 11:45 var/da/da_wrfvar.exe
> -lrwxrwxrwx 1 26 Jun 16 11:46 var/da/gen_be_cov2d.exe -> ../gen_be/gen_!
> be_cov2d.exe
> -lrwxrwxrwx 1 26 Jun 16 11:46 var/da/gen_be_cov3d.exe -> ../gen_be/gen_be_cov3d.exe
> -lrwxrwxrwx 1 26 Jun 16 11:46 var/da/gen_be_diags.exe -> ../gen_be/gen_be_diags.exe
> -lrwxrwxrwx 1 31 Jun 16 11:46 var/da/gen_be_diags_read.exe -> ../gen_be/gen_be_diags_read.exe
> -lrwxrwxrwx 1 28 Jun 16 11:46 var/da/gen_be_ensmean.exe -> ../gen_be/gen_be_ensmean.exe
> -lrwxrwxrwx 1 26 Jun 16 11:46 var/da/gen_be_ensrf.exe -> ../gen_be/gen_be_ensrf.exe
> -lrwxrwxrwx 1 24 Jun 16 11:46 var/da/gen_be_ep1.exe -> ../gen_be/gen_be_ep1.exe
> -lrwxrwxrwx 1 24 Jun 16 11:46 var/da/gen_be_ep2.exe -> ../gen_be/gen_be_ep2.exe
> -lrwxrwxrwx 1 25 Jun 16 11:46 var/da/gen_be_etkf.exe -> ../gen_be/gen_be_etkf.exe
> -lrwxrwxrwx 1 31 Jun 16 11:46 var/da/gen_be_stage0_wrf.exe -> ../gen_be/gen_be_stage0_wrf.exe
> -lrwxrwxrwx 1 33 Jun 16 11:46 var/da/gen_be_stage1_1dvar.exe -> ../gen_be/gen_be_stage1_1dvar.exe
> -lrwxrwxrwx 1 27 Jun 16 11:46 var/da/gen_be_stage1.exe -> ../gen_be/gen_be!
> _stage1.exe
> -lrwxrwxrwx 1 3 Jun 16 11:46 var/da/gen_be_stage2_!
> 1dvar.ex
> e -> ../gen_be/gen_be_stage2_1dvar.exe
> -lrwxrwxrwx 1 28 Jun 16 11:46 var/da/gen_be_stage2a.exe -> ../gen_be/gen_be_stage2a.exe
> -lrwxrwxrwx 1 27 Jun 16 11:46 var/da/gen_be_stage2.exe -> ../gen_be/gen_be_stage2.exe
> -lrwxrwxrwx 1 27 Jun 16 11:46 var/da/gen_be_stage3.exe -> ../gen_be/gen_be_stage3.exe
> -lrwxrwxrwx 1 34 Jun 16 11:46 var/da/gen_be_stage4_global.exe -> ../gen_be/gen_be_stage4_global.exe
> -lrwxrwxrwx 1 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.
> -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 fo!
> r 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.
> -Executables for running WRF-Var and gen_be are created at this step. Proceed to the next section to learn how to build OBSPROC.
> -Running Observation Preprocessor (OBSPROC)
> -OBSPROC program reads in 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 o!
> f some freely available observations and the program for conve!
> rting th
> e observations to LITTLE_R format. 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
> -Basic operations performed by OBSPROC are:
> -1) Remove observations outside the time range and domain (horizontal and top).
> -2) Re-order and merge duplicate (in time and location) data reports.
> -3) Retrieve pressure or height based on observed information using the hydrostatic assumption.
> -4) Check vertical consistency and super adiabatic for multi-level observations.
> -5) Assign observational errors based on a pre-specified error file.
> -6) Write out the observation file to be used by WRF-Var in ASCII or BUFR format.
> -7) Plot the distribution of each observation type.
> +-rwxr-xr-x 1 users 2450389 Jun 16 11:45 var/da/da_advance_time.exe
> +-rwxr-xr-x 1 user!
> s 3219026 Jun 16 11:45 var/da/da_bias_airmass.exe
> +-rwxr-xr-x 1 users 2803020 Jun 16 11:45 var/da/da_bias_scan.exe
> +-rwxr-xr-x 1 users 2775303 Jun 16 11:45 var/da/da_bias_sele.exe
> +-rwxr-xr-x 1 users 3110924 Jun 16 11:45 var/da/da_bias_verif.exe
> +-rwxr-xr-x 1 users 2765725 Jun 16 11:46 var/da/da_rad_diags.exe
> +-rwxr-xr-x 1 users 2622925 Jun 16 11:46 var/da/da_tune_obs_desroziers.exe
> +-rwxr-xr-x 1 users 2599307 Jun 16 11:46 var/da/da_tune_obs_hollingsworth1.exe
> +-rwxr-xr-x 1 users 2469588 Jun 16 11:46 var/da/da_tune_obs_hollingsworth2.exe
> +-rwxr-xr-x 1 users 2786060 Jun 16 11:46 var/da/da_update_bc.exe
> +-rwxr-xr-x 1 users 3046675 Jun 16 11:46 var/da/da_verif_anal.exe
> +-rwxr-xr-x 1 users 2518174 Jun 16 11:45 var/da/da_verif_obs.exe
> +-rwxr-xr-x 1 users 23928871 Jun 16 11:45 var/da/da_wrfvar.exe
> +lrwxrwxrwx 1 users 26 Jun 16 11:46 var/da/gen_be_cov2d.exe -> ../gen_be/gen_be_cov2d.exe
> +lrwxrwxrwx 1 users 26 Jun 16 11:46 var/da/gen_be_cov3d.exe -> ../!
> gen_be/gen_be_cov3d.exe
> +lrwxrwxrwx 1 users 26 Jun 16 11!
> :46 var/
> da/gen_be_diags.exe -> ../gen_be/gen_be_diags.exe
> +lrwxrwxrwx 1 users 31 Jun 16 11:46 var/da/gen_be_diags_read.exe -> ../gen_be/gen_be_diags_read.exe
> +lrwxrwxrwx 1 users 28 Jun 16 11:46 var/da/gen_be_ensmean.exe -> ../gen_be/gen_be_ensmean.exe
> +lrwxrwxrwx 1 users 26 Jun 16 11:46 var/da/gen_be_ensrf.exe -> ../gen_be/gen_be_ensrf.exe
> +lrwxrwxrwx 1 users 24 Jun 16 11:46 var/da/gen_be_ep1.exe -> ../gen_be/gen_be_ep1.exe
> +lrwxrwxrwx 1 users 24 Jun 16 11:46 var/da/gen_be_ep2.exe -> ../gen_be/gen_be_ep2.exe
> +lrwxrwxrwx 1 users 25 Jun 16 11:46 var/da/gen_be_etkf.exe -> ../gen_be/gen_be_etkf.exe
> +lrwxrwxrwx 1 users 31 Jun 16 11:46 var/da/gen_be_stage0_wrf.exe -> ../gen_be/gen_be_stage0_wrf.exe
> +lrwxrwxrwx 1 users 33 Jun 16 11:46 var/da/gen_be_stage1_1dvar.exe -> ../gen_be/gen_be_stage1_1dvar.exe
> +lrwxrwxrwx 1 users 27 Jun 16 11:46 var/da/gen_be_stage1.exe -> ../gen_be/gen_be_stage1.exe
> +lrwxrwxrwx 1 u!
> sers 33 Jun 16 11:46 var/da/gen_be_stage2_1dvar.exe -> ../gen_be/gen_be_stage2_1dvar.exe
> +lrwxrwxrwx 1 users 28 Jun 16 11:46 var/da/gen_be_stage2a.exe -> ../gen_be/gen_be_stage2a.exe
> +lrwxrwxrwx 1 users 27 Jun 16 11:46 var/da/gen_be_stage2.exe -> ../gen_be/gen_be_stage2.exe
> +lrwxrwxrwx 1 users 27 Jun 16 11:46 var/da/gen_be_stage3.exe -> ../gen_be/gen_be_stage3.exe
> +lrwxrwxrwx 1 users 34 Jun 16 11:46 var/da/gen_be_stage4_global.exe -> ../gen_be/gen_be_stage4_global.exe
> +lrwxrwxrwx 1 users 36 Jun 16 11:46 var/da/gen_be_stage4_regional.exe -> ../gen_be/gen_be_stage4_regional.exe
> +After successful compilation of WRF-Var, you are ready to run WRF-Var for the test case.
>
> -WRF-Var observation preprocessor is residing under "WRFDA/var/obsproc" directory
> - > 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 nameli!
> st 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" has already been created. Thus, proceed as follows.
> - > cp namelist.3dvar_obs.wrfvar-tut namelist.3dvar_obs
> -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 file: 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.
> -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,
> -GPSZD = 0, GPSRF = 0, GPSEP = 0, SSMT1 = 0, SSMT2 = 0, TOVS = 0,
> -QSCAT = 0, PROFL = 0, AIRSR = 0, OTHER = 0,
> -PHIC = 40.92, XLONC = -98.00, TRUE1 = 30.00, TRUE2 = 60.00, XIM11 = 9.00, XJM11 = 9.00,
> -base_temp= 300.00, base_lapse= 50.00, PTOP = 5000., base_pres=100000., base_tropo_pres= 20000., base_st
> -rat_temp= 215.,
> -IXC = 61, JXC = 61, IPROJ = 1, IDD = 2, MAXNES= 2,
> -NESTIX= 61, 45,
> -NESTJX= 61, 45,
> -NUMC = 1, 1,
> -DIS = 200.00, 200.00,
> -NESTI = 1, 9,
> -NESTJ = 1, 9,
> -INFO = PLATFORM, DATE, NAME, LEVELS, LATITUDE, LONGITUDE, ELEVATION, ID.
> -SRFC = SLP, PW (DATA,QC,ERROR).
> -EACH = P!
> RES, SPEED, DIR, HEIGHT, TEMP, DEW PT, HUMID (DATA,QC,ERROR)*L!
> EVELS.
> -
> INFO_FMT = (A12,1X,A19,1X,A40,1X,I6,3(F12.3,11X),6X,A5)
> -SRFC_FMT = (F12.3,I4,F7.2,F12.3,I4,F7.3)
> -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.
> -> 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.3DVAR). Precisely, the following string in this script as follows.
> - TIME_WINDOW_MIN = '2007010121'
> - TIME_ANALYSIS = '2007010200'
> - TIME_WINDOW_MAX = '2!
> 007010203'
> - OBSDATA = ../obs_gts_2007-01-02_00:00:00.3DVAR
> -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.3DVAR. To view this, type
> - > idt gmeta.2007010200
> -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.
>
> -
>
> +
> Running WRF-Var
> +In this section, you will learn how to run WRF-Var using observations and a first guess from a low-resolution (200 km) CONUS domain.
> a. Download Test Data
> -The WRF-Var system requires three input files to run: a) A WRF first guess input format file output from either WPS/real (cold-start) or WRF (warm-start), b) Observations !
> (in ASCII format or PREBUFR), and c) A background error statis!
> tics fil
> e (containing background error covariance currently calculated via the NMC-method), using "gen_be" utility of WRF-Var.
> +The WRF-Var system requires three input files to run: a) A WRF first guess input format file output from either WPS (cold-start) or WRF itself (warm-start), b) Observations (in ASCII little_r format or PREBUFR), and c) A background error statistics file (containing background error covariance currently calculated via the NMC-method using "gen_be" utility of WRF-Var).
> The following table summarizes the above info:
> -Input Data Format Created By First Guess
> - NETCDF WRF Preprocessing System (WPS) and real.exe
> +Input Data Format Created By
> +First Guess
> + NETCDF WRF Preprocessing System (WPS)
> or WRF Observations ASCII
> -(PREPBUFR also possible) HYPERLINK \l "_Running_Observation_Preprocessor" Observation Preprocessor (OBSPROC) Background Error Statistics Binary HYPERLINK \l "_Running_gen_be" WRF-Var gen_be utility In the !
> online tutorial, 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. To run this case it is desired to have at least 100MB of memory to be made available on your machine (maybe much more for other cases). 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
> +(PREPBUFR also possible) HYPERLINK \l "_Running_Observation_Preprocessor" Observation Preprocessor (OBSPROC) Background Error Statistics Binary HYPERLINK \l "_Running_gen_be" WRF-Var gen_be utility In the online tutorial, 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. To run this case there should be at least 100MB of space available (o!
> ther cases can require significantly more). Type
> + setenv DAT!
> _DIR dat
> _dir
> +Here, "dat_dir" is your own chosen directory where WRF-Var input data will be stored. Create this directory, if it does not exist, and type
> cd $DAT_DIR
> -Download the tutorial test data for a "con200" case valid at 00 UTC 02 January 2007 from
> +Download the tutorial test data for the "con200" case, which is valid at 0000 UTC on 02 January 2007, from
> HYPERLINK "http://www.mmm.ucar.edu/wrf/src/data/WRFV3-Var-testdata.tar.gz" http://www.mmm.ucar.edu/wrf/src/data/WRFV3-Var-testdata.tar.gz
> -Once you have downloaded "WRFV3-Var-testdata.tar.gz" file to $DAT_DIR, extract it by typing
> +Once you have downloaded WRFV3-Var-testdata.tar.gz file to $DAT_DIR, extract it by typing
> gunzip WRFV3-Var-testdata.tar.gz
> tar -xvf WRFV3-Var-testdata.tar
> -Now you should find the following three sub-directories/files under "$DAT_DIR"
> - ob/2007010200/ob.little_r ### Observation data in "little_r" format
> - rc/2007010200/wrfinput_d01 ###First guess fil!
> e
> - rc/2007010200/wrfbdy_d01 ### lateral boundary file
> - be/be.dat ### Background error file
> -You should first go through the section "Running Observation Preprocessor (OBSPROC)" and have a WRF-Var-ready observation file (obs_gts_2007-01-02_00:00:00.3DVAR) generated in your OBSPROC working directory. You could then copy or move obs_gts_2007-01-02_00:00:00.3DVAR to be in $DAT_DIR/ob/2007010200.
> -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.
> +After unpacking the test data, the following directories and files should exist within $DAT_DIR
> +ob/2007010200/ob.little_r (Observation data in "little_r" format)
> +rc/2007010200/wrfinput_d01(First guess file)
> +rc/2007010200/wrfbdy_d01(Lateral boundary file)!
>
> +be/be.dat (Background error file)
> +By this point, you have a!
> ll three
> input files (first guess, observation, and background error statistics) required to run WRF-Var. Also, you have successfully downloaded and compiled the WRF-Var code. If not, these steps must first be completed in order to run the test case.
> b. Run The Case
> -The data for this case is valid at 00 UTC 2nd January 2007. The first guess comes from the NCEP global final analysis system (FNL), passed through the WRF-WPS and real programs. The first-guess level 18 potential temperature field is shown below, illustrating the domain:
> +The data for this case is valid at 00 UTC, 2nd January 2007. The first guess comes from the NCEP global final analysis system (FNL), passed through the WPS and real pre-processing packages. The first-guess level 18 potential temperature field is shown below, illustrating the domain:
>
> -Hint: various NCL scripts are included under var/graphics/ncl sub-directory to display results.
> -To run WRF-Var, first create a working directory, for example, WRFDA/!
> var/test, then follow the steps below:
> -cd WRFDA/var/test (go to the working directory)
> -ln -sf WRFDA/run/LANDUSE.TBL ./LANDUSE.TBL
> -ln -sf $DAT_DIR/rc/2007010200/wrfinput_d01 ./fg (link first guess file as fg)
> -ln -sf WRFDA/var/obsproc/obs_gts_2007-01-02_00: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)
> -&wrfvar1 / &wrfvar2 /
> -&wrfvar3
> -/
> -&wrfvar4
> -/
> -&wrfvar5
> -/
> -&wrfvar6
> -/
> -&wrfvar7
> -/
> -&wrfvar8
> -/
> -&wrfvar9
> -trace_use=false, (Note: if not specified, default trace_use=true is applied. A subdirectory trace has to be create!
> d in your working directory before running da_wrfvar.exe)
> -/
> -!
> &wrf
> var10
> -/
> -&wrfvar11
> -/
> -&wrfvar12
> -/
> -&wrfvar13
> -/
> -&wrfvar14
> -/
> -&wrfvar15
> -/
> -&wrfvar16
> -/
> -&wrfvar17
> -/
> -&wrfvar18
> -analysis_date="2007-01-02_00:00:00.0000",
> -/
> -&wrfvar19
> -/
> -&wrfvar20
> -/
> -&wrfvar21
> -time_window_min="2007-01-01_21:00:00.0000",
> -/
> -&wrfvar22
> -time_window_max="2007-01-02_03:00:00.0000",
> -/
> -&wrfvar23
> -/
> -&time_control
> -start_year=2007,
> -start_month=01,
> -start_day=02,
> -start_hour=00,
> -end_year=2007,
> -end_month=01,
> -end_day=02,
> -end_hour=00,
> -/
> -&dfi_control
> -/
> -&domains
> -e_we=45,
> -e_sn=45,
> -e_vert=28,
> -dx=200000,
> -dy=200000,
> -/
> -&physics
> -mp_physics=3,
> -sf_surface_physics=1,
> -num_soil_layers=5, (IMPORTANT: it's essential to make sure the setting here is consistent with the number in your first guess file)
> -/
> -&fdda
> -/
> -&dynamics
> -/
> -&bdy_control
> -/
> -&grib2
> -/
> -&namelist_quilt
> -/
> -da_wrfvar.exe >&! wrfda.log
> -wrfda.log (or rsl.out.000!
> 0 if running in MPP mode) contains important WRF-Var runtime log. Always check the log after a WRF-Var run:
> -*** VARIATIONAL ANALYSIS ***
> - Ntasks in X 1 , ntasks in Y 1
> - *************************************
> - Parent domain
> - ids,ide,jds,jde 1 45 1 45
> - ims,ime,jms,jme -4 50 -4 50
> - ips,ipe,jps,jpe 1 45 1 45
> - *************************************
> - DYNAMICS OPTION: Eulerian Mass Coordinate
> - WRF NUMBER OF TILES = 1
> -Set up observations (ob)
> +Note: In WRF-Var, various NCL scripts are included under the var/graphics/ncl sub-directory to display results.
> +We provide a sample script to run the codes in WRFDA/var/scripts/wrappers/da_run_suite_wrapper_con200.ksh. In order to use the script, the following environment variables need to be set in this script.
> +REL_DIR - Full path of the parent code directory
> +WRFVAR_DIR - Full dir!
> ectory path of wrfvar under $REL_DIR
> +DAT_DIR - Full path of !
> data inp
> ut holding ob, be, rc directories
> +REGION - String representing region under $DAT_DIR
> +OB_DIR - Full path for Observation directory
> +RC_DIR - Full path for "FG" directory
> +BE_DIR - Full path for "background error (BE)" directory
> +INITIAL_DATE - Initial date for running WRF-Var
> +FINAL_DATE - Final date for running WRF-Var
>
> -Using ASCII format observation input
> -
> - scan obs ascii
> - end scan obs ascii
> -Observation summary
> - ob time 1
> - sound 122 global, 121 local
> - synop 1007 global, 995 local
> - pilot 112 global, 112 local
> - satem 204 global, 203 local
> - geo amv 18216 global, 17336 local
> - polar amv 0 global, 0 local
> - airep 1527 global, 1521 local
> - gpspw 113 global, 113 local
> - gpsrf 0 global, 0 local
> - metar 2551 global, 2543 local
> - ship 270 global, 260 local
> - ssmi_!
> rv 0 global, 0 local
> - ssmi_tb 0 global, 0 local
> - ssmt1 0 global, 0 local
> - ssmt2 0 global, 0 local
> - qscat 0 global, 0 local
> - profiler 0 global, 0 local
> - buoy 241 global, 236 local
> - bogus 0 global, 0 local
> - pseudo 0 global, 0 local
> - radar 0 global, 0 local
> - radiance 0 global, 0 local
> - airs retrieval 0 global, 0 local
> - sonde_sfc 122 global, 121 local
> - mtgirs 0 global, 0 local
> -
> -Set up background errors for regional application
> - WRF-Var dry control variables are:psi, chi_u, t_u and psfc
> - Humidity control variable is q/qsg
> - Using the averaged regression coefficients for unbalanced part
> -
> -Vertical truncation for psi = 15( 99.00%)
> +The following environment variables are optional:
> +E!
> XPT - Experiment ID (expt)
> +RUN_DIR - Full path for run direct!
> ory
> +FC
> _DIR - Analysis output directory
> +Note: Since output is written in $RUN_DIR, it is important for this directory to have write permissions enabled for the user account under which the test case will be run.
> +Once you have set the necessary environment variables, the case may be run by typing
> + da_run_suite_wrapper_con200.ksh
> +in the WRFDA/var/scripts/wrappers subdirectory (or from the directory where your modified wrapper script is located).
> +Successful completion of the test case results in a number of output diagnostic files in the ${RUN_DIR} directory. The final analysis file (wrfinput_d01) will appear under the ${FC_DIR}/2007010200 directory. The various textual diagnostics output files will be explained in the next section ( HYPERLINK \l "_WRF-Var_Diagnostics_1" WRF-Var Diagnostics ).
> +In order to understand the role of various important WRF-Var options, try re-running WRF-Var by changing different namelist options via the wrapper script. For example, ma!
> ke the WRF-Var minimization convergence criteria more stringent by reducing the value of "EPS" to, e.g., 0.0001 by setting "NL_EPS=0.0001" in your wrapper script. If WRF-Var has not converged by the maximum number of iterations (NTMAX=200) then you may need to increase the value of NTMAX variable by setting "export NL_NTMAX=500" in your wrapper script, and in this event, you may like to run the case again. The last section of this tutorial deals with many such WRF-Var additional exercises.
> +Note: You may like to change the ${RUN_DIR} environment variable to store results separately for each run. In your wrapper script, setting the option "CLEAN=true" can save lot of space, since this option removes the contents of the "working" directory.
>
> -Vertical truncation for chi_u = 18( 99.00%)
> -
> -Vertical truncation for t_u = 24( 99.00%)
> -
> -Vertical truncation for rh = 21( 99.00%)
> -
> -
> -Calculate innovation vector(iv)
> - !
>
> -Minimize cost function using CG method
> -For this run cost !
> function
> diagnostics will be written
> -
> -Starting outer iteration : 1
> -
> -Original gradient is 5.11285903D+02
> -For this outer iteration gradient target is 5.11285903D+00
> -Starting cost function: 3.75916289D+04 gradient= 5.11285903D+02
> -----------------------------------------------------------
> -Iter Cost Function Gradient Step
> - 1 3.52745747D+04 4.22893275D+02 1.77271355D-02
> - 2 3.36106840D+04 3.02695549D+02 1.86077231D-02
> - 3 3.24416329D+04 3.13509134D+02 2.55182799D-02
> - 4 3.14863535D+04 2.70049441D+02 1.94383780D-02
> - 5 3.07151345D+04 1.97752468D+02 2.11505260D-02
> - 6 3.01681604D+04 1.90679484D+02 2.79738918D-02
> - 7 2.98118845D+04 1.48417585D+02 1.95978521D-02
> - 8 2.94419853D+04 1.13477806D+02 3.35847985D-02
> - 9 2.92227775D+04 8.57960292D+01 3.40458452D-02
> - 10 2.90802889D+04 7.76454162D+01 !
> 3.87146721D-02
> - 11 2.89758281D+04 6.38614713D+01 3.46538671D-02
> - 12 2.89116212D+04 5.07339439D+01 3.14871956D-02
> - 13 2.88643346D+04 4.24947979D+01 3.67427178D-02
> - 14 2.88301177D+04 3.12058420D+01 3.78964627D-02
> - 15 2.88123982D+04 2.49212482D+01 3.63923716D-02
> - 16 2.87995001D+04 2.08189476D+01 4.15352477D-02
> - 17 2.87903434D+04 1.59621535D+01 4.22523996D-02
> - 18 2.87843493D+04 1.30676595D+01 4.70506154D-02
> - 19 2.87805743D+04 9.41818099D+00 4.42135584D-02
> - 20 2.87784444D+04 7.45330718D+00 4.80233115D-02
> - 21 2.87770601D+04 6.25547789D+00 4.98386142D-02
> - 22 2.87762347D+04 4.79613214D+00 4.21877119D-02
> -----------------------------------------------------------
> -
> -Inner iteration stopped after 22 iterations
> -
> -Final: 22 iter, J= 2.87762347D+04, g= 4.79613214D+00
> ------------------------!
> -----------------------------------
> -
> -rsl.out.0000 (p4 of 4)
> !
> -Diagnos
> tics
> - Final cost function J = 28776.23
> -
> - Total number of obs. = 69249
> - Final value of J = 28776.23467
> - Final value of Jo = 26116.53564
> - Final value of Jb = 2659.69904
> - Final value of Jc = 0.00000
> - Final value of Je = 0.00000
> - Final value of Jp = 0.00000
> - Final J / total num_obs = 0.41555
> - Jb factor used(1) = 1.00000
> - Jb factor used(2) = 1.00000
> - Jb factor used(3) = 1.00000
> - Jb factor used(4) = 1.00000
> - Jb factor used(5) = 1.00000
> - Jb factor used = 1.00000
> - Je factor used = 1.00000
> - VarBC factor used = 1.00000
> -
> -SUCCESS COMPLETE WRFVAR
> -
> - *** 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.
> -After successful completion of job, wrfvar_output (the WRF-Var analysis file, i.e. the new initial condition for WRF) should appear in the working directory along with a number of diagnostic files. Various text diagnostics output files will be explained in the next section ( HYPERLINK \l "_WRF-Var_Diagnostics_1" WRF-Var Diagnostics ).
> -In order to understand the role of various important WRF-Var options, try re-running WRF-Var by changing different namelist options. 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.
> -
> WRF-Var Diagnostics
> W!
> RF-Var produces a number of diagnostic files that contain usef!
> ul infor
> mation 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. In the working directory where you ran this case:
> +Having run WRF-Var, it is important to check a number of output files to see if the assimilation appears sensible. Change directory to where you ran this case:
> + > cd ${RUN_DIR}/2007010200/wrfvar
> > ls -l
> -You will see the following files generated after a successful WRF-Var run:
> --rw-r--r-- 1 xinzhang 2248804 Jun 18 13:17 check_max_iv
> --rw-r--r-- 1 xinzhang 1985 Jun 18 13:17 cost_fn
> --rw-r--r-- 1 xinzhang 1745 Jun 18 13:17 grad_fn
> --rw-r--r-- 1 xinzhang 9048641 Jun 18 13:17 gts_omb_oma
> --rw-r--r-- 1 xinzhang 2167 Jun 18 13:17 jo
> --rw-r--r-- 1 xinzhang 2009 Jun 18 13:16 namelist.input
> --rw-r--r-- 1 xinzhang 276658 Jun 18 13:17 namelist.output
> --rw-r--r-- 1 xinz!
> hang 22730 Jun 18 13:17 statistics
> -drwxr-xr-x 2 xinzhang 4096 Jun 18 13:15 trace
> --rw-r--r-- 1 xinzhang 4393186 Jun 18 13:17 unpert_obs
> --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 two files hold (in ASCII format) WRF-Var cost & gradient function values respectively for only the first and last iterations. If you set "CALCULATE_CG_COST_FN=true" (in record &WRFVAR11 in namelist.input), the cost function value of each iteration will be calculated, however, the run time will be significantly increased. A NCL script (WRFDA/var/graphcs/ncl/plot_cost_grad_fn.ncl) is provided for plotting the content of "cont_fn" & "grad_fn" generated with "CALCULATE_CG_COST_FN=true".
> - Note: Make sure that you removed first two lines (header) in "cost_fn" & "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 all observations that got pas!
> sed in W
> RF-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.
> -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.
> -rsl*: 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 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 analysis file is wrfvar_output". 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").
> -A NCL script "WRFDA/var/graphcs/ncl/WRF-Var_plot.ncl", is provided for plotting. You need to spe!
> cify 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"
> -fg = first_guess->U
> -an = analysis->U
> -plot_data = an
> -When you execute the following command from "WRFDA/var/graphics/ncl".
> - > ncl WRF-Var_plot.ncl
> -It will display like:
> +You will see something like the following:
> +total 15748
> +-rw-r--r-- 1 users 2248804 Jun 18 13:17 check_max_iv
> +-rw-r--r-- 1 users 1985 Jun 18 13:17 cost_fn
> +-rw-r--r-- 1 users 1745 Jun 18 13:17 grad_fn
> +-rw-r--r-- 1 users 9048641 Jun 18 13:17 gts_omb_oma
> +-rw-r--r-- 1 users 8213 Jun 18 13:17 index.html
> +-rw-r--r-- 1 users 2167 Jun 18 13:17 jo
> +-rw-r--r-- 1 users 2009 Jun 18 13:16 namelist.input
> +-rw-r--r-- 1 users 276658 Jun 18 13:17 namelist.output
> +-rw-r--r-- 1 user!
> s 22730 Jun 18 13:17 statistics
> +drwxr-xr-x 2 users 4096 Jun 18 13:15 trace
> +-rw-r--r-- 1 users 4393186 Jun 18 13:17 unpert_obs
> +drwxr-xr-x 3 users 4096 Jun 18 13:17 working
> +The contents of some of the more useful diagnostic files are as follows:
> +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 "NL_CALCULATE_CG_COST_FN=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 "NL_CALCULATE_CG_COST_FN=true".
> +Note: Make sure that you remove the first two records (header) in cost_fn and grad_fn. Also you need to specify the directory name for these two files.
> +gts_omb_oma: This file holds (in ASCII format) information about each type of observation, !
> such as value, quality, observation error, observation minus b!
> ackgroun
> d (OMB) and observation minus analysis (OMA). This information is very useful for analysis or forecasts verification purposes.
> +namelist.input: This is the WRF-Var namelist input file. It displays all the non-default options that have been defined by the user. If any of namelist-defined options did not appear in this file, you may like to check the variable name and verify that it matches a namelist entry in WRFDA/Registry/Registry.wrfvar.
> +namelist.output: This file contains a consolidated list of all the namelist options used.
> +rsl: A directory containing information on standard WRF-Var output from individual processors, in runs where multiple processors were used. It contains a wealth of information on the 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 for the string "print_" in WRFDA/Regi!
> stry/Registry.wrfvar.
> +statistics: This text file contains OMB (OI), and 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 final analysis file should be located in ${RUN_DIR}/2007010200/wrfvar /working/wrfvar_output, and a second copy should also be found in ${FC_DIR}/2007010200/wrfinput_d01. It is in WRF (NETCDF) format, and may be visualized using the NCL script WRFDA/var/graphcs/ncl/WRF-Var_plot.ncl.
> +You need to specify the analsyis_file name, its full path etc. The details are listed in this!
> script as comments.
> +As an example, if you are aiming to d!
> isplay U
> -component of the analysis at level 18, execute the following command after modifying the script WRFDA/var/graphcs/ncl/WRF-Var_plot.ncl
> + > ncl WRF-Var_plot.ncl
> +If successful, the script should display a figure similar the one below.
>
> -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.
> -Take time to look through the text output files to ensure you understand how WRF-Var has performed. For example,
> +
> +You may like to change the variable name, level, etc., in this script to display the variable of your choice at the desired sigma level.
> +Take time to look through the textual 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/maxi!
> mum 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.
> -How long did WRF-Var take to converge? Does it really converge? You will get the answers of all these questions by looking into rsl-files, as it indicates the number of iterations taken by WRF-Var to converge. If this is the same as the maximum number of iterations specified in the namelist (NTMAX) or its default value (=200) set in WRFDA/Registry/Registry.wrfvar", then it means that the analysis solution did not converge. If so, you may like to increase the value of "NTAMAX" and rerun your case to ensure that the convergence is achieved. On the other hand, a normal WRF-Var run should usually converge within 100 iterations. If it still doesn't converge in 200 iterations, that means there might be some problem in the observations or first guess.
> -A good visual way of seeing the impac!
> t of assimilation of observations is to plot the analysis incr!
> ements (
> i.e. analysis minus first guess difference). There are many different graphics packages used (e.g. RIP4, NCL, GRADS etc) that can do this. The plot of level 18 theta increments below was produced using the particular NCL script. This script is located at
> -"WRFDA/var/graphcs/ncl/WRF-Var_plot.ncl"
> -You need to modify this script to fix the full path for first_guess & analysis files. You may also like to modify the display level by setting "kl" and the name of the variable to display by setting "var". Further details are given in this script.
> -If you are aiming to display increment of potential temperature at level 18, after modifying "WRFDA/var/graphcs/ncl/WRF-Var_plot.ncl" suitably, make sure following pieces of codes are uncommented:
> -var = "T"
> -fg = first_guess->T ;Theta- 300
> -an = analysis->T ;Theta- 300
> -plot_data = an - fg
> -When you execute the following command from "WRFDA/var/graphics/ncl".
> - > ncl WRF-Var_plot.ncl
> -The plot created will!
> looks as follows:
> +How long did WRF-Var take to converge? Does it really converge? You will get the answers of all these questions by looking into rsl-files, as it indicates the number of iterations taken by WRF-Var to converge. If this is the same as the maximum number of iterations specified in the namelist (NTMAX) or its default value (=200) set in WRFDA/Registry/Registry.wrfvar, then it means that the analysis solution did not converge. If so, so you may like to increase the value of "NTAMAX" and re-run your case to ensure that the convergence is achieved.
> +A good visual way of seeing the impact of assimilation of observations is to plot the analysis increments (i.e., analysis minus first guess difference). There are many different graphics packages used (e.g. RIP, NCL, GRADS etc) that can do this. The plot of level 18 theta increments, below, was produced using the particular NCL script. This script is located at
> +WRFDA/var/graphcs/ncl/WRF-Var_plot.ncl
> +You need to m!
> odify this script to fix the full path for first_guess and ana!
> lysis fi
> les. You may also like to modify the display level by setting "kl" and the name of the variable to display by setting "var". Further details are given in this script.
> +If you are aiming to display increment of potential temperature at level 18, after modifying WRFDA/var/graphcs/ncl/WRF-Var_plot.ncl suitably.
> +When you execute the following command from WRFDA/var/graphics/ncl.
> + > ncl WRF-Var_plot.ncl
> +The plot created should look similar to the one below.
>
> -Note: Higher the analysis increments, more is the data impact in that region.
> +Note: Larger analysis increments indicate a larger data impact in the corresponding region of the domain.
>
> Updating WRF lateral 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 latera!
> l 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".
> -Note: Make sure that you have "da_update_bc.exe" in "WRFDA/var/da" 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 (the directory where you ran WRF-Var)
> -cp –p $DAT_DI!
> R/rc/2007010200/wrfbdy_d01 ./wrfbdy_d01 (IMPORTANT: make a cop!
> y of wrf
> bdy_d01 as the wrf_bdy_file will be overwritten by da_update_bc.exe)
> -vi param.in
> -&control_param
> - wrfvar_output_file = './wrfvar_output'
> - wrf_bdy_file = './wrfbdy_d01'
> - wrf_input = '$DAT_DIR/rc/2007010200/wrfinput_d01'
> +Before running NWP forecasts using the 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.
> +This is a simple procedure performed by the WRF utility da_updated_bc.
> +Note: Make sure that you have da_update_bc.exe in the WRFDA/var/da directory. This executable automatically!
> gets created when you compiled WRF-Var system.
> +The da_update_bc.exe program is run (via the same wrapper script used for the con200 case) by adding following line to your wrapper script:
> + export RUN_UPDATE_BC=true
> +By setting this option, the standard script located at WRFDA/var/scripts/da_run_update_bc.ksh will be activated to update the content of the wrfbdy_d01 file. 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
> + > ls –ltr $FC_DIR/2007010200/wrfbdy_d01
>
> - cycling = .false. (set to .true. if WRF-Var first guess comes from a previous WRF forecast.)
> - debug = .true.
> - low_bdy_only = .false.
> - update_lsm = .false.
> -/
> -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.
> -
> Running gen_be
> -The background error statistics file supplied with the tutorial test case can NOT be used for your applications other than the tutorial case. It is necessary to generate your domain-specific background error statistics with the gen_be utility.
> +The gen_be utility is part of the WRF-Var system, and is therefore distributed as part of the WRFDA release. The Fortran code for gen_be can be found in WRFDA/var/gen_be. The scripts to run these codes are in WRFDA/var/scripts/gen_be.
>
> -The Fortran main programs for gen_be can be found in WRFDA/var/gen_be. The executables of gen_be should be created after you have compiled the WRF-Var code (as described earlier). The scripts to run these codes are in WRFDA/var/scripts/gen_be.
> +The input data for gen_be are WRF forecasts, which are used to generate model perturbations, used as a proxy for estimates of foreca!
> st error. As discussed above, for the NMC-method, the model perturbations are differences between forecasts (e.g., T+24 minus T+12 is typical for regional applications, T+48 minus T+24 for global) valid at the same time. Given input from an ensemble prediction system (EPS), the inputs are the ensemble forecasts, and the model perturbations created are the transformed ensemble perturbations.
>
> -The input data for gen_be are WRF forecasts, which are used to generate model perturbations, used as a proxy for estimates of forecast error. For the NMC-method, the model perturbations are differences between forecasts (e.g. T+24 minus T+12 is typical for regional applications, T+48 minus T+24 for global) valid at the same time. Climatological estimates of background error may then be obtained by averaging such forecast differences over a period of time (e.g. one month). Given input from an ensemble prediction system (EPS), the inputs are the ensemble forecasts, and the model pertu!
> rbations created are the transformed ensemble perturbations. T!
> he gen_b
> e code has been designed to work with either forecast difference, or ensemble-based perturbations. The former is illustrated in this tutorial example.
> +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).
>
> -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 unnecessarily 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 minus T+12 forecast differences (the 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 the files are then arranged as follows, the gen_be_wrapper.ksh script can be used without significant modification to calculate the necessary "perturbations".
>
> -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. Then the forecast output files should 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.
> -
> Example directory/files structure for a CON200!
> domain
> (45 x 45 x 28 gridpoints):
>
> --rw-r--r-- 1 3246536 Jun 16 15:07 2007010100/wrfout_d01_2007-01-01_12:00:00
> --rw-r--r-- 1 3246536 Jun 16 15:07 2007010100/wrfout_d01_2007-01-02_00:00:00
> --rw-r--r-- 1 3246536 Jun 16 15:08 2007010112/wrfout_d01_2007-01-02_00:00:00
> --rw-r--r-- 1 3246536 Jun 16 15:08 2007010112/wrfout_d01_2007-01-02_12:00:00
> --rw-r--r-- 1 3246536 Jun 16 15:09 2007010200/wrfout_d01_2007-01-02_12:00:00
> --rw-r--r-- 1 3246536 Jun 16 15:09 2007010200/wrfout_d01_2007-01-03_00:00:00
> --rw-r--r-- 1 3246536 Jun 16 14:42 2007010212/wrfout_d01_2007-01-03_00:00:00
> --rw-r--r-- 1 3246536 Jun 16 14:42 2007010212/wrfout_d01_2007-01-03_12:00:00
> --rw-r--r-- 1 3246536 Jun 16 14:43 2007010300/wrfout_d01_2007-01-03_12:00:00
> --rw-r--r-- 1 3246536 Jun 16 14:43 2007010300/wrfout_d01_2007-01-04_00:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 15:07 2007010100/wrfout_d01_2007-01-01_00:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 15:07 2007010100/wrfout_d01_2007-01-01_12:00:00
> +-rw-r--r-- 1 users 3246!
> 536 Jun 16 15:07 2007010100/wrfout_d01_2007-01-02_00:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 15:08 2007010112/wrfout_d01_2007-01-01_12:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 15:08 2007010112/wrfout_d01_2007-01-02_00:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 15:08 2007010112/wrfout_d01_2007-01-02_12:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 15:09 2007010200/wrfout_d01_2007-01-02_00:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 15:09 2007010200/wrfout_d01_2007-01-02_12:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 15:09 2007010200/wrfout_d01_2007-01-03_00:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 14:42 2007010212/wrfout_d01_2007-01-02_12:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 14:42 2007010212/wrfout_d01_2007-01-03_00:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 14:42 2007010212/wrfout_d01_2007-01-03_12:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 14:43 2007010300/wrfout_d01_2007-01-03_00:00:00
> +-rw-r--r-- 1 users 3246536 Jun 16 14:43 2007010300/wrfout_d01_2007-01-03_12:00:00
> +-rw-r--r-- 1 us!
> ers 3246536 Jun 16 14:43 2007010300/wrfout_d01_2007-01-04_00:0!
> 0:00
>
> -
> In the above example, only 3 days (00Z 01 Jan to 00Z 03 Jan. 2007) of forecasts, every 12 hours are supplied to gen_be_wrapper to estimate forecast error covariance. It is only for demonstration. The minimum number of forecasts required depends on the application, number of grid points, etc. Month-long (or longer) datasets are typical for the NMC-method. Generally, at least 1-month dataset should be used.
> +In the above example, only 3 days (00Z 01 Jan to 00Z 03 Jan. 2007) of forecasts, every 12 hours, are supplied to gen_be_wrapper to estimate forecast error covariance; this is only for demonstration. The minimum number of forecasts required depends on the application, number of grid points, etc. Month-long (or longer) datasets are typical for the NMC-method. Generally, at least 1-month dataset should be used.
>
> -Under WRFDA/var/scripts/gen_be, gen_be_wrapper.ksh is used to generate the BE data, following variables need to be set to fit your case:
> +Under the WRFDA/var/scri!
> pts/gen_be directory, the gen_be_wrapper.ksh is used to generate the BE data, and the following variables need to be set to fit your case:
>
> WRFVAR_DIR=/karri/users/xinzhang/support/WRFDA #WRFDA path
> REGION=con200 #Region ID
> EXPT=expt # Experiment ID
> EXP_DIR=/karri/users/xinzhang/support/$REGION/$EXPT
> START_DATE=2007010200
> -END_DATE=2007010312
> +END_DATE=2007010300
> NUM_LEVELS=28
>
> -Note: The START_DATE and END_DATE are perturbation valid dates. As show in the forecast list above, when you have 24-hour and 12-hour forecasts initialized at 2007010100 through 2007010300, the first and final forecast difference valid dates are 2007010200 and 2007010312 respectively.
> -
> Note: The forecast dataset should be located in $EXP_DIR/fc. Then type:
>
> - > gen_be_wrapper.ksh
> + > gen_be_wrapper.ksh
>
> -Once gen_be_wrapper.ksh runs completed, the be.dat can be found under $EXP_DIR/gen_be directory.
> +Once gen_be_wrapper.ksh completes, the be.dat file can be found !
> under the $EXP_DIR/gen_be directory.
>
> -To get a clear idea ab!
> out what
> are included in be.dat, the script gen_be_plot_wrapper.ksh may be used to plot various data in be.dat such as:
> +To get a clearer idea about what are include in BE, the script gen_be_plot_wrapper.ksh may be used to plot various data in be.dat such as:
> +
> +
> +Running Observation Preprocessor (OBSPROC)
> +The OBSPROC program decodes observations in LITTLE_R format, such as the ouput of the MM5 "gts_decoder" or the "fetch.csh" utilities for inputting into the WRF-Var system. For more information 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 .
> +The basic operations performed by OBSPROC are:
> +1) Remove the observations outside the time range and domain (horizontal and top).
> +2) Re-order and merge the duplicate (time and location) data reports.
> +3) Retrieve the pressure or height based on the observed information wi!
> th the hydrostatic assumption.
> +4) Check the vertical consistency and super adiabatic for multi-level observations.
> +5) Estimate observational error based on the pre-specified error file.
> +6) Write out at the WRF-Var input format.
> +7) Plot the distribution for each type of observations.
>
> -
> +The WRF-Var observation preprocessor may be found in the WRFDA/var/obsproc directory
> + > cd WRFDA/var/obsproc
> + > make
> +Once this is complete (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 README.namelist for details);
> +For your reference in "var/obsproc" directory, a file named "namelist_3dvar_obs.wrfvar-tut" has already been created. Thus, proceed as follows:
> + > cp namelist.3dvar_obs.wrfvar-tut namelist.3dvar_obs
> +edit namelist.3dvar_obs
> +In this namelist file, all you need is to change the full path and name of t!
> he observation file (ob.little_r) depending upon where this fi!
> le is do
> wnloaded 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 file, obs_gts.3dvar, in the obsproc directory. This is the input observation file to WRF-Var. Before running WRF-Var, you may like to learn more about various types of data you are aiming to assimilate for this case, for example, their geographical distribution, etc. This file is in ASCII format and so you can easily view it. To graphically view the contents of this file, there is a "MAP_plot" utility to look at the data distribution for each type of observations. To run MAP_plot, 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.3dvar). Precisely, the following string in this script as follows.
> + TIME_WINDOW_MIN = '2007010121'
> + TIME_ANALYSIS = '2007010200'
> + TIME_WINDOW_MAX = '2007010!
> 203'
> + OBSDATA = ../obs_gts.3dvar
> +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.3dvar. To view this, type
> + > idt gmeta.2007010200
> +It will display (panel by panel) geographical distribution of various types of data that are listed in the header of "obs_gts.3dvar". The geographical distribution of "sonde" observations for this test case are shown in the figure below.
> +
> +
> +After successfully creating your own observation file (obs_gts.3dvar), copy it to $DAT_DIR using the command (issued from the obsproc directory)
> + > mv obs_gts.3dvar $DAT_DIR/ob/2007010200/ob.ascii
> +
> Additional WRF-Var Exercises:
> (a) Single Observation response in WRF-Var:
> -Single observation test is done in WRF-Var by setting num_pseudo=1 along with other pre-speci!
> fied values in record &wrfvar15 and &wrfvar19 of namel!
> ist.inpu
> t,
> -With the settings shown below, WRF-Var generates a single observation with pre-specified innovation Observation – First Guess) value at desired location e.g at (in terms of grid coordinate) 23x23, level 14 for "U" observation with error characteristics 1 m/s, innovation size = 1.0 m/s.
> -&wrfvar15
> -num_pseudo = 1,
> -pseudo_x = 23.0
> -pseudo_y = 23.0
> -pseudo_z = 14.0
> -pseudo_err = 1.0
> -pseudo_val = 1.0
> -/
> -&wrfvar19
> -pseudo_var = 'u' (Note: pseudo_var can be u, v, t, p, q. If pseudo_var is q, then the reasonable values of pseudo_err and pseudo_val are 0.001)
> -/
> -Note: You may like to repeat this exercise for other observations like temperature ("t"), pressure "p", specific humidity "q" etc.
> +In WRF-Var, when you activate the namelist option "pseudo=1" by defining
> +"export NL_NUM_PSEUDO=1"
> +WRF-Var generates a single observation with a pre-specified innovation (Observation – First Guess) value at a specified location, e.g., at (in terms of grid co-ordinate) 23x23, !
> level 14 for "U" observation with error characteristics 1 m/s, innovation size = 1.0 m/s, include the following options in your da_run_suite_wrapper_con200.ksh script and run it. A shot-cut is export SINGLE_OBS=true.
> +export NL_NUM_PSEUDO=1
> +export NL_PSEUDO_VAR="u" #Can be "u v t p q"
> +export NL_PSEUDO_X=23.0
> +export NL_PSEUDO_Y=23.0
> +export NL_PSEUDO_Z=14.0
> +export NL_PSEUDO_ERR=1.0 #Should be "1.0 1.0 1.0 1.0 0.001"
> +export NL_PSEUDO_VAL=1.0 #Should be "1.0 1.0 1.0 1.0 0.001"
> +Also set " export runplot_psot=1".
> +Note: You may also like to change your "RUN_DIR" to generate output in separate directory. You may also notice that in this sample wrapper script for con200, all these parameters are already set but they are commented. So you need to just remove the undesired comments.
> +After you have run this new wrapper script successfully, look at various diagnostics files to understand the response of one single "U" obs!
> ervation almost at the middle of the domain. You can display t!
> he analy
> sis increments as you did previously or run the same wrapper script by setting:
> + "export runplot_psot=2"
> +It will activate some standard NCL script residing in "WRFDA/var/graphics/ncl" and generate following three files in your new $RUN_DIR/plotpsot directory.
> +xy_psot1.pdf --- XY cross-section
> +xz_psot1.pdf --- XZ cross-section
> +yz_psot1.pdf --- YZ cross-section
> +
> +Note: You may like to repeat this exercise for other observations like temperature ("t"), pressure "ps", specific humidity, etc.
> (b) Response of BE length scaling parameter:
> -Run single observation test with following additional parameters in record &wrfvar7 of namelist.input
> -&wrfvar7
> -len_scaling1 = 0.5, # reduce psi length scale by 50%
> -len_scaling2 = 0.5, # reduce chi_u length scale by 50%
> -len_scaling3 = 0.5, # reduce T length scale by 50%
> -len_scaling4 = 0.5, # reduce q length scale by 50%
> -len_scaling5 = 0.5, # reduce Ps length scale by 50%
> -/
> +Run single observation test !
> with following additional parameters
> +export NL_LEN_SCALING1=0.5 # reduce length psi-scale by 50%
> +export NL_LEN_SCALING2=0.5 # reduce length chi_u-scale by 50%
> +export NL_LEN_SCALING3=0.5 # reduce length T-scale by 50%
> +export NL_LEN_SCALING4=0.5 # reduce length Q-scale by 50%
> +export NL_LEN_SCALING5=0.5 # reduce length ps-scale by 50%
> Note: You may like to try the response of individual variable by setting one parameter at one time. See the spread of analysis increment.
> (c) Response of changing BE variance:
> -Run single observation test with following additional parameters in record &wrfvar7 of namelist.input
> -&wrfvar7
> -var_scaling1 = 0.25, # reduce psi variance by 75%
> -var_scaling2 = 0.25, # reduce chi_u variance by 75%
> -var_scaling3 = 0.25, # reduce T variance by 75%
> -var_scaling4 = 0.25, # reduce q variance by 75%
> -var_scaling5 = 0.25, # reduce Ps variance by 75%
> -/
> +Run single observation test with following additional parameter!
> s
> +export NL_VAR_SCALING1=0.25 # reduce psi-variance by 75%!
>
> +expor
> t NL_VAR_SCALING2=0.25 # reduce chi_u-variance by 75%
> +export NL_VAR_SCALING3=0.25 # reduce T-variance by 75%
> +export NL_VAR_SCALING4=0.25 # reduce Q-variance by 75%
> +export NL_VAR_SCALING5=0.25 # reduce ps-variance by 75%
> Note: You may like to try the response of individual variable by setting one parameter at one time. See the magnitude of analysis increments.
> (d) Response of convergence criteria:
> Run con200 case with
> -&wrfvar6
> -eps = 0.0001
> -
> -/
> + export NL_EPS=0.0001
> + See rsl.out.0000.html and if the solution did not converge in 200 iterations which is the default value for minimization inner iterations loop, increase its limit by setting
> + export NL_NTMAX=1000
> You may like to compare various diagnostics with earlier run.
> (e) Response of outer loop on minimization:
> Run con200 case with
> -&wrfvar6
> -max_ext_its = 2
> -/
> + export NL_MAX_EXT_ITS=2
> With this setting "outer loop" for the minimization procedure will get act!
> ivated. You may like to compare various diagnostics with earlier run.
> Note: Maximum permissible value for "MAX_EXT_ITS" is 10
> -(f) Response of suppressing particular types of data in WRF-Var:
> -The types of observations that WRF-Var gets to use actually depend on what is included in the observation file and the WRF-Var namelist settings. For example, if you have SYNOP data in the observation file, you can suppress its usage in WRF-Var by setting use_synopobs=false in record &wrfvar4 of namelist.input. It is OK if there is no SYNOP data in the observation file and use_synopobs=true.
> -Turning on and off of certain types of observations are widely used for assessing impact of observations on data assimilations.
> -Note: It is important to go through the default "use_*" settings in record &wrfvar4 in "WRFDA/Registry/Registry.wrfvar" to know what observations are activated in default.
> +(f) Response of suppressing a particular type of data in WRF-Var:
> +Suppose if someone w!
> ants not to include "SYNOP" type of data. One way is that do n!
> ot proce
> ss it via "obsproc" by not including it in "little_r". However, it can be suppressed in WRF-Var through namelist option by setting
> + "export NL_USE_SYNOPOBS=false"
> +Note: grep "use_" string in "WRFDA/Registry.wrfvar" to learn about all types of data used in WRF-Var.
>
> Description of Namelist Variables
> -WRF-Var namelist variables.
> +The following is a description of WRF-Var namelist variables.
>
>
> -Variable Names Default Value Description &wrfvar1 write_increments false .TRUE.: indicates to write out the analysis increment file, which is useful for plotting the increments fields, especially for the SINGLE-OBS test.
> - .FALSE.: no increment file:'analysis_increments' written out. wrfvar_mem_model 0 Not used var4d 0 0: 3D-Var mode; 1: 4D-Var mode multi_inc 0 0: normal run; 1: multi-incremental run var4d_coupling 2 Not used global false Not used print_detail_airep false print_detail_radar false print_detail_rad false print_detail_xa false print_detai!
> l_xb false print_detail_obs false print_detail_f_obs false print_detail_grad false print_detail_regression false print_detail_spectral false print_detail_testing false print_detail_parallel false print_detail_be false print_detail_timing false check_max_iv_print true &wrfvar2 analysis_accu 900 Specify the accuracy of the time difference in seconds between the analysis time and the first guess time. calc_w_increment false .TRUE.: the increment of the vertical velocity W will be diagnosed based on the increments of other fields. If there is information of the W from observations assimilated, such as the Radar radial velocity, the W increments ar always computed, no matter CALC_W_INCREMENTS=.TRUE. or .FALSE.
> +Variable Names Default Value Description &wrfvar1
> + write_increments false .TRUE.: causes analysis increment to be written to a file, which is useful for plotting the increments fields, especially for the SINGLE-OBS test.
> + .FALSE.: no!
> analysis_increments file will be written out. wrfvar_mem_mo!
> del 0 No
> t used var4d 0 0: 3D-Var mode; 1: 4D-Var mode multi_inc 0 0: normal run; 1: multi-incremental run var4d_coupling 2 Not used global false Not used print_detail_airep false print_detail_radar false print_detail_rad false print_detail_xa false print_detail_xb false print_detail_obs false print_detail_f_obs false print_detail_grad false print_detail_regression false print_detail_spectral false print_detail_testing false print_detail_parallel false print_detail_be false print_detail_timing false check_max_iv_print true &wrfvar2 analysis_accu 900 Specify the accuracy of the time difference, in seconds, between the analysis time and the first guess time. calc_w_increment false .TRUE.: the increment of the vertical velocity W will be diagnosed based on the increments of other fields. If there is information of the W from observations assimilated, such as the Radar radial velocity, the W increments are always computed, no matter CALC_W_INCRE!
> MENTS=.TRUE. or .FALSE.
> .FALSE.: the increment of the vertical velocity W is zero if no W information assimilated.
> - dt_cloud_model false write_qcw false write_qrn false write_qci false write_qsn false write_qgr false write_filtered_obs false &wrfvar3 fg_format 1 Indicates the first guess format: 1 = WRF; ( 2 = MM5; 3 = KMA, not tested) ob_format 2 Indicates the observation file format: 1 = BURF; 2 = ASCII num_fgat_time 1 1 = 3DVar, >1 apply to FGAT and 4DVar &wrfvar4 use_synopobs true .TRUE.: assimilate the SYNOP data if any available.
> -.FALSE.: not assimilate the SYNOP data even if available from OBS file. use_shipsobs true .TRUE.: assimilate the SHIPS data if any available.
> -.FALSE.: not assimilate the SHIPS data even if available from OBS file. use_metarobs true .TRUE.: assimilate the METAR data if any available.
> -.FALSE.: not assimilate the METAR data even if available from OBS file. use_soundobs true .TRUE.: assimilate the SOUND!
> data if any available.
> -.FALSE.: not assimilate the SOUND dat!
> a even i
> f available from OBS file. use_mtgirsobs true .TRUE.: assimilate the MTGIRS data if any available.
> -.FALSE.: not assimilate the MTGIRS data even if available from OBS file. use_pilotobs true .TRUE.: assimilate the PILOT data if any available.
> -.FALSE.: not assimilate the PILOT data even if available from OBS file. use_airepobs true .TRUE.: assimilate the AIREP data if any available.
> -.FALSE.: not assimilate the AIREP data even if available from OBS file. use_geoamvobs true .TRUE.: assimilate the GEOAMV data if any available.
> -.FALSE.: not assimilate the GEOAMV data even if available from OBS file. use_polaramvobs true .TRUE.: assimilate the POLARAMV data if any available.
> -.FALSE.: not assimilate the POLARAMV data even if available from OBS file. use_bogusobs true .TRUE.: assimilate the BOGUS data if any available.
> -.FALSE.: not assimilate the BOGUS data even if available from OBS file. use_buoyobs true .TRUE.: assimilate the BUOY data if any available.
> -.FALSE!
> .: not assimilate the BUOY data even if available from OBS file. use_profilerobs true .TRUE.: assimilate the PROFILER data if any available.
> -.FALSE.: not assimilate the PROFILER data even if available from OBS file. use_satemobs true .TRUE.: assimilate the SATEM data if any available.
> -.FALSE.: not assimilate the SATEM data even if available from OBS file.
> -** Currently only the retrieved SATEM thickness data can be assimilated use_gpsztdobs false .TRUE.: assimilate the GPSZTD data if any available.
> -.FALSE.: not assimilate the GPSZTD data even if available from OBS file. use_gpspwobs true .TRUE.: assimilate the GPSPW data if any available.
> -.FALSE.: not assimilate the GPSPW data even if available from OBS file. use_gpsrefobs true .TRUE.: assimilate the GPSREF data if any available.
> -.FALSE.: not assimilate the GPSREF data even if available from OBS file. use_ssmiretrievalobs false .TRUE.: assimilate the SSMI retrieval data (PW and surface wind speed) if any av!
> ailable.
> + dt_cloud_model false write_qcw false write_qrn!
> false
> write_qci false write_qsn false write_qgr false write_filtered_obs false &wrfvar3 fg_format 1 Indicates the first guess format: 1 = WRF; ( 2 = MM5; 3 = KMA, not tested) ob_format 2 Indicates the observation file format: 1 = BURF; 2 = ASCII num_fgat_time 1 1 = 3DVar, >1 apply FGAT and 4DVar &wrfvar4 use_synopobs true .TRUE.: assimilate any available SYNOP data.
> +.FALSE.: do not assimilate the SYNOP data, even if provided in the OBS file. use_shipsobs true .TRUE.: assimilate any available SHIPS data.
> +.FALSE.: do not assimilate SHIPS data, even if provided in the OBS file. use_metarobs true .TRUE.: assimilate any available METAR data.
> +.FALSE.: do not assimilate METAR data, even if provided in the OBS file. use_soundobs true .TRUE.: assimilate any available SOUND data.
> +.FALSE.: do not assimilate SOUND data, even if provided in the OBS file. use_mtgirsobs true .TRUE.: assimilate any available MTGIRS data.
> +.FALSE.: do not assimilate MTGIRS da!
> ta, even if provided in the OBS file. use_pilotobs true .TRUE.: assimilate any available PILOT data.
> +.FALSE.: do not assimilate PILOT data, even if provided in the OBS file. use_airepobs true .TRUE.: assimilate any available AIREP data.
> +.FALSE.: do not assimilate AIREP data, even if provided in the OBS file. use_geoamvobs true .TRUE.: assimilate any available GEOAMV data.
> +.FALSE.: do not assimilate GEOAMV data, even if provided in the OBS file. use_polaramvobs true .TRUE.: assimilate any available POLARAMV data.
> +.FALSE.: do not assimilate POLARAMV data, even if provided in the OBS file. use_bogusobs true .TRUE.: assimilate any available BOGUS data.
> +.FALSE.: do not assimilate BOGUS data, even if provided in the OBS file. use_buoyobs true .TRUE.: assimilate any available BUOY data.
> +.FALSE.: do not assimilate BUOY data, even if provided in the OBS file. use_profilerobs true .TRUE.: assimilate any available PROFILER data.
> +.FALSE.: do not assimilate PROFILER!
> data, even if provided in the OBS file. use_satemobs true .T!
> RUE.: a
> ssimilate any available SATEM data.
> +.FALSE.: do not assimilate SATEM data, even if provided in the OBS file.
> +** Currently only the retrieved SATEM thickness data can be assimilated use_gpsztdobs false .TRUE.: assimilate any available GPSZTD data.
> +.FALSE.: do not assimilate GPSZTD data, even if provided in the OBS file. use_gpspwobs true .TRUE.: assimilate any available GPSPW data.
> +.FALSE.: do not assimilate GPSPW data, even if provided in the OBS file. use_gpsrefobs true .TRUE.: assimilate any available GPSREF data.
> +.FALSE.: do not assimilate GPSREF data, even if provided in the OBS file. use_ssmiretrievalobs false .TRUE.: assimilate the SSMI retrieval data (PW and surface wind speed) if any available.
> .FALSE.: not assimilate the SSMI retrieval data (PW and surface wind
> -speed) even if available from OBS file. use_ssmitbobs false .TRUE.: assimilate the SSMI Brightness temperature data if any available.
> -.FALSE.: not assimilate the SSMI Brightness temperature !
> data even if available from OBS file.
> - use_ssmt1obs false .TRUE.: assimilate the SSMT1 (temperature) data if any available.
> -.FALSE.: not assimilate the SSMT1 (temperature) data even if available
> -from OBS file. use_ssmt2obs false .TRUE.: assimilate the SSMT2 (relative humidity) data if any available.
> -.FALSE.: not assimilate the SSMT2 (relative humidity) data even if available from OBS file.
> - use_qscatobs true .TRUE.: assimilate the Quik SCAT (SeaWinds) data if any available.
> -.FALSE.: not assimilate the Quik SCAT (SeaWinds) data even if available
> +speed) even if available from OBS file. use_ssmitbobs false .TRUE.: assimilate any available SSMI Brightness temperature data.
> +.FALSE.: do not assimilate SSMI Brightness temperature data, even if provided in the OBS file. use_ssmt1obs false .TRUE.: assimilate any available SSMT1 (temperature) data.
> +.FALSE.: do not assimilate SSMT1 (temperature) data, even if provided in the OBS file. use_ssmt2obs false .TRUE.: as!
> similate any available SSMT2 (relative humidity) data.
> +.FALSE!
> .: do no
> t assimilate SSMT2 (relative humidity) data, even if provided in the OBS file. use_qscatobs true .TRUE.: assimilate any available Quik SCAT (SeaWinds) data.
> +.FALSE.: do not assimilate Quik SCAT (SeaWinds) data, even if provided in the OBS file.
> ** Note at this moment, assimilation of only the SeaWinds Level 2B data from JPL.
> - use_radarobs false .TRUE.: assimilate the RADAR data if any available.
> -.FALSE.: not assimilate the RADAR data even if available from OBS file.
> - use_radar_rv false use_hirs2obs fasle use_hirs3obs false use_hirs4obs false use_mhsobs false use_msuobs false use_amsuaobs false use_amsubobs false use_airsobs false use_airsretobs true use_eos_amsuaobs false use_eos_radobs false use_hsbobs false use_ssmisobs false use_kma1dvar false use_filtered_rad false use_obs_errfac false .TRUE.: the OBS error tuning factors need to be applied.
> -.FALSE.: no the OBS error tuning factors need to be applied. At this moment, always s!
> et use_obs_errfac =.FALSE., not change.
> + use_radarobs false .TRUE.: assimilate any available RADAR data.
> +.FALSE.: do not assimilate RADAR data, even if provided in the OBS file. use_radar_rv false use_hirs2obs fasle use_hirs3obs false use_hirs4obs false use_mhsobs false use_msuobs false use_amsuaobs false use_amsubobs false use_airsobs false use_airsretobs true use_eos_amsuaobs false use_eos_radobs false use_hsbobs false use_ssmisobs false use_kma1dvar false use_filtered_rad false use_obs_errfac false .TRUE.: apply OBS error tuning factors.
> +.FALSE.: do not apply the OBS error tuning factors.
> +** Currently, always set use_obs_errfac =.FALSE.
> &wrfvar5
> - check_max_iv true .TRUE.: Go through the Maximum OBS error check based on the innovations (O-B). For safety, in general, it should set check_max_iv = .TRUE.
> -.FALSE.: no Maximum OBS error check. Only when you sure that all of the observation data have the good quality, such a!
> s in the SINGLE-OBS tests, you can set check_max_iv = .FALSE.
> !
> - put_r
> and_seed false set put_rand_seed = .FALSE., not change omb_set_rand false set omb_set_rand = .FALSE., not change omb_add_noise false set omb_add_noise = .FALSE., not change. position_lev_dependant false obs_qc_pointer 0 Indicates the quality flag (qc) criterion, integer number, default is 0:
> + check_max_iv true .TRUE.: Go through the Maximum OBS error check based on the innovations (O-B). For safety, in general, it should set to .TRUE.
> +.FALSE.: no Maximum OBS error check. Set to .FALSE. only when you sure that all of the observation data are of good quality, such as in the SINGLE-OBS tests, you can set check_max_iv = .FALSE.
> + put_rand_seed false set put_rand_seed = .FALSE., do not change omb_set_rand false set omb_set_rand = .FALSE., do not change omb_add_noise false set omb_add_noise = .FALSE., do not change. position_lev_dependant false obs_qc_pointer 0 Indicates the quality flag (qc) criterion, integer number, default is 0:
> the data with qc >= obs_qc!
> _pointer are assimilated.
> -the data with qc < obs_qc_pointer are discarded. max_sound_input 5000 max_mtgirs_input 50000 max_synop_input 50000 max_geoamv_input 300000 max_polaramv_input 300000 max_airep_input 200000 max_satem_input 50000 max_pilot_input 30000 max_radar_input 10000 max_metar_input 30000 max_gpspw_input 4000 max_ships_input 20000 max_profiler_input 30000 max_bogus_input 5000 max_buoy_input 30000 max_ssmi_rv_input 30000 max_ssmi_tb_input 30000 max_ssmt1_input 30000 max_ssmt2_input 30000 max_qscat_input 50000 max_gpsref_input 800000 max_airsr_input 100000 max_tovs_input 10000000 max_ssmis_input 10000000 report_start 1 report_end 10000000 tovs_start 1 tovs_end 10000000 &wrfvar6 max_ext_its 1 Used to assign the number of the outer loops. For example, 1 = a single outer loop, 3 = 3 outer loops, etc., now the maximum
> -number of outer loops is allowed to be 10. ntmax 200 The maximum number of iteratio!
> ns of the minimization in internal loop nsave 4 Not used wri!
> te_inter
> val 5 Not used eps
> +the data with qc < obs_qc_pointer are discarded. max_sound_input 5000 max_mtgirs_input 50000 max_synop_input 50000 max_geoamv_input 300000 max_polaramv_input 300000 max_airep_input 200000 max_satem_input 50000 max_pilot_input 30000 max_radar_input 10000 max_metar_input 30000 max_gpspw_input 4000 max_ships_input 20000 max_profiler_input 30000 max_bogus_input 5000 max_buoy_input 30000 max_ssmi_rv_input 30000 max_ssmi_tb_input 30000 max_ssmt1_input 30000 max_ssmt2_input 30000 max_qscat_input 50000 max_gpsref_input 800000 max_airsr_input 100000 max_tovs_input 10000000 max_ssmis_input 10000000 report_start 1 report_end 10000000 tovs_start 1 tovs_end 10000000 &wrfvar6 max_ext_its 1 Used to assign the number of the outer loops. For example, 1 = a single outer loop, 3 = 3 outer loops, etc.,
> +Currently, the maximum
> +number of outer loops is 10. ntmax 200 The maximum number of iterations of the mi!
> nimization in internal loop nsave 4 Not used write_interval 5 Not used eps
> 0.01 (max_ext_its) Used to assign the minimization convergence criterion for the internal loop
> -within each of the outer loops. precondition_cg false precondition_factor 1.0 &wrfvar7 rf_passes 6 Used to assign the number of passes of recursive filter. var_scaling1 1.0 The background error variance tuning factor for control variable 1 --- stream function PSI. var_scaling2 1.0 The background error variance tuning factor for control variable 2 --- potential velocity CHI. var_scaling3 1.0 The background error variance tuning factor for control variable 3 --- unbalanced pressure Pu. var_scaling4 1.0 The background error variance tuning factor for control variable 4 --- specific humidity q or relative humidity RH. var_scaling5 1.0 Not used currently len_scaling1 1.0 The scale-length (used in the recursive filter) tuning factor for control variable 1 --- Stream function PSI. len_scalin!
> g2 1.0 The scale-length (used in the recursive filter) tuning !
> factor f
> or control variable 2 --- potential velocity CHI. len_scaling3 1.0 The scale-length (used in the recursive filter) tuning factor for control variable 3 --- unbalanced pressure Pu. len_scaling4 1.0 The scale-length (used in the recursive filter) tuning factor for control variable 4 --- specific humidity q or relative humidity RH. len_scaling5 1.0 Not used currently jb_factor 1.0 je_factor 1.0 power_truncation 1.0 &wrfvar8 def_sub_domain false x_start_sub_domain 1.0 y_start_sub_domain 1.0 x_end_sub_domain 1.0e10 y_end_sub_domain 1.0e10 &wrfvar9 stdout 6 stderr 0 trace_unit 7 trace_pe 0 trace_repeat_head 10 trace_repeat_body 10 trace_max_depth 30 trace_use true trace_use_frequent false trace_use_dull false trace_memory true trace_all_pes false trace_csv true use_html true warnings_are_fatal false &wrfvar10 test_transforms false TRUE.: Do the VToX transform correctness check. Here V represents the control variab!
> les, X represents the analyzed variables. VToX means the transform formulas and their adjoint. When you change the V or X, you must do the VToX check first to guarantee the correctness. Program stopped after check finished.
> -.FALSE. Not do adjoint check, but do the data assimilation. test_statistics false interpolate_stats true Not used test_dm_exact false &wrfvar11 cv_options_hum 1 1 --> Use the specific humidity q as the control variable.
> +within each of the outer loops. precondition_cg false precondition_factor 1.0 &wrfvar7 rf_passes 6 Used to assign the number of passes of recursive filter. var_scaling1 1.0 The background error variance tuning factor for control variable 1 --- stream function PSI. var_scaling2 1.0 The background error variance tuning factor for control variable 2 --- potential velocity CHI. var_scaling3 1.0 The background error variance tuning factor for control variable 3 --- unbalanced pressure Pu. var_scaling4 1.0 The ba!
> ckground error variance tuning factor for control variable 4 -!
> -- speci
> fic humidity q or relative humidity RH. var_scaling5 1.0 Not used currently len_scaling1 1.0 The scale-length (used in the recursive filter) tuning factor for control variable 1 --- Stream function PSI. len_scaling2 1.0 The scale-length (used in the recursive filter) tuning factor for control variable 2 --- potential velocity CHI. len_scaling3 1.0 The scale-length (used in the recursive filter) tuning factor for control variable 3 --- unbalanced pressure Pu. len_scaling4 1.0 The scale-length (used in the recursive filter) tuning factor for control variable 4 --- specific humidity q or relative humidity RH. len_scaling5 1.0 Not used currently jb_factor 1.0 je_factor 1.0 power_truncation 1.0 &wrfvar8 def_sub_domain false x_start_sub_domain 1.0 y_start_sub_domain 1.0 x_end_sub_domain 1.0e10 y_end_sub_domain 1.0e10 &wrfvar9 stdout 6 stderr 0 trace_unit 7 trace_pe 0 trace_repeat_head 10 trace_repeat_body 10 trace_max_depth 30 trace!
> _use true trace_use_frequent false trace_use_dull false trace_memory true trace_all_pes false trace_csv true use_html true warnings_are_fatal false &wrfvar10 test_transforms false .TRUE.: Do the VToX transform correctness check. Here V represents the control variables, X represents the analyzed variables. VToX means the transform formulas and their adjoint. When you change the V or X, you must do the VToX check first to guarantee the correctness. Program stopped after check finished.
> +.FALSE. Do not do adjoint check, but do the data assimilation. test_statistics false interpolate_stats true Not used test_dm_exact false &wrfvar11 cv_options_hum 1 1 --> Use the specific humidity q as the control variable.
> 2 --> Use the relative humidity RH as the control variable. check_rh 2 0 --> No supersaturation check after minimization.
> -1 --> With the supersaturation (rh>100%) and minimum rh (rh<10%) check, and make the local adjust!
> ment of thespecific humidity.
> +1 --> With the supersaturati!
> on (rh&g
> t;100%) and minimum rh (rh<10%) check, and make the local adjustment of the specific humidity.
> 2 --> With the maximum (rh>95%) and minimum (rh<11%) rh check, and make the multi-level q adjustment under the constraints of integrated water vapor in column conserved. set_omb_rand_fac 1.0 Scaling factor for random O-B (*sigma_o). Not change. seed_array1 0 The first element of the seed for subroutine random_seed. Not change. seed_array2 0 The second element of the seed for subroutine random_seed. Not change. sfc_assi_options 1 1 --> Before the minimization, the surface observed parameters (wind, temperature, moisture and pressure) are reduced to the lowest model level. This means that the original observations are modified based on the information of the first guess fields. The observations are discarded when the elevations of the observing sites are too far from the lowest model level height (> 100m).
> 2 --> Based on the surface similarity theory in PB!
> L, some of the observation operators (Hx) are developed to get the analysis equivalent of the surface observed parameters, then the innovations are computed.
> The original values of the surface observation are never changed. Regardless of the elevations of the observing sites, the analysis 10-m wind and 2-m temperature, moisture are computed. Only the analysis pressure computation need to consider the station heights. calculate_cg_cost_fn false .TRUE.: Compute the cost functions every iteration and output.
> @@ -708,26 +440,18 @@
> 1=SQRT(pressure),
> 2=pressure vert_evalue 1 1 --> use the global eigenvector/eigenvalue. Now program hardwired vert_evalue = 1, other values will stop the job. Not change it.
> 2 --> use the I-dependent eigenvector/eigenvalue.
> -Note: Although the I-dependent (approximately latitude-dependent) eigenvector and eigenvalue are available in BE file, the GLOBAL eigenvector/eigenvalue gave smoother analysis results. max_vert_var1 99.0 Specify the maximum truncation value (percentage) to explain the variance of the control variable 1 -- Stream function, in eigenvector decomposition max_vert_var2 99.0 Specify the maximum truncation value (percentage) to explain the variance of the control variable 2 -- Potential velocity, in eigenvector decomposition max_vert_var3 99.0 Specify the maximum truncation value (percentage) to explain the variance of the control variable 3 -- Unbalanced part of pressure, in eigenvector decomposition max_vert_var4 99.0 Specify the maximum trunca!
> tion value (percentage) to explain the variance of the control variable 4 -- Specify humidity or relative humidity, in eigenvector decomposition max_vert_var5 99.0 Not used &wrfvar14 rtminit_print 1 rtminit_nsensor 1 rtminit_platform -1 (max_instruments) rtminit_satid -1.0 (max_instruments) rtminit_sensor -1.0 (max_instruments) rad_monitoring 0 (max_instruments) thinning_mesh 60.0 (max_instruments) thinning_mesh false read_biascoef true biascorr false biasprep false write_profile false write_jacobian false qc_rad true write_iv_rad_ascii false write_oa_rad_ascii false write_filtered_rad false use_error_factor_rad false use_landem false mw_emis_sea 1 tovs_min_transfer 10 tovs_batch false rtm_option 1 use_crtm_kmatrix false use_crtm_kmatrix_fast false crtm_cloud false only_sea_rad false use_simulated_rad false use_pseudo_rad false pseudo_rad_platid 1 pseudo_rad_satid 16 pseudo_rad_senid 3 pseudo_rad_ichan !
> 6 pseudo_rad_lat 35.0 pseudo_rad_lon 130.0 pseudo_rad_tb!
> 258.0
> pseudo_rad_err 1.0 spccoeff_file CRTM_SpcCoeff.bin taucoeff_file CRTM_TauCoeff.bin aerosolcoeff_file CRTM_AerosolCoeff.bin cloudcoeff_file CRTM_CldCoeff.bin emiscoeff_file CRTM_EmisCoeff.bin use_varbc false freeze_varbc false varbc_factor 1.0 use_airs_mmr false airs_warmest_fov false crtm_atmosphere 0 &wrfvar15 num_pseudo 0 Set the number of pseudo observations. Currently only the value of 1 is allowed, i.e. num_pseudo = 1 --- the SINGLE-OBS test pseudo_x 1.0 Set the x-position (J) of the OBS in unit of grid-point. pseudo_y 1.0 Set the y-position (I) of the OBS in unit of grid-point. pseudo_
>
> ...
>
> [Message clipped]
> _______________________________________________
> Mmmdoc-developers mailing list
> Mmmdoc-developers at mailman.ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/mmmdoc-developers
>
>
--
Xiang-Yu Huang
National Center for Atmospheric Research
Mesoscale and Microscale Meteorology Division
P.O. Box 3000, Boulder, CO 80307-3000, USA
Phone: 1-303-497-8975 Fax: 1-303-497-8171
huangx at ucar.edu http://www.mmm.ucar.edu/people/huang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/mmmdoc-developers/attachments/20080701/e26ce210/attachment-0001.html
More information about the Mmmdoc-developers
mailing list