Quality Meta Data Values of Variables 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 variable 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 variables.
In the calibration data manager, you can display the current quality meta data state of the variables of the source dataset in the Variables (& functions) to process list in comparison using the following symbols:
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 | 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 variables 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. |
Example 1
The following example shows how the comparison rules are used with single variables.
Process | Source Variable 1 | Destination 1 Variable 1 | Destination 2 Variable 1 | Result Source Variable 1 |
1 | No quality meta data | No quality meta data | No quality meta data |
|
2 | No quality meta data | No quality meta data | A |
|
3 | No quality meta data | A | A |
|
4 | No quality meta data | A | B |
|
5 | A | No quality meta data | No quality meta data |
|
6 | A | No quality meta data | A |
|
7 | A | No quality meta data | B |
|
8 | A | A | A |
|
9 | A | A | B |
|
10 | A | B | B |
|
11 | A | No variable | A |
|
12 | A | No variable | No quality meta data |
|
13 | A | No variable | B |
|
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.
Example 2
The following example shows how the comparison rules are used with two or more variables.
Process | Source Variable 1/Variable 2 | Destination 1 Variable 1/Variable 2 | Result Source Variable 1/Variable 2 |
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 | No variable/A |
|
8 | A/A | No variable/No quality meta data |
|
9 | A/A | No variable/B |
|
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.