Differences of Calculated Results
Revision as of 06:28, 6 May 2015 by (→Definitions: valod operators added)
For data generated by
- mathematical models (model results), or
- analysis of calculated results (characteristic numbers), or
- measured data (observational data)
Various differences can be computed. Input data can be typically categorized as follows:
- Category K0: , time-independent quantities;
- Category K1: , time-dependent quantities, one time step;
- Category KC: , time-dependent quantities, several discrete time steps, constant time step ;
- Category KN: , time-dependent quantities, several discrete time steps, varying time step .
For geophysical data categories K1, KC and KN are of significance. Examples:
- Category K1: topography/bathymetry for a specific instant in time;
- Category KC: water level at discrete times with constant time step, e. g. computed by a mathematical model;
- Category KN: tidal high water for times at non-equidistant time intervals, e.g. derived from a water level time serie.
- reference data : with respect to various deviations for can be evaluated. Typical data are either observational data or computational as well as analysis results for a specific (reference) state (situation);
- variant data : can be also either observational data or computational as well as analysis results, for which deviations shall be computed with respect to the reference state. Typically variant data are given for a different period in time (natural variation) or a different state of the system under study.
- valid operator 1: returns .T. or .F., in dependence whether is valid or invalid. Can be also applied to .
- valid operator 2: returns .T. or .F., in dependence whether is valid or invalid.
Requirements for the computation of differences
The following requirements must be fulfilled by and :
- and must belong to the same category (see above);
- the number of times must be identical for and ;
- for data belonging to category KC constant time steps must coincide for and ;
- (physical) dimension as well as meaning must be equivalent for and ;
- (short for ) as well as (short for ) must be valid data for the same instant in time; otherwise the dervied results will become invalid.
The following computational rules are implemented in NCDELTA.
back to Pre- and Postprocessing