-
Notifications
You must be signed in to change notification settings - Fork 25.2k
RankEval doesn't take the requested number of results into consideration #29205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Pinging @elastic/es-search-aggs |
@cbuescher could you take a look? |
@paweloque thanks for your question, RankEval currently disregards the "size" parameter specified in queries on purpose. Instead, the maximum number of documents to be retrieved should be specified for all the current metrics in the "metric" section using the "k" parameter (named so because Precision is usually calculated for a window size k, so its named "Precicsion at k" (Prec@k). The window size should be specified in the metric because this way we can make sure that different queries don't use different "size" values to make the results comparable. I just realized this isn't mentioned in the documentation so far, so thanks for pointing this out. I will add proper usage examples for the "k" parameter to the docs. For now, you can use e.g.
For a result window of 20. |
@cbuescher Thanks for your reply and helping me! That perfectly makes sense. |
The rank_eval documentation was missing an explanation of the parameter `k` that controls the number of top hits that are used in the ranking evaluation. Closes elastic#29205
The rank_eval documentation was missing an explanation of the parameter `k` that controls the number of top hits that are used in the ranking evaluation. Closes #29205
The rank_eval documentation was missing an explanation of the parameter `k` that controls the number of top hits that are used in the ranking evaluation. Closes #29205
The rank_eval documentation was missing an explanation of the parameter `k` that controls the number of top hits that are used in the ranking evaluation. Closes #29205
RankEval takes page size into consideration:
Currently RankEval only looks at the first 10 results of a query. Even if the number of results is specified, rank eval only requests 10 results and compares them with the expected results.
RankEval should consider the specified 'size' for calculations of the search quality.
The text was updated successfully, but these errors were encountered: