I have been experiencing this problem from the versions later than 3.7 - as follows:
If domain setup has non-uniform e_we and e_sn in the nests, wrf.exe stops exactly at the time set for radt (if it is set at 10, wrf stops
at this time). If I run only one domain (parent one), I am not experiencing this problem. Is there anything I need to change for the
nests to run. Also, if I set the nest dx=dy < 4 km, the wrf stops without giving any errors (no cfl violation, etc)., Did anyone find this
issue while running WRF?
&geogrid
parent_id = 1, 1, 2,
parent_grid_ratio = 1, 3, 3,
i_parent_start = 1, 100, 150,
j_parent_start = 1, 140, 80,
e_we = 335, 469, 355,
e_sn = 335, 235, 355,
geog_data_res = 'usgs_lakes+30s','usgs_lakes+30s','usgs_lakes+30s',
dx = 18000,
dy = 18000,
map_proj = 'mercator',
ref_lat = 40.0,
ref_lon = 95.0,
ref_x = 167.5
ref_y = 167.5
truelat1 = 40.0,
truelat2 = 40.0,
stand_lon = 95.0,
opt_geogrid_tbl_path = './'
geog_data_path = '/iitm2/cccr-res/ramesh/Models/geog'
If domain setup has non-uniform e_we and e_sn in the nests, wrf.exe stops exactly at the time set for radt (if it is set at 10, wrf stops
at this time). If I run only one domain (parent one), I am not experiencing this problem. Is there anything I need to change for the
nests to run. Also, if I set the nest dx=dy < 4 km, the wrf stops without giving any errors (no cfl violation, etc)., Did anyone find this
issue while running WRF?
&geogrid
parent_id = 1, 1, 2,
parent_grid_ratio = 1, 3, 3,
i_parent_start = 1, 100, 150,
j_parent_start = 1, 140, 80,
e_we = 335, 469, 355,
e_sn = 335, 235, 355,
geog_data_res = 'usgs_lakes+30s','usgs_lakes+30s','usgs_lakes+30s',
dx = 18000,
dy = 18000,
map_proj = 'mercator',
ref_lat = 40.0,
ref_lon = 95.0,
ref_x = 167.5
ref_y = 167.5
truelat1 = 40.0,
truelat2 = 40.0,
stand_lon = 95.0,
opt_geogrid_tbl_path = './'
geog_data_path = '/iitm2/cccr-res/ramesh/Models/geog'