|
Input data may be specified either by giving a path in the Source parameter or by giving a GRIB-based data object in the Data parameter. Note that you should specify either Source or Data, not both.
Drop a MARS Retrieval or a GRIB file icon inside this icon field. In Python or Macro, supply a Fieldset object.
Select a method for specifying the output grid.
Note 2: Interpolation as k-nearest neighbours is the only method able to support filtering
Supply a grid definition as described here: grid - keyword in MARS/Dissemination request.
Examples of valid grid definitions:
GUI | Python / Macro | Result |
---|---|---|
1/1 | [1, 1] or "1/1'" | A regular lat/lon grid with 1x1 degree point spacing |
0.25/0.25 | [0.25, 0.25] or "0.25/0.25" | A regular lat/lon grid with 0.25x0.25 degree point spacing |
O1280 | "O1280" | An octahedral reduced Gaussian grid, octahedral with 1280 latitude lines between the pole and equator |
N640 | "N640" | An 'original' reduced Gaussian grid, with 640 latitude lines between the pole and equator |
F400 | "F400" | A regular Gaussian grid, with 400 latitude lines between the pole and equator |
This parameter can be left empty to preserve the grid properties (regular/reduced lat/lon or Gaussian) while performing other kinds of post-processing (changing bits per value, calculation of gradients, etc.).
If Grid Definition Mode is Template, set path to a GRIB file to be used as template.
If Grid Definition Mode is Template, set a GRIB-based data object to be used as template.
These projections require setting several parameters, named following the convention in their descriptions:
Most of these parameters are required and do not have default values, meaning that they must be filled in. The parameters are:
Here are examples of generating Lambert grids.
| |||
|
Activates processing that is particular to wind fields. Winds are represented by its vector Cartesian components u/v (gridded) or U/V (spectral) and, typically, they are archived as (spectral) vorticity/divergence (vo/d.) The relation between the spectral and gridded wind components is u = U / cos(latitude) and v = V / cos(latitude).
It is up to the user to specify if the input consists of wind fields. Set this appropriatelly in order to perform the correct processing.
Possible options are:
| Converts pairs of Cartesian components vector fields (spectral) U/V to (gridded) u/v. This option is required if regridding wind fields on/to a rotated grid. Note: assumes that the input come in pairs of alternating U/V. |
| Converts pairs of (spectral) vo/d fields into (spectral) U/V or (gridded) u/v. In case of gridded output, scaling by the cosine of their latitudes is applied (as above.) Note: assumes that the input come in pairs of alternating vo/d. |
| Each processed field is treated individually. |
If the input files are spectral, the following parameters are used to fine-tune the conversion to grid points. The general workflow is:
Spherical harmonics truncation, as described here: truncation - keyword in MARS/Dissemination request.
When the output is spectral, defines the output intended truncation; When the output is gridded, defines the intermediate truncation before spectral inverse transform to gridded space. Possible values are Automatic, None or a number describing the spectral truncation to be applied.
Intermediate grid when performing spectral inverse transform to gridded space, as described intgrid - keyword in MARS/Dissemination request.
Possible values are:
There is a high degree of customisation available to parametrise the available interpolation methods. Please note:
Specifies the type of interpolation to be used on the fields. The default is Automatic, which selects either Linear or Nearest Neighbour based on an internal table of known parameters. If the parameter is unknown, the default will be Linear. The possible interpolation methods are:
Available for any of the 'nearest' interpolation methods; Supports Interpolation K-Nearest Neighbours or Nearest LSM. Possible values are:
| input points with radius (option Distance) of output point |
| n-closest input points (option Nclosest) to output point (default 4) |
| input points respecting Distance ∩ Nclosest |
| input points respecting Distance U Nclosest |
| n-closest input points (option Nclosest), if all are at the same distance (within option Distance Tolerance) return all points within that distance (robust interpolation of pole values) |
| nearest input point, if at the same distance to other points (option Nclosest) chosen by lowest index |
| Sample of n-closest points (option Nclosest) out of input points with radius (option Distance) of output point, not sorted by distance |
| as above, sorted by distance |
Associated options supporting Nearest Method (described above):
Only available if Interpolation is K Nearest Neighbours. General way on how to interpolate input neighbouring point values to output points, including the Inverse Distance Weighting (IDW) class methods (see Wikipedia), which operates over input points returned by Nearest Method. Possible values are:
| filter for processing topographic data (see IFS documentation, Part IV: Physical Processes, 11.3.1 Smoothing operator) |
| IDW of the form distance-1; If input points match output point, only that point's value is used for output |
| IDW of the form (1 + distance2)-1 |
| IDW of the form distance-p (option Distance Weighting Shepard Power, default 2.) |
| IDW of the form exp(- distance2 / (2 σ)2) (option Distance Weighting Gaussian Stddev, default 1.) |
| emulate Interpolation as Nearest Neighbour by picking first point (note that, when Nearest Method is Sample, a random near point is picked) |
| no distance weighting, average input values (irrespective of distance) |
On multiple input points, weights are normalised linearly to unity. Associated options supporting Distance Weighting (described above):
This treatment is applied after calculation of the interpolation weights, and before they are applied to input values to generate output values. This allows modifications of these weights based on input data, such as the presence of missing values — In any case, no missing values are ever used for interpolation.
Most of the options avaiable concern modyfing the set of input points weights pertaining to a specific output point. When removing interpolation weights (pe. because they point to a missing value) all the remaining interpolation weights are re-normalised (linearly) to sum(wi) = 1.
Possible values are:
| if all input point values (contributing to an output point) are missing, set output value to missing (it requires all input point values to be missing) |
| if any input point values (contributing to an output point) are missing, set output value to missing (it suffices one input missing value) |
| if the most significant point for interpolation (largest interpolation weight) is missing, set output value to missing (typically, not generally, this corresponds to the nearest input point) |
| allows a user-specified value (option Simulated Missing Value) with a tolerance (option Simulated Missing Value Epsilon) |
| emulate Interpolation as Nearest Neighbour by selecting the most significant point for interpolation to each output point (discarding the other contributions) |
| no non-linear corrections are applied |
* In the presence of missing values this can can create wrong results.
Associated options supporting Non Linear (described above):
Land-sea masks (LSMs) can be configured for two different purposes:
Only available if Interpolation is Nearest LSM. Possible values are:
Only available if LSM is On, this is the factor adjusting input point weights if they are not of the same type (land/sea) as related output point; On application, all contributing input point weights are re-normalised (linearly) to sum(wi) = 1.
Specifies whether the input/output LSM file will come from LSM Named Input/Output (named, default) or LSM File Input/Output (file).
Select one of the predefined names from the following:
| binary-based LSM sourced from MODIS Land Water Mask MOD44W (see reference) |
| binary-based LSM at high resolution (legacy, pre-climate files version 15) |
| GRIB-based IFS supporting climate files version 15, on this specific grid |
| (as above, for this grid) |
| (as above, for this grid) |
| (as above, for this grid) |
| (as above, for this grid) |
| (as above, for this grid) |
Provide the path to an input/output LSM GRIB file.
If input/output is not on the same grid (geometry) as provided input/output LSM (respectively), interpolate with this method to a temporary LSM with required geometry.
For GRIB-based LSM (so excluding '1km' and '10min'), the threshold for condition (value ≥ threshold) to distinguish land (true) from sea (false).
This options allows application of differential operators to input fields. The current available approach is similar as used in the Finite Volume Module of the IFS, specifically:
It employs an edge-based, median-dual finite-volume method, with field values interpreted as averaged quantities of the supporting "dual cells".
There is support for both scalar and vector (u/v) fields; Due to the geometrical interpretation being ill-posed at the poles (singularities) there is an additional option to force missing values at the poles.
Activates a nabla (differential) operator processing on the fields. Possible options are:
| Scalar field gradient (∇) |
| Scalar field Laplacian (∇2) |
| Vector (u/v) field gradient (∇) |
| Vector (u/v) field divergence (∇⋅) |
| Vector (u/v) field vorticity or curl (∇×) |
| no differential processing |
Due to the supporting differential operators calculation method, values aren't well defined at the poles (singularities); This option allows forcing missing value at the poles. Possible values are On and Off.
Supply a grid definition as described here: area - keyword in MARS/Dissemination request (swapping north/south).
Specifies the geographical area that the output fields will cover, the default being for the whole globe. Enter lat/lon in degree bounds of an area separated by a "/" (south/west/north/east), or in Macro or Python provide a list, e.g. [south, west, north, east]; alternatively, use the assist button to define the area graphically.
For example, this set of parameters generates the following output data:
|
Specifies the width of a frame within a given sub-area, as described here frame - keyword in MARS/Dissemination request.
The width of the frame is specified as an (integer) number of grid points inwards from a given area. The following plots show a sub-area with Frame set to 8.
Position of the South Pole of the intended rotated grid as lat/lon in degree, as described here: rotation - keyword in MARS/Dissemination request.
This is applicable to regular lat/lon or regular/reduced Gaussian grids. Enter lat/lon in degree, or in Macro or Python, enter [lat, lon]
; alternatively, use the assist button to select the point graphically.
Specifies the output GRIB bitsPerValue, as described here: accuracy - keyword in MARS/Dissemination request.
If left empty, this will take the value from the input fields. This option can also be used to simply change the number of bits per value in a Fieldset if no other processing options are given. Note that if Packing is set to ieee, then the only valid values for this parameter are 32 and 64.
Specifies the output GRIB packingType, as described here: accuracy - keyword in MARS/Dissemination request.
Possible values are (depending on build-time configuration):
Specifies the output GRIB edition (or format). Note that format conversion is not supported.
Possible values are: