- 积分
- 5027
- 贡献
-
- 精华
- 在线时间
- 小时
- 注册时间
- 2013-2-1
- 最后登录
- 1970-1-1
|
登录后查看更多精彩内容~
您需要 登录 才可以下载或查看,没有帐号?立即注册
x
本帖最后由 莎朗嘿哟YY 于 2015-2-4 18:50 编辑
我现在的问题是,我要把模式数据比如vor[i,j,k]插值到这样一个点(29,106,653.8)上面,括号里面是纬度,经度,hpa
也就是我现在要把模式数据往一个三维空间点上去插值。然后我找到了这个dk_anyprofile子程序(子程序在附件里面),我感觉是可以满足我这个要求的,但是
我想问一下,有人在IDL里面使用过dk_anyprofile这个插值函数嘛????具体怎么使用啊,看了说明有点看不明白。望大神指点一二。说明如下:
; anyprofile
; ----------
;
; Interpolates from grid (model/UM) data to the points on a profile (for
; example the 3-D vertical track of a sonde or a satellite profile).
; Neither the gridded data nor the observations need be on fixed
; pressure (or other) levels.
;
; Vertical coords to interpolate to can be a set of fixed levels (using
; the COMMON_Y keyword, and not necessarily the same as either the model
; or obs levels) or the original levels of the obs. GRID_Y can be a 4D
; grid of e.g. pressures applying to each individual gridded data point, or
; can be a vector applying to regular pressure gridded data. The algorithm (算法)
; works whatever. Only dependence is a regular lat/lon grid for the model data.
;
; The profile is broken into a series of contiguous(邻近的) segments(部分). Each
; segment is the section of the profile bounded by the same four
; grid points. For GOMOS, the profile has been seen to pass through
; up to 9 different grid boxes, creating 9 different "segments".
;
; Vertical interpolation is in log pressure (or theta), from UM levels to the
; profile levels. The horizontal interpolation to profile points is
; bilinear(双线性) in lat and lon (see book 11-6). (水平插值是双线性的)
;
; Inputs
; ------
;
; grid_data - 3 or 4D regular lat-lon gridded data
; [lon,lat,lev,optional time]
; grid_longitude - Matching lon and lat, lev and time arrays
; grid_latitude
; grid_y
; grid_time (still required even if only one time slot位置)
;
; profile_data - 2D profile data [lev,profile_num]
; profile_longitude - 2D matching longs [lev,profile_num]
; profile_latitude - 2D ditto同上 lats
; profile_time - 1D matching IDL julian day time [profile_num]. There is
; as yet no height dependence here.
; profile_y - 2D profile vertical coords [lev,profile_num]. Pressure
; or theta usually
;
; Outputs
; -------
;
; umprofiles - structure containing gridded data interpolated to
; the observation lons, lats, and to either
; common levels (COMMON_Y option) or observation
; levels (default)
;
; Keywords
; --------
;
; COMMON_Y - specifies(确定) a common set of levels onto which to interpolate
; grid and profile data. If not set, default is to interpolate
; grid data to the profile levels
;
; LEVEL_AVERAGE - profile data is binned between half levels calculated
; from the COMMON_Y full levels. Not yet implemented apart from with
; COMMON_Y
;
; KEEP_ALL_MODEL - On COMMON_Y levels, we can keep all model data rather
; than setting it to NaN if corresponding profile pt. does not
; exist.
;
; REPEAT_CALL - Anyprofile is designed to work on 4D data, but if this
; does not fit into memory, pass in either smaller 4D chunks or
; 3D fields. Setting this keyword will build up the umprofiles
; output structure over multiple calls to this routine. This assumes
; that the set of independent profiles is the same for each call
; and that there are not memory problems there!
;
; INDPROFILES - Outputs independent data in a structure in the
; same format as UMPROFILES. This is only useful (and only
; implemented) for the COMMON_Y case.
;
; WINDOW - Half size of time window, in days. Default is WINDOW = 0.125,
; i.e all profiles within +/- 3 hours of model data are considered. ???
;
; 8/11/04 AJG
; ??? future keywords to go to GRID flex pressures or PROFILE..???
|
|