Skip to content

why the value of k is fixed to 60? #9

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

Open
kranthi419 opened this issue Sep 26, 2024 · 1 comment
Open

why the value of k is fixed to 60? #9

kranthi419 opened this issue Sep 26, 2024 · 1 comment

Comments

@kranthi419
Copy link

why the value of k is fixed to 60? in RRF.

@Raudaschl
Copy link
Owner

In all honestly, it felt like the best default value for the use cases I tested.
In many implementations and research studies involving RRF, a k value around 60 has been commonly used.
One advance of setting it to 60 reduces the weight difference between higher and lower-ranked documents, leading to a more inclusive fusion where more documents from different queries contribute to the final ranking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants