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 (signal 11)

azurebullet007

New member
Hi, everyone. I am running wrf for CMAQ model. I wanted to run a simulation from 04/27/2016 to 05/22/2016. But I meet the
Segmentation fault (signal 11) issues. I have modified the time_step for many times. The simulation always stock around 2:10. What should I do to fix it?
The attachments are the namelist.wps and namelist.input file.
 

Attachments

  • namelist.wps
    707 bytes · Views: 0
  • namelist.input
    3.7 KB · Views: 2
May have to go to the WRF-CMAQ forum for this. Here is the link to their group and forum. But someone here might have the answer too.

 
Your namelist.input looks fine to me except that the time step is way samll. For DX=12km, you can set time_step= 60 or 72.

Segmentation fault could be caused by various reasons, e.g., insufficient memory, problematic input data, etc.

Did your case fail immediately after you launch ./wrf.exe, or it failed after a while? In addition to segmentation fault, did you see other error messages?
 
May have to go to the WRF-CMAQ forum for this. Here is the link to their group and forum. But someone here might have the answer too.

Hi, William, I mentioned CMAQ just to introduce my purpose. A
Your namelist.input looks fine to me except that the time step is way samll. For DX=12km, you can set time_step= 60 or 72.

Segmentation fault could be caused by various reasons, e.g., insufficient memory, problematic input data, etc.

Did your case fail immediately after you launch ./wrf.exe, or it failed after a while? In addition to segmentation fault, did you see other error messages?
Hi, Ming. It can run for 2-hour simulation. I cannot find any other error message. I have tried 60 seconds and I will try 72 next time.
 
Your namelist.input looks fine to me except that the time step is way samll. For DX=12km, you can set time_step= 60 or 72.

Segmentation fault could be caused by various reasons, e.g., insufficient memory, problematic input data, etc.

Did your case fail immediately after you launch ./wrf.exe, or it failed after a while? In addition to segmentation fault, did you see other error messages?
Hi, Ming. I have tried 72 for time_step. The result shows that I met the segmentation fault even sooner. Do yo have any other suggestion for me to try?
 
Please double check all your RSL files and find possible error messages, which will be helpful for me to figure out what is wrong. Segmentation fault is often caused by NaN or unreasonable physics variables somewhere.

Also, which version of WRF did you run? What is the forcing data you used?
 
Top