WRF Known Problems V4.0.2
When RRTMG is turned on with CAM ozone as input (o3input=2), the variable ozmixm has 13 elements in time dimension, and monthly ozone data is stored in the 2nd to 13th elements, corresponding to 1-12 month. In the subroutine "ozn_time_int", however, the time dimension for "ozmixm" is not specified accordingly. This causes the interpolation to be off by 1 month, giving an incorrect zero-value.
The above problem is corrected in the phys/module_radiation_driver.F file. See the GitHub commit here for additional details and specific code modifications. You can also download the corrected file here: Modified module_radiation_driver.F
You will need to place the modified file in your phys/ directory and then recompile the code. There is no need to issue a 'clean -a' or to reconfigure prior to recompiling.
When running real.exe with some datasets (seen often with ERA-interim, but has also been seen with CFSR and GFS), along with the default namelist.input option "surface_input_source = 3", users see the fatal error:
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: LINE: 2963
mismatch_landmask_ivgtyp
-------------------------------------------
This was a problem that began in V3.8 when the default for surface_input_source was changed from 1 to 3. The file dyn_em/module_initialize_real.F was modified to fix the problem. For detailed information on the problem, fix, and for the specifics of the modified code, see the GitHub commit here. Users can download the corrected file here: Modified module_initialize_real.F
You will need to place the modified file in your dyn_em/ directory and then recompile the code. There is no need to issue a 'clean -a' or to reconfigure prior to recompiling.
When running Noah-MP with no urban scheme (bulk method), the roughness length in urban areas used a bare soil value. This resulted in a high temperature, high wind speed, and low sensible heat flux over cities.
A correction is made to the phys/module_sf_noahmplsm.F file to use z0 from the Noah-MP look-up table. See the GitHub commit here for additional details and specifics on the code modification. Users can download the corrected file here: Modified module_sf_noahmplsm.F
You will need to place the modified file in your dyn_em/ directory and then recompile the code. There is no need to issue a 'clean -a' or to reconfigure prior to recompiling.
If a user tried to start a simulation after the last LBC valid period, the WRF model would get into an infinite loop and print out repeated statements:
THIS TIME 2000-01-24_18:00:00, NEXT TIME 2000-01-25_00:00:00
d01 2000-01-25_06:00:00 Input data is acceptable to use: wrfbdy_d01
2 input_wrf: wrf_get_next_time current_date: 2000-01-24_18:00:00 Status = -4
d01 2000-01-25_06:00:00 ---- ERROR: Ran out of valid boundary conditions in file wrfbdy_d01
The file share/input_wrf.F has been modified to resolve the problem. See the GitHub PR for additional details and specifics on the code modification. Users can download the corrected file here:Modified input_wrf.F
You will need to place the modified file in your share/ directory and then recompile the code. There is no need to issue a 'clean -a' or to reconfigure prior to recompiling.