-
Notifications
You must be signed in to change notification settings - Fork 486
Refactor fusion implementation to use ScoredDocs #2620
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
Working on it! |
Running times for end to end fusion after ScoredDocs refactoring from #2774 , with run_fusion_regression.py. Ranx cache increases speed quite a bit, so for fairness I cleared its cache before each run. Times measured in seconds.
|
Thanks @lilyjge ! Two questions:
|
|
Table including running times of previous implementation before refactoring:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current implementation of fusion is built around
TrecRun
, e.g., https://github.com/castorini/anserini/blob/master/src/main/java/io/anserini/fusion/TrecRunFuser.javaBut we already have
ScoredDocs
:https://github.com/castorini/anserini/blob/master/src/main/java/io/anserini/search/ScoredDocs.java
Should we refactor our implementation to use
ScoredDocs
?Potential cons:
The text was updated successfully, but these errors were encountered: