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

./metgrid.exe error

N

noah_lover

New member
Hi,
The following error occurs when I run ./metgrid.exe, the geogrid.exe and ungrib.exe were running successfully.
The WPS version is 4.6.0, the forcing data is NCEP GDAS Final Analysis ds083.3.
However, I can run a case successfully before when use the gfs data.
How can I solve the error?
Thanks for your reply!

root@fab332271e79:/WRF/noah/Build_WRF/WPS-4.6.0# ./metgrid.exe
Processing domain 1 of 1
Processing 2025-02-01_00
FILE
Processing 2025-02-01_06
FILE
Processing 2025-02-01_12
FILE
Processing 2025-02-01_18
FILE
Processing 2025-02-02_00
FILE
Processing 2025-02-02_06
FILE
Processing 2025-02-02_12
FILE
Processing 2025-02-02_18
FILE
Processing 2025-02-03_00
FILE
Processing 2025-02-03_06
FILE
Processing 2025-02-03_12
FILE
Processing 2025-02-03_18
FILE
Processing 2025-02-04_00
FILE
Processing 2025-02-04_06
FILE
Processing 2025-02-04_12
FILE
Processing 2025-02-04_18
FILE
Processing 2025-02-05_00
FILE
Processing 2025-02-05_06
FILE
Processing 2025-02-05_12
FILE
Processing 2025-02-05_18
FILE
Processing 2025-02-06_00
FILE
Processing 2025-02-06_06
FILE
Processing 2025-02-06_12
FILE
Processing 2025-02-06_18
FILE
Processing 2025-02-07_00
FILE
Processing 2025-02-07_06
FILE
Processing 2025-02-07_12
FILE
Processing 2025-02-07_18
FILE
Processing 2025-02-08_00
FILE
Processing 2025-02-08_06
FILE
Processing 2025-02-08_12
FILE
Processing 2025-02-08_18
FILE
Processing 2025-02-09_00
FILE
Processing 2025-02-09_06
FILE
Processing 2025-02-09_12
FILE
Processing 2025-02-09_18
FILE
Processing 2025-02-10_00
FILE
Processing 2025-02-10_06
FILE
Processing 2025-02-10_12
FILE
Processing 2025-02-10_18
FILE
Processing 2025-02-11_00
FILE
Processing 2025-02-11_06
FILE
Processing 2025-02-11_12
FILE
Processing 2025-02-11_18
FILE
Processing 2025-02-12_00
FILE
Processing 2025-02-12_06
FILE
Processing 2025-02-12_12
FILE
Processing 2025-02-12_18
FILE
Processing 2025-02-13_00
FILE
Processing 2025-02-13_06
FILE
Processing 2025-02-13_12
FILE
Processing 2025-02-13_18
FILE
Processing 2025-02-14_00
FILE
Processing 2025-02-14_06
FILE
Processing 2025-02-14_12
FILE
Processing 2025-02-14_18
FILE
Processing 2025-02-15_00
FILE
Processing 2025-02-15_06
FILE
Processing 2025-02-15_12
FILE
Processing 2025-02-15_18
FILE
Processing 2025-02-16_00
FILE
Processing 2025-02-16_06
FILE
Processing 2025-02-16_12
FILE
Processing 2025-02-16_18
FILE
Processing 2025-02-17_00
FILE
Processing 2025-02-17_06
FILE
Processing 2025-02-17_12
FILE
Processing 2025-02-17_18
FILE
Processing 2025-02-18_00
FILE
Processing 2025-02-18_06
FILE
Processing 2025-02-18_12
FILE
ERROR: Error in ext_pkg_write_field
Note: The following floating-point exceptions are signalling: IEEE_OVERFLOW_FLAG IEEE_UNDERFLOW_FLAG IEEE_DENORMAL
 
The namelist.wps file

