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

ungrib crashes with intel compiler

alainF

Member
Hello,
I try to rebuild my system with the Intel compiler.
I passed all the tests of the tutorial about compiling WRF.
I have successfully built WRF and WPS, and all the required libraries such as netcdf, jasper...
geogrid.exe runs fine,
But ungrib.exe crashes when it has output all the PFILE:*** it had to do.
The message is :

Name of source model =>NCEP GFS Analysis
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
libc.so.6 00007FDD4537A520 Unknown Unknown Unknown
ungrib.exe 00000000004238C5 Unknown Unknown Unknown
ungrib.exe 000000000040E65D Unknown Unknown Unknown
ungrib.exe 000000000040735D Unknown Unknown Unknown
libc.so.6 00007FDD45361D90 Unknown Unknown Unknown
libc.so.6 00007FDD45361E40 __libc_start_main Unknown Unknown
ungrib.exe 0000000000407275 Unknown Unknown Unknown

I have compiled it in serial mode and you will find attached the log of the compiler and also namelist.wps.
I have tried to compile in dmpar mode and obtained same result.
Thank you for your help.
 

Attachments

  • ungrib.log
    613.4 KB · Views: 3
  • namelist.wps
    1.6 KB · Views: 1
  • log.compile.txt
    84.7 KB · Views: 1
Hi,
Is it possible that you only pointed to the grib-specific libraries when building WPS, and you are no longer pointing to the right paths? If you aren't sure, can you send your configure.wps file, and please issue the following commands, and send the .txt files:

Code:
echo $JASPER_INC >& jasperinc.txt

echo $JASPER_LIB >& jasperlib.txt

echo $LD_LIBRARY_PATH >& ld.txt
 
Hello,
Thanks a lot for your reply.
Concerning Jasper variables, I thought that the names were JASPERINC and JASPERLIB, not JASPER_INC and JASPER_LIB. In doubt, I have set JASPER_LIB and JASPER_INC to JASPERLIB and JASPERINC. I ran ungrib.exe with the same result than before.
You will find the requested files. I have also included the copy of $PATH.
 

Attachments

  • configure.wps
    3.3 KB · Views: 1
  • jasperinc.txt
    44 bytes · Views: 1
  • jasperlib.txt
    40 bytes · Views: 1
  • ld.txt
    1,002 bytes · Views: 0
  • path.txt
    935 bytes · Views: 1
I have succeeded !
Actually, I had to type the following commands before runtime :

ulimit -s unlimited
export OMP_STACKSIZE=4G (although I don't know if this one is really important)

I knew the trick for wrf.exe, but I did not know that it would be important for running ungrib.exe too.
I think that this is due to the Intel compiler.
But also I wonder if the large size of the input grib files are also responsible for that ( 42 x 550 MB, and each file named FILE:*** generated by ungrib has a size of 818 MB (it is quite large !)
 
That is great news! I'm glad to hear you found a solution, and I suppose the large size of the files were the culprit. As for your message regarding the variables "JASPERLIB" and "JASPERINC," you're absolutely correct, and they should be set, without the underscore. I apologize for the confusion I caused!
 
I have succeeded !
Actually, I had to type the following commands before runtime :

ulimit -s unlimited
export OMP_STACKSIZE=4G (although I don't know if this one is really important)

I knew the trick for wrf.exe, but I did not know that it would be important for running ungrib.exe too.
I think that this is due to the Intel compiler.
But also I wonder if the large size of the input grib files are also responsible for that ( 42 x 550 MB, and each file named FILE:*** generated by ungrib has a size of 818 MB (it is quite large !)
That is great news! I'm glad to hear you found a solution, and I suppose the large size of the files were the culprit. As for your message regarding the variables "JASPERLIB" and "JASPERINC," you're absolutely correct, and they should be set, without the underscore. I apologize for the confusion I caused!

The question is why is these commands needed for intel and not for gnu?
Code:
ulimit -s unlimited
export OMP_STACKSIZE=4G (although I don't know if this one is really important)

And why don't they work all the time?
 
Top