View Issue Details

IDProjectCategoryView StatusLast Update
0007975Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2022-05-06 16:42
ReporterOctavia Stan Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version1.04.09.398 
Summary0007975: Aggregates Count and Average have problems in handling configuration.TreatUncertainAsBad = false
Description

The aggregates tests 003-02, 003-03, 004-02, 004-03 that set
configuration.TreatUncertainAsBad = false

They do not evaluate correctly for Count and Average. They seem to consider Uncertain values as bad even though they are instructed to treat them as Good

For example for interval: [2011-01-01T12:07:15.600Z - 2011-01-01T12:08:35.400Z]
server Value not equal to expected ctt value (index [2])
Server Value = Value = 8 status = UncertainDataSubNormal (0x40a40401) - Limit None source timestamp = 2011-01-01T12:07:15.600Z
CTT Value = Value = 7 status = UncertainDataSubNormal (0x40a40401) - Limit None source timestamp = 2011-01-01T12:07:15.600Z
Server Value = Value = 6 status = UncertainDataSubNormal (0x40a40401) - Limit None source timestamp = 2011-01-01T12:08:35.400Z
CTT Value = Value = 6 status = UncertainDataSubNormal (0x40a40401) - Limit None source timestamp = 2011-01-01T12:08:35.400Z

the data is:
2011-01-01T12:07:10Z, 2011-01-01T12:07:10Z, Good, Raw, Double, 231.5
2011-01-01T12:07:20Z, 2011-01-01T12:07:20Z, !!Good!!, Raw, Double, 607.1
2011-01-01T12:07:30Z, 2011-01-01T12:07:30Z, !!Good!!, Raw, Double, 354.42
2011-01-01T12:07:30Z, 2011-01-01T12:07:30Z, Good, Annotation, 2012-01-01T12:07:30Z, Engineer1, Scanner fixed
2011-01-01T12:07:40Z, 2011-01-01T12:07:40Z, !!Good!!, Raw, Double, 802.08
2011-01-01T12:07:50Z, 2011-01-01T12:07:50Z, !!Good!!, Raw, Double, 537.38
2011-01-01T12:07:50Z, 2011-01-01T12:07:50Z, Good, Annotation, 2012-01-01T12:07:50Z, Tehnician_1, Value flagged as questionable
2011-01-01T12:08:00Z, 2011-01-01T12:08:00Z, Uncertain, Raw, Double, 878.64
2011-01-01T12:08:10Z, 2011-01-01T12:08:10Z, !!Good!!, Raw, Double, 877.91
2011-01-01T12:08:20Z, 2011-01-01T12:08:20Z, !!Good!!, Raw, Double, 77.19
2011-01-01T12:08:30Z, 2011-01-01T12:08:30Z, !!Good!!, Raw, Double, 606.52
2011-01-01T12:08:40Z, 2011-01-01T12:08:40Z, Good, Raw, Double, 548.21

there are 7 Good statuses and one Uncertain that shall be considered Good therefore the value 8 provided by the server is correct

Additional Information

Issue found using SampleServer from Softing OPC UA .Net Standard SDK version 3.20

TagsNo tags attached.
Files Affected

Activities

Paul Hunkar

2022-05-05 12:44

administrator   ~0016670

The calculation are correct as currently implemented - the definition of the aggregate overrides the TreatUncertain flag

The count aggregate has the following definition:
"The Count Aggregate defined in Table 32 retrieves a count of all the raw values within an interval. If one or more raw values are non-Good, they are not included in the count, and the Aggregate StatusCode is determined using the StatusCode Calculation (see 5.4.3) for non-time based Aggregates. If no Good data exists for an interval, the count is zero"

  • This definition explicit excludes non-Good - The treat Uncertain as Bad does not apply.

The definition of Average is:
"The Average Aggregate defined in Table 16 adds up the values of all Good Raw data for each interval, and divides the sum by the number of Good values. If any non-Good values are ignored in the computation, the Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3). This Aggregate is not time based so the PercentGood/PercentBad applies to the number of values in the interval.

  • This definition explicit includes Only Good - The treat Uncertain as Bad does not apply.

Paul Hunkar

2022-05-06 16:42

administrator   ~0016683

reviewed in call agreed to no fix

Issue History

Date Modified Username Field Change
2022-05-05 12:10 Octavia Stan New Issue
2022-05-05 12:44 Paul Hunkar Assigned To => Paul Hunkar
2022-05-05 12:44 Paul Hunkar Status new => resolved
2022-05-05 12:44 Paul Hunkar Resolution open => no change required
2022-05-05 12:44 Paul Hunkar Note Added: 0016670
2022-05-06 16:42 Paul Hunkar Status resolved => closed
2022-05-06 16:42 Paul Hunkar Note Added: 0016683