View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000347510000-006: MappingsSpecpublic2016-07-20 08:222016-12-06 17:34
ReporterThomas Merk Assigned Torandyarmstrong  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0003475: Handling of NaN
Description

In 5.2.2.3 the statement was added:
... This means a NaN value for a Variable always produces a DataChange each time the SamplingInterval elapses.

I do not understand why NaN shall always produce DataChange notification.
Once notified is enough. Obviously the normal operators "==" / "<" / ">" cannot be used, some special handling has to be implemented.

What shall happen for SamplingRate 0?
Automatically fill up the monitored item queue?
Already queued values can be lost!

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0003630 closedMatthias Damm 10000-004: Services Handling of NaN 

Activities

Thomas Merk

2016-07-20 10:03

reporter   ~0007110

Last edited: 2016-07-21 12:19

Issue was meant for Specification Part 6.
Accidentially added here - plese move it.

Jim Luth

2016-08-30 16:01

administrator   ~0007162

Clarify that Sample Rate of 0 - means exception reporting so only the change of state in and out of NAN would cause the variable to report. Also allow similar "state change" testing for other Sample Rates.

randyarmstrong

2016-12-04 21:27

administrator   ~0007408

Added errata and update to Part 6 1.04 DRAFT 09.

randyarmstrong

2016-12-06 17:26

administrator   ~0007435

Discussed in call on 12/6.

Agree to remove all mention from sampling from Part 6 and add it to Part 4.
The text is here:

This means a NaN value for a Variable always produces a DataChange each time the SamplingInterval elapses if the standard logic is used. Servers shall check for NaN and only produce a DataChange when the value enters or leaves the NaN state.

Jim Luth

2016-12-06 17:27

administrator   ~0007436

Will require a 1.03 Errata.

Jim Luth

2016-12-06 17:29

administrator   ~0007437

Need to clone to Part 4

randyarmstrong

2016-12-06 17:30

administrator   ~0007444

Removed sampling requirement from Part in 1.04 DRAFT 10.

Jim Luth

2016-12-06 17:34

administrator   ~0007445

Agreed to changes in 1.04 Draft 10 and 1.03 Errata.

Issue History

Date Modified Username Field Change
2016-07-20 08:22 Thomas Merk New Issue
2016-07-20 10:03 Thomas Merk Note Added: 0007110
2016-07-21 12:19 Thomas Merk Note Edited: 0007110
2016-08-18 03:44 randyarmstrong Project NodeSets, XSDs and Generated Code => 10000-006: Mappings
2016-08-18 03:44 randyarmstrong Category Implementation Bug => Api Change
2016-08-30 16:01 Jim Luth Note Added: 0007162
2016-08-30 16:02 Jim Luth Category Api Change => Spec
2016-08-30 16:02 Jim Luth Target Version => 1.04
2016-08-30 16:02 Jim Luth Assigned To => randyarmstrong
2016-08-30 16:02 Jim Luth Status new => assigned
2016-12-04 21:27 randyarmstrong Note Added: 0007408
2016-12-04 21:27 randyarmstrong Status assigned => resolved
2016-12-04 21:27 randyarmstrong Resolution open => fixed
2016-12-06 17:26 randyarmstrong Note Added: 0007435
2016-12-06 17:26 randyarmstrong Status resolved => feedback
2016-12-06 17:26 randyarmstrong Resolution fixed => reopened
2016-12-06 17:27 Jim Luth Note Added: 0007436
2016-12-06 17:28 Jim Luth Assigned To randyarmstrong => Matthias Damm
2016-12-06 17:28 Jim Luth Status feedback => assigned
2016-12-06 17:29 Jim Luth Assigned To Matthias Damm => randyarmstrong
2016-12-06 17:29 Jim Luth Note Added: 0007437
2016-12-06 17:29 Jim Luth Issue cloned: 0003630
2016-12-06 17:29 Jim Luth Relationship added related to 0003630
2016-12-06 17:30 randyarmstrong Note Added: 0007444
2016-12-06 17:30 randyarmstrong Status assigned => resolved
2016-12-06 17:30 randyarmstrong Resolution reopened => fixed
2016-12-06 17:34 Jim Luth Note Added: 0007445
2016-12-06 17:34 Jim Luth Status resolved => closed
2016-12-06 17:34 Jim Luth Fixed in Version => 1.04