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

Similar to segmentation fault

ghuan

New member
Hi, I always run wrf.exe and it stops suddenly within 3-6 hours. Sometimes it shows "segmentation fault", and sometimes it returns nothing.I have tried for three days, including lowering time_step, setting automatic step size or repeatedly adjusting the number of cores, but none of them worked. I will attach my last namelist.input, namelist.wps and some rsl.out. I hope to get your effective reply as soon as possible. Thank you very much!
 

Attachments

  • namelist.input
    4.9 KB · Views: 1
  • namelist_gh.wps
    867 bytes · Views: 1
  • rsl.out.0000
    279.4 KB · Views: 1
Hi,
Because there isn't a lot of information provided in the rsl* file, I can't say, without a doubt, what the issue is, but I have a couple of thoughts:

1) The size of d01 is too small

Code:
e_we      = 90, 178, 247,
e_sn       = 75, 130, 265,

See Why domains should be at least 100x100 grid spaces for an explanation

2) Due to the size of d02 and especially d03, you likely need to use more than just 30 processors. I understand that the size of d01 prevents you from using many more than that, but if you increase the size of domain 1 (based on the above description), you should be able to use a number of processors better suited for the size of d03. See Choosing an Appropriate Number of Processors.

3) You mentioned decreasing the time_step. Were you getting CFL errors in your rsl* files when your time_step was larger? If not, it may not be necessary to use a smaller time_step. You can issue the following to determine whether CFL errors exist when using a larger time step:
Code:
grep cfl rsl*
 
Top