search for: set_sort_by_relevance_then_value

I am using BM25 with k1=0 and min_normlen=1 to get weights unaffected by document length and term frequency in the document (min_normlen=1 isn't necessary I guess) and am expecting single-term weights to be identical for all matches. I have added a document value to steer such general search queries and it works fine, except that for some search terms, I get results like:

Dear xapian developers, I've added a function named "set_sort_by_relevance_then_value()". Now I want to rebuild python-bindings to include the new function and test if it works or not. I guess there is a way to rebuild all of the binding modules include the new function. I am not used to SWIG. I want to which files I need to change and how to build it. Thanks! Sungsoo Kim...

...e and time with set_sort_by_value_then_relevance(4) and to only 100 if I use set_sort_by_relevance(). The first figure is the correct one. Note that the MSet is obtained with Enquire::get_mset(0, 100, 101), so that probably explains where the 100 comes from. The estimate will also be correct with set_sort_by_relevance_then_value(4). If I am not mistaken, a similar problem was reported, and apparently fixed, back in September : http://comments.gmane.org/gmane.comp.search.xapian.general/5110 I am using 1.0.3. Fabrice

Posting recent offline discussion... On Fri, Apr 27, 2012 at 10:55 AM, Marius Tibeica <mtibeica at gmail.com> wrote: > Hi Liam, > > I've added the Enquire class and designed a query spec structured as a JS > object. Hope you like it :) > I'll probably be off a few days (there is a national holiday Tuesday which > means i have a long weekend :D) but maybe I'll