all third-level commands in block > OBSERVATION
The times at which the observed and calculated system response are compared are referred to as calibration times. They are specified using command
The standard situation is sketched in Figure (a) below, assuming that equally spaced calibration times (dashed lines)
have been defined.
If, for some reason, only a subset of the available data can be used for calibration as shown in Figure (b),
the user must specify the time window between which data should be processed:
time_A and time_B are the lower and upper bounds of the window. Only one time window may be specified per data set. If more than one time window is required, new data sets containing the same data must be generated and different time windows specified for each data set (see keyword INDIVIDUAL for an alternative option).
The time units of time_A and time_B can be specified using one of the time_unit keywords.
If a data set does not contain data that extend over the entire range of calibration times, iTOUGH2 automatically adjusts the time window to coincide with the first and last data point as shown in Figure (c). A warning message is printed, however, which can be avoided by explicitly specify the time window. If the specified time window is larger than the available data set, the value of the first and last data point is horizontally extrapolated to time_A and time_B, respectively, as indicated in Figure (d).
If keyword INDIVIDUAL is present, individual time windows will be set around each data point, and the observation times will be automatically added to the vector of calibration times. No time_A and time_B need to be specified in this case.
If time is shifted, the time window must be given with reference to the time system of the
data, if command
>> :7 EQUALLY spaced TIMES in [MINUTES]
>>> ELEMENT: ZZZ99
>>>> DATA [HOURS] on FILE: pres.dat
>>>> time WINDOW: 299.0 901.0 [SECONDS] -> 3 calibration points
>>>> DEVIATION : 1.E3