View Issue Details

IDProjectCategoryView StatusLast Update
000306710000-013: AggregatesSpecpublic2015-07-20 16:56
Reporteruser328Assigned ToRod Stein  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.02 
Target Version1.03Fixed in Version1.03 
Summary0003067: Count Aggregate: When there is no good data in the interval, value is null instead of zero
Description

Eg: (Appendix A.19, Part 13) Historian 1, Time Slice: 12:00:32.000, Count Value in the table is null.
Historian1
Timestamp value StatusCode
12:00:30 30 Raw, Good
12:00:40 40 Raw, Bad
12:00:50 50 Raw, Good

Between the Interval 32 to 48 there is only one value(40) that is Bad.

There are 2 statements in the Spec (Part 12: Section 5.4.4.19) that needs clarification:

  1. If one or more raw values are non-good, they are not included in the count.
  2. If no good data exists for an interval, the count is zero.

When you have only one value and when you do not include the value, why is the count null? Shouldn't the count be zero?

Count retrieves the number of raw values over the interval. How can the count be null when you are looking for the number of raw values?

TagsNo tags attached.
Commit Version

Activities

Rod Stein

2015-07-15 21:58

developer   ~0006235

Fixed in 1.03.07
A zero has been added in Annex A.19 where it had been incorrectly omitted.

Jim Luth

2015-07-20 16:56

administrator   ~0006240

Fixed in final release.

Issue History

Date Modified Username Field Change
2015-05-14 21:48 user328 New Issue
2015-05-14 21:48 user328 Status new => assigned
2015-05-14 21:48 user328 Assigned To => Nathan Pocock
2015-05-26 16:40 Jim Luth Assigned To Nathan Pocock => Rod Stein
2015-07-15 21:58 Rod Stein Note Added: 0006235
2015-07-15 21:58 Rod Stein Status assigned => resolved
2015-07-15 21:58 Rod Stein Fixed in Version => 1.03
2015-07-15 21:58 Rod Stein Resolution open => fixed
2015-07-20 16:56 Jim Luth Note Added: 0006240
2015-07-20 16:56 Jim Luth Status resolved => closed