Using the ExtData component: Difference between revisions
Line 95: | Line 95: | ||
Occasionally the user might want to satisfy a variable with a data set that is constant (only one time on a file that has no tokens) and should not be time interpolated. If the user specifies "-" for the refresh template (update once) and ExtData finds that the file template has not tokens, and that the file itself only has one time, ExtData will note this and update the variable once, and update the variable once with this set of data. | Occasionally the user might want to satisfy a variable with a data set that is constant (only one time on a file that has no tokens) and should not be time interpolated. If the user specifies "-" for the refresh template (update once) and ExtData finds that the file template has not tokens, and that the file itself only has one time, ExtData will note this and update the variable once, and update the variable once with this set of data. | ||
==== Vector Variables ==== | ==== Vector Variables ==== | ||
When importing winds into an application the user has the option to handle these specially so that the u and v components are not separately treated as scalars, but as proper vector quantities when regridding to the target grid. Currently this is only supported when going from Lat-Lon data to an application on the Cube-Sphere grid. The syntax is as follows | When importing winds into an application the user has the option to handle these specially so that the u and v components are not separately treated as scalars, but as proper vector quantities when regridding to the target grid. Currently this is only supported when going from Lat-Lon data to an application on the Cube-Sphere grid. The syntax is for this is as follows: | ||
UC0;VC0 'm s-1' xyz C N N 0 0.0 1.0 U;V file_template | |||
Notice the difference is that the two components of the wind are entered on one line and separated by a semi-colon, likewise the corresponding variables in the file are separated by a semi-colon. | |||
In addition to regridding to the cube, the u and v components will be moved to the stagger location and rotation (along the meridonal and zonal directions or along the cube faces) specified in the import spec, for example to import winds to the cube-sphere grid on the c-grid stagger location and rotated along the cube faces, you would define the imports as such: | |||
call MAPL_AddImportSpec ( gc, & | |||
SHORT_NAME = 'UC0', & | |||
LONG_NAME = 'eastward_wind_on_C-Grid_after_advection', & | |||
UNITS = 'm s-1', & | |||
STAGGERING = MAPL_CGrid, & | |||
ROTATION = MAPL_RotateCube, & | |||
DIMS = MAPL_DimsHorzVert, & | |||
VLOCATION = MAPL_VLocationCenter, RC=STATUS ) | |||
VERIFY_(STATUS) | |||
call MAPL_AddImportSpec ( gc, & | |||
SHORT_NAME = 'VC0', & | |||
LONG_NAME = 'northward_wind_on_C-Grid_before_advection', & | |||
UNITS = 'm s-1', & | |||
STAGGERING = MAPL_CGrid, & | |||
ROTATION = MAPL_RotateCube, & | |||
DIMS = MAPL_DimsHorzVert, & | |||
VLOCATION = MAPL_VLocationCenter, RC=STATUS ) | |||
VERIFY_(STATUS) | |||
The possible staggering locations are MAPL_AGrid, MAPL_CGrid, MAPL_DGrid. | |||
The possible rotation options are MAPL_RotateLL (winds will be along meridonal and zonal directions) or MAPL_RotateCube (winds will be rotated along the cube faces). | |||
=== Masks === | === Masks === |