| Note |
|---|
As of release 2007/01 the Analysis function is no longer available. |
| Table of Contents |
|---|
Analysis of a Configuration
...
Timeseries are matched on the following keys:
Key ** | Comment |
locationId | A locationId is unique. A timeseries may also be identified using a locationSetId, which is a collection of locationId's. A locationSetId may consist of a large number of locationId's. When a locationSetId is used, the locationSetId is shown in the tree and the underlying timeseries are shown in a table. |
parameterId | the parameterId is unique |
timeSeriesType | the timeSeriesType is unique |
timeStep | the time step is unique |
moduleInstanceId | a timeseries will in most cases be assigned a moduleInstanceId that is equal to the moduleInstance that creates it. However, this is not a rule. It may equally be possible that a time series is assigned a different moduleInstanceId. For each timeseries it is therefore required that both moduleInstanceId's are used to identify the timeseries: |
...
General rule: each module requires an input and an output timeseries.
Special case: some module may obtain data from other sources or may not produce a timeseries. The special cases are given the table below.
Module | Input to the module | Output from the module |
importRun | import xml files from filesystem |
|
transformation | Optional: timeseries or profile data |
|
export |
| xml file to filesystem |
general adapter | Optional: timeseries or import from filesystem in PI format | optional: timeseries or export to filesystem |
interpolation | Input and output timeseries are always the same |
|
...