- 积分
- 35
- 贡献
-
- 精华
- 在线时间
- 小时
- 注册时间
- 2020-3-20
- 最后登录
- 1970-1-1
|
发表于 2020-5-8 10:55:54
|
显示全部楼层
本帖最后由 ranmao 于 2020-5-8 11:25 编辑
是修改 METGRID.TBL 这个文件的控制内容吗?这是官网上找到的类似的问题
The issue may be in how the metgrid program is interpolating the skin temperature field from a grid that is essentially identical to the WRF model domain defined by geogrid. In the v4.1 METGRID.TBL file, the entry for SKINTEMP is as follows:
CODE: SELECT ALL
========================================
name=SKINTEMP
mpas_name=skintemp
interp_option=sixteen_pt+four_pt+wt_average_4pt+wt_average_16pt+search
masked=both
interp_land_mask = LANDSEA(1)
interp_water_mask = LANDSEA(0)
fill_missing=0.
========================================
I'd need to look further into the metgrid code to see exactly how the interpolation methods handle a grid point that is not surrounded by valid data in the input (intermediate) dataset, but as a quick test, could you try modifying the SKINTEMP entry so that it looks like the following?
CODE: SELECT ALL
========================================
name=SKINTEMP
mpas_name=skintemp
interp_option=nearest_neighbor
fill_missing=-999.
========================================
You'll only need to re-run metgrid and check whether there are any -999 values in the interpolated skin temperature field in your met_em files. If there are no -999 values, that would tell us that it is the interpolation methods that are the cause of the zero values in the top row of the interpolated field, in which case we may be able to make the interpolation methods more robust (or just use a nearest-neighbor interpolation, since we know the source and target grids are identical).
|
|