Remove hit weight experiment

Remove hit weight experiment.

Results of the experiment show that higher hit weights yield greater coverage, but at the expense of accuracy. The decreased accuracy outweighs the increased coverage.

BUG=111069
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=139086

[cbentzel, 2012-05-25 16:34:34]

LGTM

http://codereview.chromium.org/10453013/diff/7001/chrome/browser/predictors/a...
File chrome/browser/predictors/autocomplete_action_predictor.cc (left):

http://codereview.chromium.org/10453013/diff/7001/chrome/browser/predictors/a...
chrome/browser/predictors/autocomplete_action_predictor.cc:245:
StringPrintf("Prerender.OmniboxNavigationsCouldPrerender_%.1f%s",
Do you plan to obsolete these in histograms.xml?

http://codereview.chromium.org/10453013/diff/7001/chrome/browser/predictors/a...
File chrome/browser/predictors/autocomplete_action_predictor.cc (right):

http://codereview.chromium.org/10453013/diff/7001/chrome/browser/predictors/a...
chrome/browser/predictors/autocomplete_action_predictor.cc:424: const double
number_of_hits = static_cast<double>(value.number_of_hits);
Do you actually need the explicit cast here? Mantissa of double seems like
enough to capture int - although I suppose there is some loss-of-precision if
int is 64 bit on a particular platform.

Either way, I think it's fine, just curious.

[commit-bot: I haz the power, 2012-05-25 16:54:11]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/dominich@chromium.org/10453013/7001

[dominich, 2012-05-25 16:54:56]

https://chromiumcodereview.appspot.com/10453013/diff/7001/chrome/browser/pred...
File chrome/browser/predictors/autocomplete_action_predictor.cc (left):

https://chromiumcodereview.appspot.com/10453013/diff/7001/chrome/browser/pred...
chrome/browser/predictors/autocomplete_action_predictor.cc:245:
StringPrintf("Prerender.OmniboxNavigationsCouldPrerender_%.1f%s",
On 2012/05/25 16:34:34, cbentzel wrote:
> Do you plan to obsolete these in histograms.xml?

Actually I'll remove them if they're even there. They never worked in the UMA UI
as they rely on two field trials which it doesn't support.

https://chromiumcodereview.appspot.com/10453013/diff/7001/chrome/browser/pred...
File chrome/browser/predictors/autocomplete_action_predictor.cc (right):

https://chromiumcodereview.appspot.com/10453013/diff/7001/chrome/browser/pred...
chrome/browser/predictors/autocomplete_action_predictor.cc:424: const double
number_of_hits = static_cast<double>(value.number_of_hits);
On 2012/05/25 16:34:34, cbentzel wrote:
> Do you actually need the explicit cast here? Mantissa of double seems like
> enough to capture int - although I suppose there is some loss-of-precision if
> int is 64 bit on a particular platform.
> 
> Either way, I think it's fine, just curious.

A preference to be explicit.

const double a = some_int;

could be a mistake. I like to eliminate doubt for the reader.

[commit-bot: I haz the power, 2012-05-25 17:00:12]

Try job failure for 10453013-7001 on linux_rel for step "update".
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_rel&...

Step "update" is always a major failure.
Look at the try server FAQ for more details.

[commit-bot: I haz the power, 2012-05-25 17:09:01]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/dominich@chromium.org/10453013/9

[commit-bot: I haz the power, 2012-05-25 18:50:38]

Change committed as 139086