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 metgrid.exe error

deva_wrf

Member
Dear sir,
I am facing error while runing metgrid in WPS

Error
./metgrid.exe
Processing domain 1 of 3
Processing 2023-09-21_00
FILE
Processing 2023-09-21_03
FILE
Processing 2023-09-21_06
FILE
Processing 2023-09-21_09
FILE
Processing 2023-09-21_12
FILE
ERROR: Error in ext_pkg_write_field
application called MPI_Abort(MPI_COMM_WORLD, 0) - process 0

input file from NCEP GFS (.25*.25) for the year 2023
WPS 4.0 and WRF 4.0 used


and these are the last line of metgrid.log fle

2024-08-01 12:56:29.405 --- INFORM: Couldn't find SOILT100 at level 200100.000000 to fill level 100.000000 of SOILT.
2024-08-01 12:56:29.405 --- INFORM: Going to create the field SOIL_LEVELS
2024-08-01 12:56:29.405 --- INFORM: Going to create the field PRES
2024-08-01 12:56:29.405 --- INFORM: Couldn't find PSFC at level 200100.000000 to fill level 200100.000000 of PRES.
2024-08-01 12:56:29.434 --- Initializing output module.
2024-08-01 12:56:29.436 --- ERROR: Error in ext_pkg_write_field
 
Last edited:
Dear sir,
I am facing error while runing metgrid in WPS

Error
./metgrid.exe
Processing domain 1 of 3
Processing 2023-09-21_00
FILE
Processing 2023-09-21_03
FILE
Processing 2023-09-21_06
FILE
Processing 2023-09-21_09
FILE
Processing 2023-09-21_12
FILE
ERROR: Error in ext_pkg_write_field
application called MPI_Abort(MPI_COMM_WORLD, 0) - process 0

input file from NCEP GFS (.25*.25) for the year 2023
WPS 4.0 and WRF 4.0 used


and these are the last line of metgrid.log fle

2024-08-01 12:56:29.405 --- INFORM: Couldn't find SOILT100 at level 200100.000000 to fill level 100.000000 of SOILT.
2024-08-01 12:56:29.405 --- INFORM: Going to create the field SOIL_LEVELS
2024-08-01 12:56:29.405 --- INFORM: Going to create the field PRES
2024-08-01 12:56:29.405 --- INFORM: Couldn't find PSFC at level 200100.000000 to fill level 200100.000000 of PRES.
2024-08-01 12:56:29.434 --- Initializing output module.
2024-08-01 12:56:29.436 --- ERROR: Error in ext_pkg_write_field
can you upload all your metgrid log files and namelist.wps file
 
This is more like a data issue. I don't think there is anything wrong with WPS codes.

Where did you download your GFS data?
 
That is the correct site where you should download GFS data. GFS datafiles form this webiste have been widely used for runing WRF, and we don't think ther eis nay issue with this dataset. Also, WPS codes work just fine.

Your issue is derived from libs you installed or inappropriate environmental settings of your computer. Please consult your computer manager how to install libs and set environment of your machine.
 
Earlier I have performed multiple simulation, they run smoothly all the library is installed, but when we run this case its shows some error mentioned above
 
Please upload your namelist.wps for me to take a look. I will see whether I can repeat your case .....
 
I am able to run your case successfully. The only change I made to your namelist.wps is:

geog_data_res = 'default','default','default',

I also run this case in parallel mode because this is a big case with the following options:

Code:
e_we              =  143, 304, 664
 e_sn              =  128, 265, 532

I would suggest you test this case over a single domain, i.e., max_dom =1. If it can run successfully, we can be sure that the WPS codes work fine. I am suspicious that somehow your machine doesn't have sufficient memory to run such a big case.
 
I perform other run, then the metered.exe run fine, I think it the problem is regarding to the gfs data set or the namelist.wps, I am using was 4.0 and wrf 4.0
too
I am getting the same error when running with max domain =1,
 
Last edited:
I am perplexing by this case...

If possible, please try newer version of WPS (e.g., WPSv4.5), and let me know whether it works.
 
What is the error message in your compiling log file? If you didn't save the message, please re-try:
./ compile > wps.log

Then upload your wps.log. for me to take a look.
 
Top