Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Check if cover scoredist is score before treating it like its an encoded score #907
Currently, if a cover's scoredist is <7, the scoredist gets treated as if it were the same as the score, which gets encoded as a value between 1 and 7 on a log scale. The scoredist is then "decoded" based on the scorefactor of the index. The scoredist is the same as the score in many cases, for example, when there is no proximity option.
It's possible for a scoredist that does take distance from a proximity point into account as part of it's scoredist to have a scoredist of <7. When it's treated the same as the score, it often gets "decoded" to end up as 1. This hides relevant differences in features that have low scores but some differentiation in distance from a point.
This is an attempt to preserve the original scoredist if the scoredist is not equal to the score, instead of guessing based on whether the scoredist is <7.
Summary of Changes