View Issue Details

IDProjectCategoryView StatusLast Update
000659410000-011: Historical AccessSpecpublic2022-09-22 20:31
ReporterThomas Reuther Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformSpecificationOSUnified ArchitectureOS VersionPart 11
Fixed in Version1.05.03 RC1 
Summary0006594: "A.2 Determining the first historical data point" conflicts with "6.4.3.2 Read raw functionality"
Description

Today I was using our Historian server and wanted to get the first (and maybe last) data point in history. The spec part 11 v 1.04 says:

"A.2 Determining the first historical data point

[...] one of the following queries using ReadRawModifiedDetails parameters:
returnBounds=false
numValuesPerNode=1
startTime=DateTime.MinValue+1 second
endTime= DateTime.MinValue
Or:
returnBounds=false
numValuesPerNode=1
startTime=DateTime.MinValue
endTime= DateTime.MaxValue"

The first method returns the first data point while the second method actually returns the last value.

I was blaming the developer of the server but he reponses with "6.4.3.2 Read raw functionality

If [...] endTime and numValuesPerNode alone are specified then the data will be returned in reverse order."

That means: if start time is not sepcified (= DateTime.MinValue in second method) then the reverse order comes into play. Together with numValuesPerNode = 1 it will return the last value in history.

Additional Information

It would be enough the rename the second method to: "A.2 Determining the last historical data point"

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0003632 closedPaul Hunkar Part 11 - Determining the first historical data point - specification error 

Activities

Paul Hunkar

2022-08-04 06:27

developer   ~0017260

Updated text as suggested - - the second example is for how to find the most recent historical value.

Jim Luth

2022-09-22 20:31

administrator   ~0017816

Agreed to changes edited in F2F meeting.

Issue History

Date Modified Username Field Change
2021-03-10 14:24 Thomas Reuther New Issue
2021-04-13 16:49 Jim Luth Assigned To => Rod Stein
2021-04-13 16:49 Jim Luth Status new => assigned
2022-08-04 06:27 Paul Hunkar Assigned To Rod Stein => Paul Hunkar
2022-08-04 06:27 Paul Hunkar Status assigned => resolved
2022-08-04 06:27 Paul Hunkar Resolution open => fixed
2022-08-04 06:27 Paul Hunkar Fixed in Version => 1.05.03 RC1
2022-08-04 06:27 Paul Hunkar Note Added: 0017260
2022-08-05 06:26 Paul Hunkar Relationship added related to 0003632
2022-09-22 20:31 Jim Luth Status resolved => closed
2022-09-22 20:31 Jim Luth Note Added: 0017816