Restart issues
Problem: In this release, the restart capability is broken, unless one restarts from a boundary condition time. This means if one has 6 hourly lateral boundary conditions, and if one restarts at 6 hourly interval, restart works fine. Restarting from at times between the boundary times may fail.
Solution: We are looking for a fix to the problem.
diff_opt = 2 Problem with V3.9.1 Release
Problem: In the file dyn_em/module_diffusion_em.F, some undefined k indices were used outside k loops instead of kts. This happened in one line of the recently changed (since V3.9.1) code to fix the slope terms in diff_opt=2. This affects the v-wind component computation in the y direction at the surface over sloped terrain. This problem only occurs when using the diff_opt = 2 option, along with the use of terrain data, in the y direction (e.g., this would apply to all real data cases over land. This would not apply to any of the idealized cases, unless terrain was added. This does not apply to the hill_2d_x case, as it is x-direction specific).
Solution: Replace your dyn_em/module_diffusion_em.F file with this file. Go back to WRFV3/ and recompile. It is not necessary to issue a 'clean -a' or to reconfigure. Simply recompile, and the compilation should be fairly quick.
ERA-Interim Data Problem
Problem: When using ERA-Interim data, along with the default namelist.input option 'surface_input_source = 3', you may get the following error:
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: LINE: 2963
mismatch_landmask_ivgtyp
-------------------------------------------
Solution: There currently is no formal fix for this problem, but until we track down the exact cause and solution, a work-around is to simply change "surface_input_source" to 1 (instead of 3) in the namelist.input file, and then re-run real, which should correct the problem, and not cause any changes in your output.
Out of bounds error in module_diffusion_em.F for v3.9.1
Problem: In the dyn_em/module_diffusion_em.F file for v3.9.1, there is an out-of-bounds error in the horizontal_diffusion_v_2 subroutine. The computation of the field zy_at_v in the i,j loop (not the i,k,j loop). The "k" index for the array zy should be "kts". This bug was introduced with v3.9.1 and fixed in v3.9.1.1.
This is the original (WRONG) line (line 2907)
zy_at_v(i, kts, j) = 0.5 * (zy(i, k, j) + zy(i, k + 1 , j))
Here is the correct line in v4:
zy_at_v(i, kts, j) = 0.5 * (zy(i, kts, j) + zy(i, kts + 1 , j))
Solution: Modify the module_diffusion_em.F file to reflect the correct line, as indicated above. Save the file and then go back to WRFV3/ and recompile. There is no need to clean the code, or to reconfigure. A simple recompilation should suffice.
Half vs. Full 1D Coefficients for Hybrid Vertical Coordinate in small_step Routine (posted September 11, 2018)
Problem: In the original implementation of the hybrid vertical coordinate (v3.9), the
cpp directives utilized capitalization to differentiate between the use
of full-level (c1f, for example) and half-level (c1h, for example) 1d
coeffieicent arrays. For several locations in the dyn_em/module_small_step.F routine, the use of the
"mu" array with the "t_2" field incorrectly was assigned to full levels.
In four statements where the half-level t_2 array is used, the half-level
c1h and c2h 1d arrays replace the incorrect full-level 1d arrays c1f and c2f.
Solution: There is a modification to the file dyn_em/module_small_step_em.F. Please download the module_small_step_em.F.fix-for-v3.9.1.tar.gz file, place it in your WRFV3/dyn_em/ directory, and then unpack the file. You will then need to recompile the code; however, since this is not a configuration or registry change, it will not be necessary to issue a 'clean -a' or to reconfigure. Simply recompile the code.
"random seed" Compilation Error for G3 (Posted November 24, 2018)
Problem:
Some compilers will complain with the following error:
call random_seed (PUT=seed)
1
Error: Size of 'put' argument of 'random_seed' intrinsic at (1) too small (12/33)
module_cu_g3.f90:3195:41:
Solution: Place this modified module_cu_g3.F file in your phys/ directory and recompile the code.
"Ran out of valid boundary conditions in file wrfbdy_d01" infinite loop
Problem: 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
Solution:
The file share/input_wrf.F has been modified to resolve the problem. See the GitHub Pull Request 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.
