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

./geogrid.exe error! ERROR: Error in ext_pkg_write_field

Zhanghaopeng

New member
Hello everyone. When I running ./geogrid.exe, I meet some errors. The detailed contents are as follows:
Parsed 49 entries in GEOGRID.TBL
Processing domain 1 of 1
Processing XLAT and XLONG
WRF_DEBUG: NetCDF error: Exec format error
WRF_DEBUG: NetCDF error for Var XLAT_M Element sr_x in ext_ncd_put_var_ti.code INTEGER, line 124
WRF_DEBUG: NetCDF error: No such file or directory
WRF_DEBUG: ext_ncd_write_field: NetCDF error in wrf_io.F90, line 2696
ERROR: Error in ext_pkg_write_field
WPS--version--4.3.1
netcdf-c -4.7.2
netcdf-fortran -4.5.2
gcc--10.1.0
Can you give me some advices?
 

Attachments

  • configure.wps
    3.4 KB · Views: 0
  • geogrid.log
    10.5 KB · Views: 1
  • namelist.wps
    788 bytes · Views: 1
Hi,
Apologies for the long delay in response while our team tended to time-sensitive obligations. Thank you for your patience.

I see in another thread you mention that you have "write" permissions to the WPS directory, and the directory for which you've set "opt_output_from_geogrid_path."

After geogrid runs (and stops), is there a geo_em.d01* file created? If so, is it complete and readable with something like "ncview?" I assume it's either not created, or doesn't open with a netCDF reader, but if so, can you look to see if anything looks off about the data, and then continue to run ungrib/metgrid/real/wrf to see if there are problems?

I don't think these things would be causing the error you're seeing, but there are worth pointing out:

1) turn off debug_level. This rarely provides any useful information, and ends up just adding a lot of junk to the log file.
2) Your domain is too small. It's using 50x30 grid points. No domain should be smaller than 100x100 grid points. If this isn't causing issues now, it will later. See Why domains should be at least 100x100 grid spaces.
3) If nothing else works, can you try to compile WPS again, from scratch, using a new/pristine version of WPS, and then run geogrid again? It sounds silly, but often these weird errors are resolved simply by reinstalling the code.
 
Hi,
Apologies for the long delay in response while our team tended to time-sensitive obligations. Thank you for your patience.

I see in another thread you mention that you have "write" permissions to the WPS directory, and the directory for which you've set "opt_output_from_geogrid_path."

After geogrid runs (and stops), is there a geo_em.d01* file created? If so, is it complete and readable with something like "ncview?" I assume it's either not created, or doesn't open with a netCDF reader, but if so, can you look to see if anything looks off about the data, and then continue to run ungrib/metgrid/real/wrf to see if there are problems?

I don't think these things would be causing the error you're seeing, but there are worth pointing out:

1) turn off debug_level. This rarely provides any useful information, and ends up just adding a lot of junk to the log file.
2) Your domain is too small. It's using 50x30 grid points. No domain should be smaller than 100x100 grid points. If this isn't causing issues now, it will later. See Why domains should be at least 100x100 grid spaces.
3) If nothing else works, can you try to compile WPS again, from scratch, using a new/pristine version of WPS, and then run geogrid again? It sounds silly, but often these weird errors are resolved simply by reinstalling the code.
Thank you very much for your reply, kwerner!
Now, I have solved the error.
Because I had passed the test of all libraries on the WRF official website before, I thought all the libraries I installed were normal. But jokervtv tell that the error due to a wrong installation of netcdf, I recompiled all the dependent libraries with the intention of giving it a try, and now they can run normally. Maybe I disabled certain functions when installing some libraries, such as HDF5 or NETCDF, which caused me to pass the test on the WRF official website, but I couldn't generate nc files correctly.
 
Top