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

EDIT ::: RESOLVED ---- Child domain with same resolution as parent domain


THE PROBLEM WAS THAT "GEOG_DATA_RES" needed to be defined for both domains.


I am attempting to create a nested domain configuration such that the child domain has the same resolution as the parent domain. The reason for wanting to do this is that I have multiple input data sources and other pre-compiled programs that use additional ancillary data that are set up to run on the parent domain, but I need to conduct some simulations on a smaller domain. My idea was to create the necessary files for the parent domain and then just use ncks to cut out the portion of the domain that I need. The problem is that upon creating the domains, they do not seem to overlap exactly:

For example, here is the &geogrid portion of namelist.wps:

parent_id = 1, 1,
parent_grid_ratio = 1, 1,
i_parent_start = 1, 321,
j_parent_start = 1, 177,
e_we = 954, 405,
e_sn = 835, 265,
geog_data_res = 'modis_lakes',
dx = 0.1218330000000000000,
dy = 0.1218330000000000000,
map_proj = 'lat-lon',
pole_lat = 36.0
pole_lon = 180.
stand_lon = 106.0
ref_lat = 54.0
ref_lon = -106.0,

Then, if I cut the LANDMASK field from the smaller domain (note that ncks uses 0-based indexing):

ncks -v LANDMASK -d south_north,176,439 -d west_east,320,723
ncks -v LANDMASK

And compare it to the LANDMASK from the smaller domain, I find that they are not identical:

Given the +1/-1 locations, it does not simply look like a shift in one or both directions (i.e., I would assume alternating +1/-1 at boundaries).

I appreciate the advice.



Screen Shot 2022-08-18 at 12.40.45 PM.png
Last edited: