Skip to content

BUG: handle equal thresholds in threshold_firm - #881

Open
whyvineet wants to merge 1 commit into
PyWavelets:mainfrom
whyvineet:fix-threshold-firm-equal-thresholds
Open

whyvineet wants to merge 1 commit into
PyWavelets:mainfrom
whyvineet:fix-threshold-firm-equal-thresholds

Conversation

@whyvineet

Copy link
Copy Markdown
Contributor

This PR contained an early-return guard in the case where value_low is equal to value_high, as when a firm threshold is applied this becomes a hard threshold. This is in order to avoid the 0/0 calculation which results in NaN.

Resolves #880

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

threshold_firm returns NaN at the threshold when value_low == value_high

1 participant