| commit | 0b06844f4d6e6a9a3b42438493c52d248397011d | |
| author | ashokvardhan <ashokvardhan@chromium.org> | |
| Fri, 20 Feb 2015 19:28:16 +0000 (20 11:28 -0800) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Fri, 20 Feb 2015 19:29:09 +0000 (20 19:29 +0000) | ||
| tree | b484ad1c8e59e1e57a19231a9f32fa2b5b211ce5 | treesnapshot (tar.gz zip) |
| parent | ca57a51bbb794575650b9e1b071b68aeae3d5e87 | commitdiff |
Adding knobs on HQP provider. Having an option of experimenting with topicality score and changing final relevance score ranges from omnibox bundled params.
1. Option to suppress the URLs with topicality score lower than the given threshold. This way we can control the URLs with high popularity and low topicality scoring.
2. Changing the final-relevance score buckets to linearly interpolate with in-certain ranges. This will help to control the score ranges.
With above options one can set the bundled params. Ex:
HQPExperimentalScoringEnabled="true"
HQPExperimentalScoringTopicalityThreshold="0.8"
HQPExperimentalScoringBuckets="0.0:400,1.5:600,12.0:1300,20.0:1399"
More details can be found in the bug: crbug/306198
BUG=306198
TEST=ScoredHistoryMatchTest.GetFinalRelevancyScore
Review URL: https://codereview.chromium.org/905023003
Cr-Commit-Position: refs/heads/master@{#317369}
1. Option to suppress the URLs with topicality score lower than the given threshold. This way we can control the URLs with high popularity and low topicality scoring.
2. Changing the final-relevance score buckets to linearly interpolate with in-certain ranges. This will help to control the score ranges.
With above options one can set the bundled params. Ex:
HQPExperimentalScoringEnabled="true"
HQPExperimentalScoringTopicalityThreshold="0.8"
HQPExperimentalScoringBuckets="0.0:400,1.5:600,12.0:1300,20.0:1399"
More details can be found in the bug: crbug/306198
BUG=306198
TEST=ScoredHistoryMatchTest.GetFinalRelevancyScore
Review URL: https://codereview.chromium.org/905023003
Cr-Commit-Position: refs/heads/master@{#317369}