Lines Matching refs:relevance
611 // History returns results sorted for us. We force the relevance to decrease
613 // match having a relevance greater than the previous, but they might be
614 // equal. If we didn't force the relevance to decrease and we ended up in a
615 // situation where the relevance was equal, then which was shown first would
618 // relevance.
639 int relevance = CalculateRelevanceForHistory(i->time, term_looks_like_url,
641 if (i != results.begin() && relevance >= last_relevance)
642 relevance = last_relevance - 1;
643 last_relevance = relevance;
646 relevance,
694 // The relevance of past searches falls off over time. There are two distinct
698 // relevance of a search 15 minutes ago is discounted about 50 points, while
699 // the relevance of a search two weeks ago is discounted about 450 points.
717 // Don't let scores go below 0. Negative relevance scores are meaningful in
744 // TODO(kochi): http://b/784900 Use relevance score from the NavSuggest
752 int relevance,
758 AutocompleteMatch match(this, relevance, false, type);
840 // NOTE: We purposefully do a direct relevance comparison here instead of
846 // result even if the precision of our relevance score is too low to
848 if (!i.second && (match.relevance > i.first->second.relevance))
854 int relevance,
858 AutocompleteMatch match(this, relevance, false,
