Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add recall metric #138

Open
KShivendu opened this issue May 10, 2024 · 3 comments
Open

Add recall metric #138

KShivendu opened this issue May 10, 2024 · 3 comments
Labels
good first issue Good for newcomers

Comments

@KShivendu
Copy link
Member

KShivendu commented May 10, 2024 •
edited
Loading

We calculate precision but for higher values of K, it's more valuable to optimize for recall. Therefore, we should measure it.
@KShivendu KShivendu added the good first issue Good for newcomers label May 10, 2024
@ashishu23
Copy link

hi @KShivendu , I am interested in solving this. Just wanted to confirm if the issue still persists?
If not , then can I work on this?

@LukasWestholt
Copy link

What exactly is the difference between recall and precision?

@LukasWestholt
Copy link

Ok i see here: https://en.wikipedia.org/wiki/Precision_and_recall

LukasWestholt added a commit to LukasWestholt/qdrant-benchmark-fork that referenced this issue Oct 4, 2024
@LukasWestholt
add recall metric qdrant#138
9016ecb
@LukasWestholt LukasWestholt mentioned this issue Oct 4, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@LukasWestholt @KShivendu @ashishu23