Known Problems in Version 3.0.1 (Details)
Known Problems in Version 3.0.1.1 (Details, updated 2/15/09)
Observation Nudging for Nests (posted 4/27/09)
Problem: The user specified horizontal radius of influence for nests (obs_rinxy) is not applied correctly. This applies to all versions since WRFV2.2. The code incorrectly divides the user-input value obs_rinxy by the ratio of the nest gridsize to coarse-mesh gridsize.
Solution: The following patch applied to file phys/module_fddaobs_rtfdda.F fixes the problem: Change this line:
schnes=1/float(3**(inest-1))
to
schnes=1.0
KF scheme issue (Posted 4/10/09)
Problem: An error was introduced to V3.0 (also in V3.0.1 and V3.0.1.1) KF schemes (cu_physics=1 and cu_physics=99). The error may cause long lasting cloud in rare areas.
Solution: The fix is to replace line line 2189 (NCA(I,J) = TADVEC) with
NCA(I,J) = REAL(NIC)*DT in phys/module_cu_kfeta.F, and replace liine 1925 with the same change in module_cu_kf.F.
Nest Ratio 1:2 Problem (Posted 4/9/09)
Problem: Nest ratio 1:2 is not working correctly in current release.
Solution: Working on a solution. In the mean time, use another nest ratio.
Bug In Lin Microphysics Scheme (posted 10/16/08)
Problem: A bug was introduced to the Lin microphysics scheme (mp_physics=2) in V3.0 code. It can cause over-prediction of cloud ice and graupel. It may also cause over-prediction of surface rainfall. This bug has been fixed in V3.0.1 code.
Solution: Download the modified module_mp_lin.F file to directory phys/ if you are still using V3.0 code. Rename and recompile.
Occasional Spurious High PBL Height In MYJ Scheme (posted 8/1/08)
Problem: MYJ PBL scheme occasionally produces unrealistically high PBL and high TKE in sporadic columns. This is reported by PSU researchers.
Solution: Download the modified module_bl_myjpbl.F (from PSU). The scheme computes the PBL depth by using the TKE profile criteria from Penn State, instead of the current MYJ method that searches for the first level of background TKE. This fix reduces the PBL height in general.
Using Gridded nudging and IO Quilting Together (posted 7/28/08, Fixed in V3.0.1)
Problem: There is an error to correctly read gridded fdda data when gridded nudging (grid_fdda = 1) and io quilting (nio_tasks_per_group > 0 and nio_group >= 1) are used together.
Solution: Download the modified module_io.F.fix into frame/ directory, rename the file to module_io.F. Recompile. Note that the error may exist in the prior versions of the model, however, this modified file may not be compatible with earlier version of the code.
OpenMP compile in V3 (posted 5/16/08, updated 5/23/08)
Problem 1: WRF build mechanism does not actually incorporate OpenMP when smpar and dm+sm are selected. This is fixed in V3.0.1.
Solution 1: After running configure and selecting either (smpar) or (dm+sm) option, edit the resulting configure.wrf file and add $(OMP) to the FCFLAGS line.
Problem 2: Certain physics options do not work correctly with OpenMP compile. These are cu_physics = 3 (Grell-Devenyi) and 5 (new Grell 3D scheme); mp_physics = 7 (Goddard GCE) and 10 (Morrison); and ra_lw_physics = 3, ra_sw_physics = 3 (both CAM radiation). There is no known problem with these physics options if OpenMP is not used. Likewise, there is no known OpenMP problems with other physics options.
Solution 2: Do not attempt to use the above listed options with OpenMP compile.
Using Shared Libraries with NETCDF 3.6.2 and Later (posted 6/20/08)
Problem: If one encounters the following problem at runtime:
>wrf.exe
wrf.exe: error while loading shared libraries: libnetcdf.so.4: cannot open shared object file: No such file or directory
It probably means that you are using netcdf 3.6.2 with shared library build enabled.
Solution: For PGI compiler 6.1 or later, one can add -R/usr/local/netcdf/lib to LIB_EXTERNAL macro in the configure.wrf file, so the line looks like:
LIB_EXTERNAL = $(WRF_SRC_ROOT_DIR)/external/io_netcdf/libwrfio_nf.a \
-L/usr/local/netcdf/lib -lnetcdf -R/usr/local/netcdf/lib
Or, one can rebuild netcdf without shared library option enabled.
Same fix should be applied to WPS configure file, configure.wps.
Using Adaptive Time Stepping with Nest (posted 6/20/08, Fixed In V3.0.1)
Problem: Some users encountered difficulties when using adaptive time stepping with nesting.
Solution: A suggestion has been made by the developer to set namelist variable max_step_increase_pct = 5, 51, 51, i.e. to make this control a domain-dependent variable, and use large value for the nests. To enable this, one will need to modify Registry/Registry.EM and change the following line to:
rconfig integer max_step_increase_pct namelist,domains max_doms 5 h \
"max_step_increase_pct"
Do 'clean -a', 'configure', and compile again so that the domain-dependent namelist can be used.
