Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of erickerickson@gmail.com
 designates 209.85.223.200 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=Yej3Pt115dYJPw3cuzXXOU3TGTqKoQXDyLC7OQdUEna7G1YXa0wkdmP0GnFBeakc32
         TV+H12k7SNaUsBI70py3pKJJjlEk/v+SZfQR5EIlJpAZ18LQUc4JOM82ocD4NAcO0gyj
         3JKh+cR2ljO1fAv37tstTiu1GDGqO8RsSBYp8=
MIME-Version: 1.0
In-Reply-To: <4d19a3630908220701g5c6441aw42ed18cfdd08b1dd@mail.gmail.com>
References: <23293723.post@talk.nabble.com>
	 <Pine.LNX.4.64.0905011433110.17125@radix.cryptio.net>
	 <25093931.post@talk.nabble.com>
	 <4d19a3630908220701g5c6441aw42ed18cfdd08b1dd@mail.gmail.com>
Date: Mon, 24 Aug 2009 10:05:13 -0400
Message-ID: <359a92830908240705l6dd1c7c5i72bc0017bd138695@mail.gmail.com>
Subject: Re: How to het the score in percentage
From: Erick Erickson <erickerickson@gmail.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=002215048e77ed48150471e3b435

--002215048e77ed48150471e3b435
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I'm not saying that calculating percentages is a bad thing *within a
query*.Your
absolutely right, users want some clue about how "good" a match
various items are.

But trying to compare percentages (scores) between *two different queries*
then trying to infer that there is some "better fit" based on that data
is where problems creep in.....


FWIW
Erick


On Sat, Aug 22, 2009 at 10:01 AM, Shashi Kant <shashi.mit@gmail.com> wrote:

> Chris & Erick's arguments are persuasive , however we do live in an
> imperfect world. Most of our users want to see the relative importance
> of a results vis-a-vis the rest....
>
> Relative Importance (%) = (d - dmin)/(dmax-dmin) * 100
>
> Where dmax is the highest Lucene score (score of top result) and dmin
> is the least (the score of the last result) and d = current score.
>
> This would work for any n results.
>
> While this might be technically 'meh', we took a simple normalization
> approach of Lucene scores, it helped the users in gauging the relative
> importance and relate better. End of day, isn't that what matters
> most?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

--002215048e77ed48150471e3b435--