Quality block
The Quality block sets the quality of fields based on the quality or values of other fields.
Quality block
Description
Depending on configuration, the block sets the quality of the output fields in one of the following two ways:
- The worst of:
- The quality of the field on the Value input port
- The quality of the field on the Quality input port.
or
- The worst of:
- The quality of the field on the Value input port
- The quality of the field on the Quality input port.
- The quality that results from the comparison between the value field on the Quality input port and the configured Value for Good Quality.
quality block
Block Type
Data quality block
Input/Output ports
The block has 2 input ports:
-
Quality Port - The fields that are intended to determine the output quality.
-
Value Port - The fields that are intended to determine the output value.
On the output port, an output field is generated for every field in the Value input port.
Functions performed on tags
-
On the values - The output field values are copied from the field values on the Value input port.
-
On the timestamp - The output field timestamp is the latest of the field timestamp on the Value input port and the field timestamp on the Quality input port.
-
On the quality - Depending on configuration, the block sets the quality of the output fields in one of the following two ways:
-
- If the configuration is set to Use Quality of Fields then the output quality is set to the worst of:
- The quality of the field on the Value input port
- The quality of the field on the Quality input port.
or
- If the configuration is set to Use Values of Fields then the output quality is set to the worst of:
- The quality of the field on the Value input port
- The quality of the field on the Quality input port.
- The quality that results from the comparison between the value field on the Quality input port and the configured Value for Good Quality. (A match results in good quality, a mismatch results in bad quality.)
- If the configuration is set to Use Quality of Fields then the output quality is set to the worst of:
Examples illustrating the use of quality or value of the quality field
These examples illustrate what happens for different permutations of good (1) or bad (0) quality for:
-
Value field quality (the quality on the Value field)
-
Quality field value (the value on the Quality field)
-
Quality field quality (the quality on the Quality field)
We give examples for:
-
"Use_Values_of_Fields"_and_the_"Value_for_Good_Quality"_has_been_configured_as_"1"
-
"Use_Values_of_Fields"_and_the_"Value_for_Good_Quality"_has_been_configured_as_"Good"
If the configuration is set to "Use Quality of Fields"
Value field value | Value field quality | Quality field value | Quality field quality | Output field value | Output field quality |
2 | 1 | 123 | 1 | 2 | 1 |
3 | 0 | 123 | 1 | 3 | 0 |
4 | 1 | 234 | 1 | 4 | 1 |
5 | 1 | 123 | 0 | 5 | 0 |
6 | 0 | 345 | 1 | 6 | 0 |
7 | 0 | 123 | 0 | 7 | 0 |
8 | 1 | 456 | 0 | 8 | 0 |
9 | 0 | 567 | 0 | 9 | 0 |
Here, the Output Field Quality is determined by the worst of the Value field quality and the Quality field quality.
If the configuration is set to "Use Values of Fields" and the "Value for Good Quality" has been configured as "123"
Value field value | Value field quality | Quality field value | Quality field quality | Output field value | Output field quality |
2 | 1 | 123 | 1 | 2 | 1 |
3 | 0 | 123 | 1 | 3 | 0 |
4 | 1 | 234 | 1 | 4 | 0 |
5 | 1 | 123 | 0 | 5 | 0 |
6 | 0 | 345 | 1 | 6 | 0 |
7 | 0 | 123 | 0 | 7 | 0 |
8 | 1 | 456 | 0 | 8 | 0 |
9 | 0 | 567 | 0 | 9 | 0 |
Here, the Output field quality is determined by the worst of the Value field quality, the Quality field quality, and the quality that results from a comparison between the Quality field value and the configured Value for Good Quality.
If the configuration is set to "Use Values of Fields" and the "Value for Good Quality" has been configured as "Good"
Value field value | Value field quality | Quality field value | Quality field quality | Output field value | Output field quality |
2 | 1 | 123 | 1 | 2 | 0 |
3 | 0 | 123 | 1 | 3 | 0 |
4 | 1 | 234 | 1 | 4 | 0 |
5 | 1 | 123 | 0 | 5 | 0 |
6 | 0 | 345 | 1 | 6 | 0 |
7 | 0 | 123 | 0 | 7 | 0 |
8 | 1 | 456 | 0 | 8 | 0 |
9 | 0 | 567 | 0 | 9 | 0 |
2 | 1 | Good | 1 | 2 | 1 |
3 | 0 | Good | 1 | 3 | 0 |
4 | 1 | Bad | 1 | 4 | 0 |
5 | 1 | Good | 0 | 5 | 0 |
6 | 0 | Bad | 1 | 6 | 0 |
7 | 0 | Good | 0 | 7 | 0 |
8 | 1 | Bad | 0 | 8 | 0 |
9 | 0 | Bad | 0 | 9 | 0 |
2 | 1 | GOOD | 1 | 2 | 0 |
Here, the Output field quality is determined by the worst of the Value field quality, the Quality field quality, and the quality that results from a comparison between the Quality field value and the configured Value for Good Quality.
Notes: Quality field values on the input port that represent good quality need to match the Value for Good Quality configured on the block properties.
In the case of a non-numeric entry, the match is case sensitive. So if "Good" is configured as the Value for Good Quality, "123" does not match and "GOOD" does not match. Any Quality field value which does not match the configured Value for Good Quality is considered a designation of bad quality.
In the case of a numeric entry, the match is done numerically. So if "1" is configured as the Value for Good Quality, "1.0" and "1.00" match and are considered good quality , while "1X" and "Good" do not match and are considered bad quality.
Related topics: