-
Notifications
You must be signed in to change notification settings - Fork 87
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
Boost symbol matches in BM25 #876
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -588,6 +588,22 @@ func findMaxOverlappingSection(secs []DocumentSection, off, sz uint32) (uint32, | |
return uint32(j), ol1 > 0 | ||
} | ||
|
||
func (p *contentProvider) matchesSymbol(cm *candidateMatch) bool { | ||
if cm.fileName { | ||
return false | ||
} | ||
|
||
// Check if this candidate came from a symbol matchTree | ||
if cm.symbol { | ||
return true | ||
} | ||
|
||
// Check if it overlaps with a symbol. | ||
secs := p.docSections() | ||
_, ok := findMaxOverlappingSection(secs, cm.byteOffset, cm.byteMatchSz) | ||
return ok | ||
} | ||
|
||
func (p *contentProvider) findSymbol(cm *candidateMatch) (DocumentSection, *Symbol, bool) { | ||
if cm.fileName { | ||
return DocumentSection{}, nil, false | ||
|
@@ -619,6 +635,29 @@ func (p *contentProvider) findSymbol(cm *candidateMatch) (DocumentSection, *Symb | |
return sec, si, true | ||
} | ||
|
||
// calculateTermFrequency computes the term frequency for the file match. | ||
// Notes: | ||
// * Filename matches count more than content matches. This mimics a common text search strategy to 'boost' matches on document titles. | ||
// * Symbol matches also count more than content matches, to reward matches on symbol definitions. | ||
func (p *contentProvider) calculateTermFrequency(cands []*candidateMatch, df termDocumentFrequency) map[string]int { | ||
// Treat each candidate match as a term and compute the frequencies. For now, ignore case | ||
// sensitivity and treat filenames and symbols the same as content. | ||
termFreqs := map[string]int{} | ||
for _, m := range cands { | ||
term := string(m.substrLowered) | ||
if m.fileName || p.matchesSymbol(m) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Personally, this is still on the right side of the "black magic" line :) I didn't tune any parameters, just threw in this check and it works well across two eval datasets. |
||
termFreqs[term] += 5 | ||
} else { | ||
termFreqs[term]++ | ||
} | ||
} | ||
|
||
for term := range termFreqs { | ||
df[term] += 1 | ||
} | ||
return termFreqs | ||
} | ||
|
||
func (p *contentProvider) candidateMatchScore(ms []*candidateMatch, language string, debug bool) (float64, string, []*Symbol) { | ||
type debugScore struct { | ||
what string | ||
|
This file contains 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
This file contains 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
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
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.
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.
We are duplicating some checks, since we run both
calculateTermFrequency
for the overall file score, pluscandidateMatchScore
for the individual chunk scores. It would be good to unify these, but I didn't want to embark on a big refactor in this PR.