WRF4.5 real.exe Error: LATC_LOC Array Bounds Exceeded Despite insert_bogus_storm = .false.

[zhanyx]

Hello,
I am conducting tests using WRF4.5-debug. When running real.exe, after successfully generating the wrfinput files for the first five domains, the wrfinput file for the last domain was not produced. The same error message appears at the end of all rsl.error.* files:

forrtl: severe (408): fort: (2): Subscript #1 of the array LATC_LOC has value 6 which is greater than the upper bound of 5

Image PC Routine Line Source
real.exe 000000000C297DC9 Unknown Unknown Unknown
real.exe 00000000009C76D0 module_configure_ 14147 module_configure.f90
real.exe 000000000204CBD3 module_alloc_spac 141 module_alloc_space_0.f90
real.exe 0000000000781DD4 module_domain_mp_ 1269 module_domain.f90
real.exe 00000000014A1A0A module_dm_mp_patc 676 module_dm.f90
real.exe 00000000014C6B3F wrf_dm_patch_doma 6466 module_dm.f90
real.exe 0000000000772804 module_domain_mp_ 410 module_domain.f90
real.exe 0000000000775023 module_domain_mp_ 678 module_domain.f90
real.exe 0000000000413BA8 MAIN__ 183 real_em.f90
real.exe 0000000000412A62 Unknown Unknown Unknown
libc-2.28.so 000014CDD418FCF3 __libc_start_main Unknown Unknown
real.exe 000000000041296E Unknown Unknown Unknown

I found that LATC_LOC is a variable related to bogus tropical cyclones, but I have already set insert_bogus_storm = .false. in namelist.input. Why is the error still related to it?
Thank you very much in advance for your time and help.

 

[zhanyx]

Hello,
I recompiled WRF without enabling the debug option. real.exe successfully generated all wrfinput files. However, when running wrf.exe, a segmentation fault occurred. Therefore, I recompiled WRF again with the debug option enabled to obtain more detailed error information. As a result, after running wrf.exe, it only output wrfout_d01_2024-06-20_00:00:00 before reporting an error. Below is the error message in rsl.error:

d01 2024-06-20_00:00:00 in NOAH DRV
forrtl: error (65): floating invalid
Image PC Routine Line Source
wrf.exe 000000000DFE8F35 Unknown Unknown Unknown
libpthread-2.28.s 000014E5FBC34CE0 Unknown Unknown Unknown
libhdf5.so.200.0. 000014E60092840F __libm_powf_e7 Unknown Unknown
wrf.exe 000000000CA43555 module_sf_noahlsm 4422 module_sf_noahlsm.f90
wrf.exe 000000000CA3C657 module_sf_noahlsm 3833 module_sf_noahlsm.f90
wrf.exe 000000000CA34F8D module_sf_noahlsm 2782 module_sf_noahlsm.f90
wrf.exe 000000000CA2B627 module_sf_noahlsm 2028 module_sf_noahlsm.f90
wrf.exe 000000000CA1C8DE module_sf_noahlsm 757 module_sf_noahlsm.f90
wrf.exe 000000000C898D52 module_sf_noahdrv 1044 module_sf_noahdrv.f90
wrf.exe 00000000091D3CBC module_surface_dr 2684 module_surface_driver.f90
wrf.exe 0000000005A351CF module_first_rk_s 392 module_first_rk_step_part1.f90
wrf.exe 000000000462504E solve_em_ 943 solve_em.f90
wrf.exe 0000000003EB6321 solve_interface_ 123 solve_interface.f90
wrf.exe 00000000005B85AB module_integrate_ 329 module_integrate.f90
wrf.exe 0000000000413666 module_wrf_top_mp 326 module_wrf_top.f90
wrf.exe 00000000004129B9 MAIN__ 29 wrf.f90
wrf.exe 0000000000412962 Unknown Unknown Unknown
libc-2.28.so 000014E5FB693CF3 __libc_start_main Unknown Unknown
wrf.exe 000000000041286E Unknown Unknown Unknown

Additionally, I checked wrfinput_d01 and found that many variables contain all zeros:

BUILD AREA FRACTION
BUILD HEIGHT
BUILD SURF RATIO
CANWAT
CPLMASK
FRC URB2D
MH URB2D
O3 GFS DU
PC
PCB
SEAICE
SR
STDH URB2D
TOPOSLPX
TOPOSLPY
UOCE
VOCE
WATER DEPTH

Could these variables be the cause of the problem?