Displaying 2 results from an estimated 2 matches for "param_k1".
Did you mean:
param_1
2010 Nov 01
1
floating-point issues with set_sort_by_relevance_then_value? (1.2.3, BM25 k1=0)
...nother). 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
trunk/xapian-core/weight/bm25weight.cc:166
This apparently prevents floating point precision issues in the last line of
get_sumpart() [which calculates termweight * wdf_double * 1 / wdf_double]. It
also speeds up my case...
2013 Jun 16
3
Backend for Lucene format indexes-How to get doclength
Hi, all:
I have wrote a demo patch for Backend for Lucene format indexes, Lucene
version is 3.6.2.
http://lucene.apache.org/core/3_6_2/fileformats.html
Now, this demo patch just support the basic features in Lucene. Compound
File(.cfs/.cfe)?term vector(.tvx/.tvd/.tvf)
delete document(.del) are not supported, skip list in .fdx is not supported
too
example/quest.cc is used to test this demo.