Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

Segmentation fault Runing WRF4.5

xiao.zh

New member
Hi all,
I met this problem while runninf Wrfv4.5:
[comput1:4365 :0:4365] Caught signal 11 (Segmentation fault: address not mapped to object at address 0xfffffffe07e33640)
==== backtrace (tid: 4365) ====
0 0x000000000004d455 ucs_debug_print_backtrace() ???:0
1 0x0000000002d4b161 module_sf_sfclayrev_mp_psim_stable_() ???:0
2 0x0000000002d46564 module_sf_sfclayrev_mp_sfclayrev1d_() ???:0
3 0x0000000002d44136 module_sf_sfclayrev_mp_sfclayrev_() ???:0
4 0x000000000261d208 module_surface_driver_mp_sfclayrev_seaice_wrapper_() ???:0
5 0x00000000025ea0ad module_surface_driver_mp_surface_driver_() ???:0
6 0x0000000001e65f9d module_first_rk_step_part1_mp_first_rk_step_part1_() ???:0
7 0x00000000016e0109 solve_em_() ???:0
8 0x00000000014fde98 solve_interface_() ???:0
9 0x00000000005b11f3 module_integrate_mp_integrate_() ???:0
10 0x00000000005b1810 module_integrate_mp_integrate_() ???:0
11 0x0000000000417a01 module_wrf_top_mp_wrf_run_() ???:0
12 0x00000000004179bf MAIN__() ???:0
13 0x0000000000417952 main() ???:0
14 0x0000000000022555 __libc_start_main() ???:0
15 0x0000000000417869 _start() ???:0
=================================
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
wrf.exe 00000000031BFBDA for__signal_handl Unknown Unknown
libpthread-2.17.s 00002B152C24C630 Unknown Unknown Unknown
wrf.exe 0000000002D4B161 Unknown Unknown Unknown
wrf.exe 0000000002D46564 Unknown Unknown Unknown
wrf.exe 0000000002D44136 Unknown Unknown Unknown
wrf.exe 000000000261D208 Unknown Unknown Unknown
wrf.exe 00000000025EA0AD Unknown Unknown Unknown
wrf.exe 0000000001E65F9D Unknown Unknown Unknown
wrf.exe 00000000016E0109 Unknown Unknown Unknown
wrf.exe 00000000014FDE98 Unknown Unknown Unknown
wrf.exe 00000000005B11F3 Unknown Unknown Unknown
wrf.exe 00000000005B1810 Unknown Unknown Unknown
wrf.exe 0000000000417A01 Unknown Unknown Unknown
wrf.exe 00000000004179BF Unknown Unknown Unknown
wrf.exe 0000000000417952 Unknown Unknown Unknown
libc-2.17.so 00002B152C981555 __libc_start_main Unknown Unknown
wrf.exe 0000000000417869 Unknown Unknown Unknown

I first met this problem while coupling with Wrf_Hydro, then I tried WRF alone, the problem still exits.
I tried the solution at (RESOLVED) WRF Single-layer, UCM crashed
add SF_URBAN_PHYSICS = 1,TS_SCHEME is 2 (Even though I did not consider urban physics at first place)
and

but the problem remains.

can anyone helo me out?
Thanks

Xiao
 

Attachments

  • namelist.input
    3.6 KB · Views: 4
  • namelist.wps
    1.3 KB · Views: 1
  • rsl.error.zip
    12.6 KB · Views: 1
Last edited:
Hi,
Can you let me know the type and the resolution of your input data into WPS?

I see that your d01 is using a resolution (grid-spacing) of 3km. We don't recommend using a parent_grid_ratio of more than ~5:1 - even between the input data and the parent domain. Does your data fall within that range, or is it a larger ratio?
 
Hi,
Can you let me know the type and the resolution of your input data into WPS?

I see that your d01 is using a resolution (grid-spacing) of 3km. We don't recommend using a parent_grid_ratio of more than ~5:1 - even between the input data and the parent domain. Does your data fall within that range, or is it a larger ratio?
Hi, Thanks for your reply. My input data is ERA5 hourly data from 1940 to present. The resolution is 0.25 degrees. The ratio between the input data and d01 is larger than 5:1. Would it help if I add a domain outside my domain 01?
 
Yes, it would help. I don't know that that is definitely causing the issue, but either way, it's better to have a parent domain around the 3km domain, given the resolution of the input data.
 
Top