[launcher-result-normalizer] Integrating into zero state providers and...
[launcher-result-normalizer] Integrating into zero state providers and experimenting with normalizers Scores from providers have different distributions and ranges, this makes them difficult to compare. Here we have implemented a basic way to normalize ChromeSearchResults by subtracting the mean of the learned distribution. After experimentation with more complex normalization methods we will then update this normalization method. Further details at go/cros-launcher-normalization In this CL we have integrated the normalizer into the omnibox provider, drive zero state provider and zero state file provider Bug: 1156930 Change-Id: Ic232efb0b31eb712959b6d386b39366ff4c38a54 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2601357Reviewed-by:Tony Yeoman <tby@chromium.org> Reviewed-by:
Rachel Wong <wrong@chromium.org> Commit-Queue: Ada Fang <adafang@google.com> Cr-Commit-Position: refs/heads/master@{#841361}
Showing
Please register or sign in to comment