geogrid.exe fails unless using cglc_modis_lcz LANDUSEF — possible cause?

[ZHOU Wan]

Hi all,

I'm encountering an issue when running ./geogrid.exe. The model fails with the following error message:

ERROR: Could not find interpolator sequence for requested resolution for LANDUSEF.
The sources specified in namelist.wps are not listed in GEOGRID.TBL.

This happens when I do not explicitly specify LANDUSEF in geog_data_res, for example:

geog_data_res = 'y2010_urb+y2010_ahe+ISA_CQ+default',
'y2010_urb+y2010_ahe+ISA_CQ+default',
'y2010_urb+y2010_ahe+ISA_CQ+default',

Or even using:

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

However, when I include the cglc_modis_lcz LANDUSEF dataset, everything runs fine:

geog_data_res = 'cglc_modis_lcz+y2010_urb+y2010_ahe+albedo_glass2020+modis_fpar2022+modis_lai2022+ISA_LCZ2018+default',
'cglc_modis_lcz+y2010_urb+y2010_ahe+albedo_glass2020+modis_fpar2022+modis_lai2022+ISA_LCZ2018+default',
'cglc_modis_lcz+y2010_urb+y2010_ahe+albedo_glass2020+modis_fpar2022+modis_lai2022+ISA_LCZ2018+default',

So my questions are:

1. Why does geogrid.exe fail when I don’t specify cglc_modis_lcz, even though previously default worked?
2. Does this relate to priority settings in GEOGRID.TBL or missing index files for other LANDUSEF sources?
3. Is there a way to override or force WPS to use a fallback LANDUSEF when others fail?

I believe my static data files are fine — the directories exist, and I used to be able to run with default alone.

Below is my full namelist.wps for reference:

&share
wrf_core = 'ARW',
max_dom = 3
start_date = '2022-08-01_00:00:00', '2022-08-01_00:00:00', '2022-08-01_00:00:00'
end_date = '2022-08-05_23:00:00', '2022-08-05_23:00:00', '2022-08-05_23:00:00'
interval_seconds = 3600,
io_form_geogrid = 2,
/

&geogrid
parent_id = 1, 1, 2
parent_grid_ratio = 1, 3, 3
i_parent_start = 1, 81, 201
j_parent_start = 1, 81, 201
e_we = 307, 439, 79
e_sn = 311, 451, 121

geog_data_res = 'cglc_modis_lcz+y2010_urb+y2010_ahe+albedo_glass2020+modis_fpar2022+modis_lai2022+ISA_LCZ2018+default',
'cglc_modis_lcz+y2010_urb+y2010_ahe+albedo_glass2020+modis_fpar2022+modis_lai2022+ISA_LCZ2018+default',
'cglc_modis_lcz+y2010_urb+y2010_ahe+albedo_glass2020+modis_fpar2022+modis_lai2022+ISA_LCZ2018+default',
! geog_data_res = 'default','default','default'
dx = 9000.0
dy = 9000.0
map_proj = 'lambert'
ref_lon = 106.79891570499628
ref_lat = 29.73164201861055
truelat1 = 30.0
truelat2 = 60.0
stand_lon = 105.0
geog_data_path = '/WPS_GEOG'
/

&ungrib
out_format = 'WPS',
prefix = 'SFILE',
/

&metgrid
fg_name = 'SFILE', 'FILE',
io_form_metgrid = 2,
opt_metgrid_tbl_path = '/WRF-4.6/WPS-4.6.1/metgrid'
/

Thanks in advance for your help!

 

[kwerner]

Hi, If you have all the default static data files stored in the directory set for geog_data_path, setting geog_data_res to default should not give this error. And by adding the "+default" to each entry, that should ensure that you can at least use the default landuse. I have a couple thoughts/questions.

1. Is your WPS_GEOG directory actually in the top-level of your directories, so that it's correct that its full path should just be "/WPS_GEOG"?
2. Have you made any modifications to the GEOGRID.TBL file that may affect the default settings for landuse?

Can you issue the following and then attach the geogrid.txt, wpsgeog_pwd.txt, and wpsgeog_ls.txt files?

From the WPS directory:
ls -ls geogrid/* >& geogrid.txt


cd /WPS_GEOG
pwd >& wpsgeog_pwd.txt
ls -ls >& wpsgeog_ls.txt

 

[ZHOU Wan]

1. Is your WPS_GEOG directory actually in the top-level of your directories, so that it's correct that its full path should just be "/WPS_GEOG"?

Thank you for your suggestions. I'd like to respond to the two points raised:

1. Geog Data Path Clarification​

Regarding the geog_data_path, I can confirm that I did use the full and correct absolute path in my actual namelist.wps configuration. The value used was:

geog_data_path = '/data/wanzhou/WPS_GEOG'

In my initial post, I omitted the leading part of the path (/data/wanzhou/) for brevity and privacy reasons, but the actual path used when running geogrid.exe is complete and correct. To verify, I executed:

pwd >& wpsgeog_pwd.txt

The output was: /data/wanzhou/WPS_GEOG, which confirms that the path is valid and matches the directory structure in my system.

​

2. GEOGRID.TBL Modifications​

I did make additions to the GEOGRID.TBL file to include several new land use datasets. However, I did not modify the entry associated with default. The line in the GEOGRID.TBL remains unchanged and points to the correct default dataset:

rel_path = default:modis_landuse_20class_30s_with_lakes/

Additionally, I verified that the required files for the default dataset are present and accessible. I ran:

ls -ls geogrid/* >& geogrid.txt

The output indicated that GEOGRID.TBL is symbolically linked to the correct file:

0 lrwxrwxrwx. 1 wanzhou research 55 Oct 12 20:45 geogrid/GEOGRID.TBL -> /home/wanzhou/WRF-4.6/WPS-4.6.1/geogrid/GEOGRID.TBL.ARW

I also confirmed that the modis_landuse_20class_30s_with_lakes/ directory exists under /data/wanzhou/WPS_GEOG. The detailed listing was saved in wpsgeog_ls.txt and shows that the default land use data is present.

Summary​

Given the above, I believe the issue may not stem from a missing path or misconfigured GEOGRID.TBL. It is possible that the geog_data_res settings or the priority handling within GEOGRID.TBL might be affecting the resolution matching process when default is not explicitly listed.

Parsed 58 entries in GEOGRID.TBL
Processing domain 1 of 3
ERROR: Could not find interpolator sequence for requested resolution for LANDUSEF. The sources specified in namelist.wps is not listed in GEOGRID.TBL.

I will continue testing and report back if I identify a more specific cause. Thanks again for your support.