Displaying 1 result from an estimated 1 matches for "r15140".
Did you mean:
15140
2010 Nov 01
1
floating-point issues with set_sort_by_relevance_then_value? (1.2.3, BM25 k1=0)
...en always seem to differ after the 14th/15th fractional digit and
only a small number of results is affected (3 out of ~16000 with a slightly
lower weight in one case, 4 out of ~70000 with a slightly higher one in
another). Platform is Debian Lenny 64bit, AMD Opteron CPUs, core-1.2.3 patched
to r15140 and using chert. This also happens with complex queries where groups
of results are expected to have identical weights.
FIX: I found a simple fix for this issue, at least for my test cases:
I added
if (param_k1 == 0) RETURN(termweight);
to the beginning of BM25Weight::get_sumpart in
trun...