| scrollbar |
|---|
| Table of Contents |
|---|
Introduction
...
A time series set may be defined to retrieve all members of an ensemble at once (for example in evaluation of ensemble statistics). This is done by defining the optional ensembleId. The ensembleId should also be defined when writing new ensemble members. (e.g. on importing ensembles in the import module).
Example
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<timeSeriesSet> <description>Example time series set</description> <moduleInstanceId>ImportTelemetry</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.obs</parameterId> <locationId>4539.TF</locationId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="minute" multiplier="15"/> <relativeViewPeriod unit="hour" start="-48" end="24" endOverrulable="true"/> <readWriteMode>read only</readWriteMode> <synchLevel>1</synchLevel> <expiryTime unit="day" multiplier="100"/> </timeSeriesSet> |
...
- A manually edited value will get the expiry time of the timeseriesset it is in, in the filters.xml or displaygroups.xml (depending on from which display the edit session started).
- If there is not expiryTime configured, then the default expirytime from the global.properties file will be taken.
- If this expiry time is not set, a default of 10 days is used.