Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added Digital Compression #414
base: master
Are you sure you want to change the base?
Added Digital Compression #414
Changes from all commits
a0caa85
71ff3a2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if rounding errors could potentially introduce additional data points between state changes. Do you think it might cause problems downstream if
points.Count > m_samples
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
m_samples
get's removed from the blob so I am not sure that even matters.By definition we assume these "Digitals" are evenly sampled so it will generate an evenly sampled flat line until it hits a state change. In theory it is possible that we Loose some points in between or generate extra ones, but since it's a flat line anyway I am not too concerned about that.
Occasionally we may compress a latched analog this way, which I suppose could be an issue, but I believe we already assume fixed sampling rate in a few places when doing math so not sure that really matters either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Off the top of my head, my main concern would be this.
openXDA/Source/Libraries/FaultData/DataAnalysis/DataGroup.cs
Lines 323 to 331 in f0ccd33
If the actual number of decoded data points doesn't match
DataGroup.m_samples
, then theDataGroup.Add()
method will fail to even include the digital series in theDataGroup
. This is called directly byDataGroup.FromData()
so the decoded data would just be silently dropped on the floor, and we would be wondering why it's not getting returned to the visualization.Also, I suppose I'm assuming that there will be a follow-up PR that includes changes to
DataGroup.FromData()
?