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

(SOLVED) Ungrib segmentation fault

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

elliottardif

New member
Hi everyone, I am attempting to run WPS within WRFv4.1.2, and I am running into a problem with ungrib. It gives a segmentation fault immediately after running the executable (see text below). I have no further information on anything ungrib is running prior to the segmentation fault. Unlimit and the chmod 775 suggested in another post do not work in this case. Any help on resolving this issue is greatly appreciated.

/storage/highspeed/EMT/WRFv4.1.2-ifc/WPS > ./ungrib.exe
Segmentation fault (core dumped)
/storage/highspeed/EMT/WRFv4.1.2-ifc/WPS >


Thank you for your time,

Elliot Tardif
 
Hi Elliot,
Can you attach your ungrib.log file, as well as your namelist.wps? Thanks!
 
Hi kwerner, I have attached the namelist.wps file to this reply. I do not have an ungrib.log file because none was produced before the segmentation fault occurred.

Thank you,

Elliot Tardif
 

Attachments

  • namelist.wps
    1.4 KB · Views: 79
Elliot,
Thanks for sending that. I don't see anything out of the ordinary in your namelist that would cause a segmentation fault.
1) Were you able to run geogrid without any problems?
2) Can you attach a couple of time periods of your input data so that I can try to run the case with your namelist?
3) Will you please also attach your configure.wps file and your WPS compile log so that I can check how it was compiled?
 
Good afternoon kwerner, here are my answers to your questions.

1. I am able to run geogrid with no issues.
2. I am using operational NAM data from NCEP (link: https://nomads.ncep.noaa.gov/pub/data/nccf/com/nam/prod/). The .grib2 files themselves are ~60M apiece so I don't think I'd be able to attach them here. You may download a couple files from nomads and drop them in.
3. I have attached the requested files to this reply for your review.

Thank you,

Elliot Tardif
 

Attachments

  • configure.wps
    3.3 KB · Views: 66
  • log.compile
    89.7 KB · Views: 62
One other point of note: I am able to run earlier versions of WRF (e.g., 3.9) using the same configuration with no problem.

Thank you,

Elliot Tardif
 
Hi Elliot,
I'm not sure exactly which files you used for your run. There are so many different ones listed in each of the links from the NAM directory (from the link you sent). You could try to package a couple files up and attach them here. If they are too large, see the home page of this forum for information on submitting large files. It would be helpful if I was using the exact files you are just to be sure. T'hanks!
 
Although the NAM data are in GRIB2 format, it's likely that ungrib isn't even getting to the point of trying to open one of the GRIB files if the segmentation fault occurs before ungrib even creates an ungrib.log file. In this case, it might be worth trying to clean and reconfigure the WPS without GRIB2 support in order to test whether it is the JasPer, PNG, or libz libraries that might be interacting badly with the v4.1 ungrib code.
 
Good afternoon, my apologies for the delay in responding. I will try configuring WPS and see if that helps. If not then I will send some large files from my test.

Thanks all for your help!

Elliot Tardif
 
Good afternoon, I wanted to put a period on this effort. I was never able to get ungrib working on v4.1.2, so I downloaded v4.2 and it now works fine. I am thinking it was a version-specific issue. Thanks to everyone for their help.

Best,

Elliot Tardif
 
Top