1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
The BM25 Weighting Scheme
=========================
This is a technical note about the BM25 weighting scheme, which is the
default weighting scheme used by Xapian. Recent TREC tests have shown
BM25 to be the best of the known probabilistic weighting schemes. In
case you're wondering, the BM simply stands for "Best Match".
We'll follow the evolution from the "traditional" probabilistic
weighting scheme (as described in the `1976 Robertson/Sparck Jones
paper <http://www.soi.city.ac.uk/~ser/papers/RSJ76.pdf>`_) through to
BM25.
The Traditional Probabilistic Weighting Scheme
----------------------------------------------
In its most general form, the traditional probabilistic term weighting
function is:
.. math::
\frac{(k_3+1)q}{(k_3+q)}\text{ * }\frac{(k_1+1)f}{(k_1L+f)}\text{ * }\log\frac{(r+0.5)(N-n-R+r+0.5)}{(n-r+0.5)(R-r+0.5)}...(1)
where
* :math:`k_1`, :math:`k_3` are constants,
* q is the wqf, the within query frequency,
* f is the wdf, the within document frequency,
* n is the number of documents in the collection indexed by this term,
* N is the total number of documents in the collection,
* r is the number of relevant documents indexed by this term,
* R is the total number of relevant documents,
* L is the normalised document length (i.e. the length of this document
divided by the average length of documents in the collection).
The factors :math:`(k_3+1)` and :math:`(k_1+1)` are unnecessary here, but help
scale the weights, so the first component is 1 when :math:`q=1` etc. But
they are critical below when we add an extra item to the sum of term
weights.
BM11
----
Stephen Robertson's BM11 uses formula :math:`(1)` for the term weights, but
adds an extra item to the sum of term weights to give the overall
document score:
.. math::
k_2 n_q \frac{(1-L)}{(1+L)} ...(2)
where:
- :math:`n_q` is the number of terms in the query (the query length),
- :math:`k_2` is yet another constant.
Note that this extra item is zero when :math:`L=1`.
BM15
----
BM15 is BM11 with the :math:`k_1+f` in place of :math:`k_1L+f` in :math:`(1)`.
BM25
----
BM25 combines the B11 and B15 with a scaling factor, b, which turns BM15
into BM11 as it moves from 0 to 1:
.. math::
\frac{(k_3+1)q}{(k_3+q)}\text{ * }\frac{(k_1+1)f}{(K+f)}\text{ * }\log\frac{(r+0.5)(N-n-R+r+0.5)}{(n-r+0.5)(R-r+0.5)}...(3)
where:
:math:`K=k_1(bL+(1-b))`
BM25 originally introduced another constant, as a power to which f and K
are raised. However, Stephen remarks that powers other than 1 were *'not
helpful'*, and other tests confirm this, so Xapian's implementation of
BM25 ignores this.
:math:`(2)` and :math:`(3)` make up BM25, with which Stephen has had so much
recent success.
This does all seem somewhat ad-hoc, with so many unknown constants in
the formula. But note that with :math:`k_2=0` and :math:`b=1` we get the
traditional formula anyway.
The default parameter values Xapian uses are :math:`k_1=1`, :math:`k_2=0`,
:math:`k_3=1`,and :math:`b=0.5`. These are reasonable defaults, but the
optimum values will vary with both the documents being searched and the
type of queries, so you may be able to improve the effectiveness of your
search system by tuning the values of these parameters.
In Xapian, we also apply a floor to L (0.5 by default) which helps stop
tiny documents get ridiculously high weights. And the matcher wants the
extra item in the sum to be positive, so we add :math:`k_{2}n_{q}` (constant for a
given query) to :math:`(2)` to give:
.. math::
\frac{2k_2n_q}{(1+L)}...(4)
|
