: Can anyone say why this is useful and what's wrong about raw scores?
in my opinion: it's not useful at all, and there is nothing wrong with
raw scores, but some people like having scores that are bounded in a
finite range, so Hits provides that.
-Hoss
-
Erick Erickson wrote:
I wound up using a TopDocs instead, which has a getMaxScore that
I was able to use to normalize scores to between 0 and 1. In my case
I was collapsing the results into quintiles, so I threw them all
back into a FieldSortedHitQueue to get them sorted by secondary
criteria onc
I wound up using a TopDocs instead, which has a getMaxScore that
I was able to use to normalize scores to between 0 and 1. In my case
I was collapsing the results into quintiles, so I threw them all
back into a FieldSortedHitQueue to get them sorted by secondary
criteria once the scores were all o
Hits will normalise scores >0<=1, but I'm using HitCollector and haven't worked
out how to normalise those scores.
From what I can see, the scores are just multiplied by a factor to bring the
top score down to 1. Is this right or is there something more to it.
Do I need to normalise scores a