lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marvin Humphrey (JIRA)" <>
Subject [jira] Commented: (LUCENE-1896) Modify confusing javadoc for queryNorm
Date Tue, 08 Sep 2009 02:52:57 GMT


Marvin Humphrey commented on LUCENE-1896:

FWIW, after all that [fuss|],

I would up leaving it in.

>From the standpoint of ordinary users, queryNorm() is harmless or mildly 
beneficial. Scores are never going to be comparable across multiple queries 
without what _I_ normally think of as "normalization" (given my background 
in audio): setting the top score to 1.0, and multiplying all other scores by the 
same factor. Nevertheless, it's better for them to be closer together than 
farther apart.

>From the standpoint of users trying to write Query subclasses, it's a wash.
On the one hand, it's not the most important method, since it doesn't affect
ranking within a single query -- and zapping it would mean one less thing to
think about.  On the other hand, it's nice to have it in there for the sake of
completeness in the implementation of cosine similarity.

I eventually would up messing with *how* the query norm gets applied to
achieve my de-voodoo-fication goals.  Essentially, I hid away queryNorm() so
that you don't need to think about it unless you really need it.

> Modify confusing javadoc for queryNorm
> --------------------------------------
>                 Key: LUCENE-1896
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Javadocs
>            Reporter: Jiri Kuhn
>            Priority: Minor
>             Fix For: 2.9
> See
> The javadoc confuses me as well.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message