&share
wrf_core = 'ARW'
max_dom = 1
start_date = '2025-02-01_00:00:00', '2025-08-05_00:00:00'
end_date = '2025-02-28_18:00:00', '2025-08-06_00:00:00'
interval_seconds = 21600
io_form_geogrid = 2
active_grid = .true.,.true.,
debug_level = 0
/

&geogrid
parent_id = 1, 1
parent_grid_ratio = 1, 3
i_parent_start = 1, 99
j_parent_start = 1, 86
e_we = 100, 766
e_sn = 50, 391
geog_data_res = 'default', 'default'
dx = 25000
dy = 25000
map_proj = 'lambert'
ref_lat = 37
ref_lon = 107
truelat1 = 30
truelat2 = 60
pole_lat = 90
pole_lon = 0
stand_lon = 107
geog_data_path = '/mnt/liuen_WRFdata/WPS_GEOG/'
opt_geogrid_tbl_path = './geogrid/'
&ungrib
out_format = 'WPS'
prefix = 'FILE'
/

&metgrid
fg_name = 'FILE'
io_form_metgrid = 2
opt_metgrid_tbl_path = './metgrid'
/
 
noah_lover said:
The namelist.wps file

&share
wrf_core = 'ARW'
max_dom = 1
start_date = '2025-02-01_00:00:00', '2025-08-05_00:00:00'
end_date = '2025-02-28_18:00:00', '2025-08-06_00:00:00'
interval_seconds = 21600
io_form_geogrid = 2
active_grid = .true.,.true.,
debug_level = 0
/

&geogrid
parent_id = 1, 1
parent_grid_ratio = 1, 3
i_parent_start = 1, 99
j_parent_start = 1, 86
e_we = 100, 766
e_sn = 50, 391
geog_data_res = 'default', 'default'
dx = 25000
dy = 25000
map_proj = 'lambert'
ref_lat = 37
ref_lon = 107
truelat1 = 30
truelat2 = 60
pole_lat = 90
pole_lon = 0
stand_lon = 107
geog_data_path = '/mnt/liuen_WRFdata/WPS_GEOG/'
opt_geogrid_tbl_path = './geogrid/'
&ungrib
out_format = 'WPS'
prefix = 'FILE'
/

&metgrid
fg_name = 'FILE'
io_form_metgrid = 2
opt_metgrid_tbl_path = './metgrid'
/
Click to expand...
you might be facing an issue where the grid isn't meeting the best practices.

see these posts by @kwerner


 
@noah_lover
The error you're seeing typically means that you are missing surface data and you should check that all your 3d meteorological fields include surface-level data.

That being said, the links posted above by William.Hatheway's are worth looking at for best practices in setting up your domain. For e.g., domains should be no smaller than 100x100 grid points.
 
kwerner said:
@noah_lover
The error you're seeing typically means that you are missing surface data and you should check that all your 3d meteorological fields include surface-level data.

That being said, the links posted above by William.Hatheway's are worth looking at for best practices in setting up your domain. For e.g., domains should be no smaller than 100x100 grid points.
Click to expand...
Hi kwerner,
Thanks for your reply!
WRF stoped on 2025-02-18_18 during the ./metgrid.exe. So, you mean the file on 2025-02-18_18 missed surface data? As mentioned above, When I tried to run WRF using initial and boundary data in March, 2025 instead Febrary, 2025, the model run successfully...I will replace the 2025-02-18_18 file and try to run WRF again.
 
noah_lover said:
Hi kwerner,
Thanks for your reply!
WRF stoped on 2025-02-18_18 during the ./metgrid.exe. So, you mean the file on 2025-02-18_18 missed surface data? As mentioned above, When I tried to run WRF using initial and boundary data in March, 2025 instead Febrary, 2025, the model run successfully...I will replace the 2025-02-18_18 file and try to run WRF again.
Click to expand...
This is likely because the GFS data has the surface information, but the GDAS data doesn't
 
You must log in or register to reply here.
Top