package.md

---

uid: Lucene.Net.Search.Similarities summary: *content

This package contains the various ranking models that can be used in Lucene. The abstract class xref:Lucene.Net.Search.Similarities.Similarity serves as the base for ranking functions. For searching, users can employ the models already implemented or create their own by extending one of the classes in this package.

Table Of Contents

1. Summary of the Ranking Methods 2. Changing the Similarity

Summary of the Ranking Methods

xref:Lucene.Net.Search.Similarities.DefaultSimilarity is the original Lucene scoring function. It is based on a highly optimized Vector Space Model. For more information, see xref:Lucene.Net.Search.Similarities.TFIDFSimilarity.

xref:Lucene.Net.Search.Similarities.BM25Similarity is an optimized implementation of the successful Okapi BM25 model.

xref:Lucene.Net.Search.Similarities.SimilarityBase provides a basic implementation of the Similarity contract and exposes a highly simplified interface, which makes it an ideal starting point for new ranking functions. Lucene ships the following methods built on xref:Lucene.Net.Search.Similarities.SimilarityBase: * Amati and Rijsbergen's {@linkplain org.apache.lucene.search.similarities.DFRSimilarity DFR} framework; * Clinchant and Gaussier's {@linkplain org.apache.lucene.search.similarities.IBSimilarity Information-based models} for IR; * The implementation of two {@linkplain org.apache.lucene.search.similarities.LMSimilarity language models} from Zhai and Lafferty's paper. Since xref:Lucene.Net.Search.Similarities.SimilarityBase is not optimized to the same extent as xref:Lucene.Net.Search.Similarities.DefaultSimilarity and xref:Lucene.Net.Search.Similarities.BM25Similarity, a difference in performance is to be expected when using the methods listed above. However, optimizations can always be implemented in subclasses; see below.

Changing Similarity

Chances are the available Similarities are sufficient for all your searching needs. However, in some applications it may be necessary to customize your Similarity implementation. For instance, some applications do not need to distinguish between shorter and longer documents (see a "fair" similarity).

To change xref:Lucene.Net.Search.Similarities.Similarity, one must do so for both indexing and searching, and the changes must happen before either of these actions take place. Although in theory there is nothing stopping you from changing mid-stream, it just isn't well-defined what is going to happen.

To make this change, implement your own xref:Lucene.Net.Search.Similarities.Similarity (likely you'll want to simply subclass an existing method, be it xref:Lucene.Net.Search.Similarities.DefaultSimilarity or a descendant of xref:Lucene.Net.Search.Similarities.SimilarityBase), and then register the new class by calling #setSimilarity(Similarity) before indexing and #setSimilarity(Similarity) before searching.

Extending {@linkplain org.apache.lucene.search.similarities.SimilarityBase}

The easiest way to quickly implement a new ranking method is to extend xref:Lucene.Net.Search.Similarities.SimilarityBase, which provides basic implementations for the low level . Subclasses are only required to implement the Float) and #toString() methods.

Another option is to extend one of the frameworks based on xref:Lucene.Net.Search.Similarities.SimilarityBase. These Similarities are implemented modularly, e.g. xref:Lucene.Net.Search.Similarities.DFRSimilarity delegates computation of the three parts of its formula to the classes xref:Lucene.Net.Search.Similarities.BasicModel, xref:Lucene.Net.Search.Similarities.AfterEffect and xref:Lucene.Net.Search.Similarities.Normalization. Instead of subclassing the Similarity, one can simply introduce a new basic model and tell xref:Lucene.Net.Search.Similarities.DFRSimilarity to use it.

Changing {@linkplain org.apache.lucene.search.similarities.DefaultSimilarity}

If you are interested in use cases for changing your similarity, see the Lucene users's mailing list at Overriding Similarity. In summary, here are a few use cases: 1.

The SweetSpotSimilarity in org.apache.lucene.misc gives small increases as the frequency increases a small amount and then greater increases when you hit the "sweet spot", i.e. where you think the frequency of terms is more significant.

2.

Overriding tf — In some applications, it doesn't matter what the score of a document is as long as a matching term occurs. In these cases people have overridden Similarity to return 1 from the tf() method.

3.

Changing Length Normalization — By overriding State), it is possible to discount how the length of a field contributes to a score. In xref:Lucene.Net.Search.Similarities.DefaultSimilarity, lengthNorm = 1 / (numTerms in field)^0.5, but if one changes this to be 1 / (numTerms in field), all fields will be treated "fairly".

In general, Chris Hostetter sums it up best in saying (from the Lucene users's mailing list):

[One would override the Similarity in] ... any situation where you know more about your data then just that it's "text" is a situation where it might make sense to to override your Similarity method.