...
Defining input variables for computations
The input variables to compute derived quantities need to be specified when the dataset is loaded. The following example shows the "Add datset" dialog in Met.3D v1.7. The input variables need to be specified by a "/"-separated string using the mapping "CF standard name:NetCDF or GRIB input variable name".
For example, assume that you are loading ECMWF ensemble forecast data from GRIB files. The variables will be named "u", "v", etc. in the GRIB files. For ECMWF-GRIB files only, Met.3D appends "(ens)", "(an)", "(fc)" to indicate whether the data refers to ensemble forecasts, analyses or HRES forecasts. Hence, your mapping string could look like:
| Code Block |
|---|
eastward_wind:u (ens)/northward_wind:v (ens)/air_temperature:t (ens)/specific_humidity:q (ens)/surface_geopotential:z (ens)/surface_air_pressure:sp (ens)/surface_temperature:2t (ens)/lwe_thickness_of_precipitation_amount:tp (ens)/geopotential:z (ens)/atmosphere_relative_vorticity:vo (ens) |
If your input data is read from NetCDF files, you would use the NetCDF variable names directly. E.g., if you u-wind variable is called "u_wind" in the input file, the corresponding part in the mapping would be "eastward_wind:u_wind".
Available derived quantities
...
| Info | ||
|---|---|---|
| ||
he The variables in the following list support all grid and vertical level types unless otherwise noted. |
...