Feat/nan policy signal processing 303 - #338
Open
solus161 wants to merge 2 commits into
Open
Conversation
Current entries are not touched. Additional entries check for non-finite, or non-nan values, and reject one that could spoil/corrupt filters' states.
…l_processing_303 # Conflicts: # crates/multicalc/tutorials/signal-processing.md
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What & why
Signal filters never panic on non-finite input (
NANorINFINITY) but returned value could be meaningless and filters' states could be corrupted, at worst, till filters' reset.What's new:
multicalc/signal_processing/mod.rsfor new message regarding this behavior;Issue State the NaN policy for
signal_processingand act on it #303Checklist
cargo test+cargo clippy --all-targetsclean locallyunwrap/expect/panicon library paths (typed errors instead)