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

WPS configure problem and ./geogrid problem


New member
Dear Supporters,
I have already installed WRF-4.3.3 with sm+dm(gun). But when I configured WPS,there was no option to select.Like this.

Will use NETCDF in dir: /thfs1/software/netcdf/4.8.0-gcc9.3.0-mpi-x
Using WRF I/O library in WRF build identified by $WRF_DIR: /thfs1/home/qx_hyt/hpp/model/PWRF/WRF-4.3.3
Found Jasper environment variables for GRIB2 support...
$JASPERLIB = /thfs1/software/jasper/2.0.14-gcc9.3.0/lib
$JASPERINC = /thfs1/software/jasper/2.0.14-gcc9.3.0/include
Please select from among the following supported platforms.

Enter selection [1-0] :

I copied other configure.wps to compile, and modified the path of WRF. It worked. I saw ./geogrid.exe, metgrid.exe and ungrib.exe. But when ./geogrid.exe, it had a mistake.Like this.

Abort(1090831) on node 0 (rank 0 in comm 0): Fatal error in PMPI_Init: Other MPI error, error stack:
MPIR_pmi_init(91)....: PMIX_Init returned -25

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0 0x40000769d5b7 in ???
#1 0x400007d3aaa8 in ???
#2 0x400007c6866f in ???
#3 0x400007a0db4b in ???
#4 0x428a0f in ???
#5 0x4044af in ???
#6 0x40000892408f in ???
#7 0x403323 in ???
Segmentation fault (core dumped)

Can someone helps me? Thank you.


  • configure.wps
    3.4 KB · Views: 4
  • namelist.wps
    703 bytes · Views: 3
  • compile.log
    106.9 KB · Views: 4
Last edited:
Just a note that it's not necessary to compile WPS with a parallel option (e.g., dmpar) unless you are planning to use very large domains (thousands x thousands of grid cells). However, you've already compiled it with the dmpar option, and that's okay. Since you were able to compile successfully, the error you're getting is not related to the compiling process, so you shouldn't need to recompile.

One thing I do notice is that your domain is extremely small (36x25 grid points). You should not run a simulation smaller than 100x100 grid points. If you are trying to use multiple processors to run geogrid, that could potentially be causing you issues. I would recommend making your domain larger and then using either a single processor, or very few (e.g., 4). Can you try that and let me know what happens?