Bug #1796
Suspicious LogRange behaviour for very small min and max
| Status: | Closed | Start date: | 2017-02-23 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Chris Cannam | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
How should LogRange::mapRange behave when either min or max is non-zero but smaller than the provided threshold?
As it stands, we will get a "wider" range for mapRange(1e-20, 1) than we will for (0, 1), which doesn't seem to make a lot of sense. We should add some tests for these and check what it really should do for proper behaviour.
History
#1
Updated by Chris Cannam over 7 years ago
I've persuaded myself that the current behaviour is OK, thinking of the threshold value as a sort of substitute for the singularity at 0 rather than an actual threshold. I've added some unit tests that document and ratify this situation.
#2
Updated by Chris Cannam over 7 years ago
- Status changed from New to Resolved
#3
Updated by Chris Cannam over 7 years ago
- Status changed from Resolved to Closed