[Feature] Implement HitRate metric for RecSys#3530
Merged
vfdev-5 merged 7 commits intopytorch:masterfrom Feb 20, 2026
Merged
Conversation
vfdev-5
reviewed
Feb 18, 2026
Contributor
Author
|
next step after hitrate could be recall@top_k which has similar logic but instead of binary hits per user, it calculates fraction/percentage of hits per user. |
Collaborator
We already have Precision/Recall metrics, so if we could add top_k wrapper or arg to the existing metrics, it would be better than introducing new metric class |
Contributor
Author
|
yes that sounds better!! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements Hitrate metric as proposed in #2631
Description:
Implements hitrate metric for recommendation systems. The hitrate is calculated for the
top-klist provided by the user and returns a list ofhitratein sorted order. A "hit" is considered when atleast one of our model's top-k predictions for recommedations is actually correct.Test cases and docstrings are also implemented.
I followed the code structure of other metrics like
loss,KL divergence, etc.Reference : https://github.com/catalyst-team/catalyst/blob/master/catalyst/metrics/functional/_hitrate.py
Also i used Gemini initially for understanding how recommendation systems and its evaluation/metrics work, and for understanding disrtibuted tests.
Check list: