zoekt/testdata/golden/TestReadSearch/ at b5a5fdc86e830d80b2be3154bb9f896fd20c3e3e · boltless.me/zoekt · Tangled

boltless.me / zoekt

0

fork of https://github.com/sourcegraph/zoekt

0

zoekt / testdata / golden / TestReadSearch /

at b5a5fdc86e830d80b2be3154bb9f896fd20c3e3e 5 files

Stefan Hengl scoring: score files based on absolute number of atoms (#542) 3y ago

ctagsrepo_v16.00000.golden

scoring: score files based on absolute number of atoms (#542) This changes how atom-score is calculated to better reflect the complexity of the result or the user's intent. Currently, the atom-score is the ratio "atomMatchCount/totalAtomAcount". However, "totalAtomAcount" is based on the pruned match-tree which may be very different from the user query. For example, a match-tree for the query "foo or bar" is pruned to (a matchtree representing the query) "foo" if the shard doesn't contain the trigram "bar". In an extreme case, a query like "foo or bar or bas or qux" can receive the maximum atom-score if a repo just contains matches for foo. Assuming that the score of a match should reflect how close a match is to the user's intent, we should rather base the atom-score on the original unpruned match-tree. However, the original match-tree is already based on a simplified query, (see "d.simplify(q)" in eval.go) Hence I change the scoring function for atom-score to be based on the absolute count and to assymptotically approach scoreFactorAtomMatch. This also makes the score more comparable across shards.

3 years ago

ctagsrepo_v17.00000.golden

scoring: score files based on absolute number of atoms (#542) This changes how atom-score is calculated to better reflect the complexity of the result or the user's intent. Currently, the atom-score is the ratio "atomMatchCount/totalAtomAcount". However, "totalAtomAcount" is based on the pruned match-tree which may be very different from the user query. For example, a match-tree for the query "foo or bar" is pruned to (a matchtree representing the query) "foo" if the shard doesn't contain the trigram "bar". In an extreme case, a query like "foo or bar or bas or qux" can receive the maximum atom-score if a repo just contains matches for foo. Assuming that the score of a match should reflect how close a match is to the user's intent, we should rather base the atom-score on the original unpruned match-tree. However, the original match-tree is already based on a simplified query, (see "d.simplify(q)" in eval.go) Hence I change the scoring function for atom-score to be based on the absolute count and to assymptotically approach scoreFactorAtomMatch. This also makes the score more comparable across shards.

3 years ago

repo17_v17.00000.golden

scoring: score files based on absolute number of atoms (#542) This changes how atom-score is calculated to better reflect the complexity of the result or the user's intent. Currently, the atom-score is the ratio "atomMatchCount/totalAtomAcount". However, "totalAtomAcount" is based on the pruned match-tree which may be very different from the user query. For example, a match-tree for the query "foo or bar" is pruned to (a matchtree representing the query) "foo" if the shard doesn't contain the trigram "bar". In an extreme case, a query like "foo or bar or bas or qux" can receive the maximum atom-score if a repo just contains matches for foo. Assuming that the score of a match should reflect how close a match is to the user's intent, we should rather base the atom-score on the original unpruned match-tree. However, the original match-tree is already based on a simplified query, (see "d.simplify(q)" in eval.go) Hence I change the scoring function for atom-score to be based on the absolute count and to assymptotically approach scoreFactorAtomMatch. This also makes the score more comparable across shards.

3 years ago

repo2_v16.00000.golden

scoring: score files based on absolute number of atoms (#542) This changes how atom-score is calculated to better reflect the complexity of the result or the user's intent. Currently, the atom-score is the ratio "atomMatchCount/totalAtomAcount". However, "totalAtomAcount" is based on the pruned match-tree which may be very different from the user query. For example, a match-tree for the query "foo or bar" is pruned to (a matchtree representing the query) "foo" if the shard doesn't contain the trigram "bar". In an extreme case, a query like "foo or bar or bas or qux" can receive the maximum atom-score if a repo just contains matches for foo. Assuming that the score of a match should reflect how close a match is to the user's intent, we should rather base the atom-score on the original unpruned match-tree. However, the original match-tree is already based on a simplified query, (see "d.simplify(q)" in eval.go) Hence I change the scoring function for atom-score to be based on the absolute count and to assymptotically approach scoreFactorAtomMatch. This also makes the score more comparable across shards.

3 years ago

repo_v16.00000.golden

scoring: score files based on absolute number of atoms (#542) This changes how atom-score is calculated to better reflect the complexity of the result or the user's intent. Currently, the atom-score is the ratio "atomMatchCount/totalAtomAcount". However, "totalAtomAcount" is based on the pruned match-tree which may be very different from the user query. For example, a match-tree for the query "foo or bar" is pruned to (a matchtree representing the query) "foo" if the shard doesn't contain the trigram "bar". In an extreme case, a query like "foo or bar or bas or qux" can receive the maximum atom-score if a repo just contains matches for foo. Assuming that the score of a match should reflect how close a match is to the user's intent, we should rather base the atom-score on the original unpruned match-tree. However, the original match-tree is already based on a simplified query, (see "d.simplify(q)" in eval.go) Hence I change the scoring function for atom-score to be based on the absolute count and to assymptotically approach scoreFactorAtomMatch. This also makes the score more comparable across shards.

3 years ago