Note |
---|
As of release 2007/01 the Analysis function is no longer available. |
Table of Contents |
---|
...
Analysis of a Configuration
Configuration analysis provides the means to in detail analyze a configuration. The analysis uses the dependencies between three configuration objects: workflows, Module Instances and timeSeriesSets to provide a visual overview of the configuration.
To analyze a configuration, activate the Analysis tab of the Configuration Manager.
1.1.1 Anchor
Approach
The principle of the configuration analysis is quite simple. For each workflow in the configuration, all module instances that are used are shown in the order in which they are used. For a selected module instance then all timeseries that are created by that module instance are displayed as the top level timeseries.
...
This procedure is recursively followed through until for example an import module instance is encountered. Following this through allows broken links, unexpected starts or ends to be easily found in a configuration.
1.1.2 anchor
Implementation
When the Analysis mode is selected, a database of all timeseries is created. This involves that all module instances are analyzed for all the timeseries that are created and that are required within each module instance. For a selected module instance the input and output timeseries are matched in order to build the analysis tree.
The configuration files have been made such that a large amount of freedom is given to the user in setting up a configuration. _Toc76626496 Anchor
Matching of timeseries
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: |
Handling of cyclic references
The configuration files allow a certain degree of cyclic referencing. A cyclic reference is caused when a module creates a timeseries that matches the input timeseries. In this case an infinite loop would be caused in the analysis processing. Note that for the actual configuration a cyclic reference does not pose any problem whatsoever.
For certain modules a cyclic reference is expected and must be handled explicitly. This is the case for the interpolation module and for the transformation module. In other cases when a cyclic reference is found no absolute inference can be made regarding the nature of the cyclic reference, and further analysis must be stopped. _
_
Transformation module
A typical example of apparent cyclic referencing in the transformation module configuration is given with the following example, in which a time series is created through merging a number of time series where after in the same configuration the merged time series is checked to ensure that no values below a given value are found.
...
Handling of this case is straightforward. When in a single interpolation module multiple interpolationSets are configured having the exact same timeseries as a result, it may be safely assumed that the last timeseries is the principal result timeseries. The other timeseries may be skipped in the analysis. _Toc76626497 Anchor
Handling of special cases
There are a number of special cases, exceptions to a general rule, that must be handled correctly by the analysis.
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 |
|
...
Using the Configuration Manager Analysis Tool
For each workflow in the configuration, all module instances that are used are shown in the order in which they are used. These are displayed in the left pane of the window:
...