Quality Meta Data Values of Functions in Comparison
The quality meta data values are stored in the appHistory.ini file. You must not change these values since they are standardized according to MSR, thus ensuring exchange with other users.
In this application, make sure that the variables and functions run through the individual quality meta data values in series. The interpretation of the quality meta data values can be set specifically in the context of the various work processes.
A function can have the same value but different quality meta data values in different datasets. In addition to comparing the values, you can also compare the quality meta data values of the function.
In the calibration data manager, you can display the current quality meta data of the functions of the source dataset in the Variables (& functions) to process list in comparison using the following symbols:
You see these symbols only if you have set the Instant Compare Quality State option to Yes in the Calibration Data Manager.
Note |
You see these symbols only if you have set the Instant Compare Quality State option to Yes in the Calibration Data Manager. |
Source and destination same | Destination not available, or | Source and destination different | ||||||||||||||||||||||||||||||||||||||||||
|
|
|
The symbols show a chart in which the colored sector represents (for example) the degree of completeness or validation, as well as the result of the comparison of the quality meta data values.
Comparison rules
The following comparison rules apply:
 | Green The source dataset contains quality meta data values. In the destination datasets, all functions, variables and subfunctions are present with the same quality meta data values. At least one destination dataset is present. |
 | Red At least one quality meta data value is different. |
 | Blue Only the source dataset contains quality meta data values. or The source dataset and the destination datasets contain no quality meta data values. or Different quality meta data values occur in the variables or subfunctions (green and blue). |
Example
The following example shows how the comparison rules are used with functions.
Process | Source Function 1/Variable 1 | Destination 1 Function 1/Variable 1 | Result Source Function 1/Variable 1 |
1 | No quality meta data /No quality meta data | No quality meta data /No quality meta data |
|
2 | No quality meta data /No quality meta data | No quality meta data /A |
|
3 | No quality meta data /A | No quality meta data /A |
|
4 | A/A | No quality meta data /A |
|
5 | A/A | A/B |
|
6 | A/A | A/A |
|
7 | A/A | A/No variable |
|
8 | A/A | No quality meta data /No variable |
|
9 | A/A | B/No variable |
|
No quality meta data: The
variable has no quality meta data value.
A, B: Valid quality meta data values.
No variable: The variable is not available.
*) See special aspects.
Special aspects
The comparison of quality meta data values of functions is made only on variables and subfunctions available in the source dataset. The tree structure of the function is not compared.
This results in the following special aspects:
The destination dataset contains additional variables or subfunctions.
These are not taken into account in the result.
The destination dataset contains fewer variables or subfunctions.
The result is "blue".
The function in the destination dataset contains all variables or subfunctions, but not all are referenced.
This is not taken into account in the result.