-
Notifications
You must be signed in to change notification settings - Fork 2.2k
feat: ranking evaluate driver may need more than one field #1953
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1953 +/- ##
==========================================
+ Coverage 84.71% 86.60% +1.88%
==========================================
Files 148 148
Lines 7094 7106 +12
==========================================
+ Hits 6010 6154 +144
+ Misses 1084 952 -132
Continue to review full report at Codecov.
|
9b84d34
to
a86e78c
Compare
Latency summaryCurrent PR yields:
Breakdown
Backed by latency-tracking. Further commits will update this comment. |
…luate-multiple-fields
2dcbb8e
to
4508080
Compare
…luate-multiple-fields
9f5af3f
to
915fdc0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
…luate-multiple-fields
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM👍
Changes introduced
Motivation of this PR comes from the realization that
NDCGEvaluator
is not applicable, since more than one field may be needed for it.RankingEvaluateDriver
now can access multiple fields of thematches
of bothDocument
andGroundTruth
.For instance, for NDCGEvaluator, we may need:
fields = ('tags__id', 'score__value')
So that the NDCGEvaluator would get
desired = (id, relevance), (id, relevance)
actual = (id, score), (id, score) so that it can be properly computed