There was a bug in my implementation of tf(float freq).
It was always 1, even when the frequency was 0.
This caused a discrepancy between the score and the debug info score - it
seems like in the debug all the dismax fields got score, while in the "real"
score fields with document frequency 0 were
: It seems like the debug information is using the custom similarity as it
: should - the bug isn't there.
: I see in the explain information the right tf value (I modified it to be 1
: in my custom similarity).
: The numbers in the explain seem to add up and make sense.
: Is it possible that the
It seems like the debug information is using the custom similarity as it
should - the bug isn't there.
I see in the explain information the right tf value (I modified it to be 1
in my custom similarity).
The numbers in the explain seem to add up and make sense.
Is it possible that the score itself
On Wed, Aug 27, 2008 at 9:38 AM, Yuri Jan <[EMAIL PROTECTED]> wrote:
> Actually, no...
> The score in the fl are 12.806475 and 10.386531 respectively, so the results
> according to that are sorted correctly.
> Is it just a problem with the debugQuery?
Looks like it... I guess the custom similarity
Actually, no...
The score in the fl are 12.806475 and 10.386531 respectively, so the results
according to that are sorted correctly.
Is it just a problem with the debugQuery?
On Wed, Aug 27, 2008 at 9:21 AM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 27, 2008 at 9:10 AM, Yuri Jan <[EM
On Wed, Aug 27, 2008 at 9:10 AM, Yuri Jan <[EMAIL PROTECTED]> wrote:
> I have encountered a weird problem in solr.
> In one of my queries (dismax, default sorting) I noticed that the results
> are not sorted by score (according to debugQuery).
>
> The first 150 results are tied (with score 12.80647
