View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003067 | 10000-013: Aggregates | Spec | public | 2015-05-14 21:48 | 2015-07-20 16:56 |
Reporter | Assigned To | Rod Stein | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.02 | ||||
Target Version | 1.03 | Fixed in Version | 1.03 | ||
Summary | 0003067: 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. 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:
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? | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2015-05-14 21:48 |
|
New Issue | |
2015-05-14 21:48 |
|
Status | new => assigned |
2015-05-14 21:48 |
|
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 |