MRR score uses a "mean" instead of "min"
See original GitHub issueIf I’m not mistaken, MRR score is a mean of reciprocal rank
scores over a set of examples, where reciprocal rank
is given as 1 / (rank of the first positive item)
.
Currently implementation in spotlight
takes a mean over ranks of positive items. I think this is not correct. It is also inconsistent with lightfm
. It also makes it impossible to have mrr
score of 1
even with perfect model (even if positive items are ranked [1, 2, 3]
, taking the mean gives result lower than 1).
Can I send a PR to fix this?
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Mean Average Precision vs Mean Reciprocal Rank
Mean reciprocal rank (MRR) gives you a general measure of quality in these situations, but MRR only cares about the single highest-ranked ...
Read more >MRR vs MAP vs NDCG: Rank-Aware Evaluation Metrics And ...
MRR: Mean Reciprocal Rank; MAP: Mean Average Precision; NDCG: Normalized Discounted Cumulative Gain. Flat and “Rank-less” Evaluation Metrics.
Read more >Mean reciprocal rank - Wikipedia
The mean reciprocal rank is a statistic measure for evaluating any process that produces a list of possible responses to a sample of...
Read more >Compute Mean Reciprocal Rank (MRR) using Pandas
Mean Reciprocal Rank or MRR measures how far down the ranking the first relevant document is. If MRR is close to 1, it...
Read more >Natural Selection and Information Retrieval-Part 3-Mean ...
The Mean Reciprocal Rank or MRR is a relative score that calculates the average or mean of the inverse of the ranks at...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s not necessarily incorrect, but I can see why you might want to do it differently.
Could you make a PR that keeps the current code as default, but allows the alternative as an option? You could pass a
mode
argument that’s eithermean
ormin
.bump