-
Notifications
You must be signed in to change notification settings - Fork 4
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
Develop #117
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e calls to put() during a single step (rel to #115).
…ly in the PEAK_MIN and PEAK_MAX cases.
PeakDetector in apex mode (PEAK_MAX/PEAK_MIN) was triggering at the moment of crossing the triggerThreshold (behaving like crossing mode) instead of triggering at fallback threshold. Fixed by adding if (_crossed) condition before allowing "_peakValue" to take on the value of the next "value"
…tion by resetting variables.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PeakDetector was not triggering correctly when in apex mode (PEAK_MAX, PEAK_MIN).
It would trigger at the moment of crossing the triggerThreshold (behaving like crossing mode) rather than triggering when falling back beyond the fallbackTolerance.
The issue was due to _peakValue being reset to -FLT_MIN when fallingBack was true, but then immediately taking on the value of the next value at the next step :
(because value is always higher than -FLT_MIN, so isMax is true!)
Issue was fixed by adding if (_crossing) conditional to ensure that _peakValue will only be updated again after the next crossing.