normalized scores

Recent questions about whether/how scores are normalized got me wondering how my application (happily) seems to be doing what I want. I have two indexes, one which contains text fields which I want to use as queries into text fields in a second index. I create a Boolean query based on all the t

Re: normalized scores

: For a given query (for a single input document), the highest score is : *not* always 1 (which is just how : I want it). Is this because I am using a Boolean query? Here is my code : snippet. the Hits class only normalizes scores if the highest score is greater then one, if it's less then 1 no no

Re: normalized scores

PM Please respond to java-user@lucene.apache.org To java-user@lucene.apache.org cc Subject Re: normalized scores : For a given query (for a single input document), the highest score is : *not* always 1 (which is just how : I want it). Is this because I am using a Boolean query? Here is my code

Re: normalized scores

On Mar 30, 2007, at 8:48 AM, Donna L Gresh wrote: It is unfortunate that some scores are being normalized and some may not be. Is there a way to obtain the unnormalized score? Any IndexSearcher.search method that does not return Hits keeps the raw scores. Try out the TopDocs returning one

Re: normalized scores

Thanks Erik, that works great-- Donna >> It is unfortunate that some scores are being normalized and some >> may not >> be. Is there a >> way to obtain the unnormalized score? >Any IndexSearcher.search method that does not return Hits keeps the >raw scores. Try out the TopDocs returning ones

Re: normalized scores

: I'm well aware that some queries will return no results due to my : filtering by 0.3. : That's the point. I expect that some of my input queries will not be a : good match : to *any* of the documents in my second index. what i'm trying ot make sure you understand is that picking 0.3 as an arbit

Custom ScoreDocComparator and normalized Scores

Hi, I'm trying to sort the search results by a "combination" of the "lucene score" and the value of a document field. The "combination" is something like that: scoreWeight * i.score + fieldWeight * getFieldValue(i.doc) I expect results between 0 and scoreWeight + fieldWeight

Re: Custom ScoreDocComparator and normalized Scores

First off: why do you need the normalized scores in your equation? for the purposes of comparing the calculated values in order to sort them, it shouldn't matter if they are normalized or not. Second: I strongly suggest you take a look at FunctionQuery ... it was created for hte expres pu

RE: Custom ScoreDocComparator and normalized Scores

-Mensaje original- De: Chris Hostetter [mailto:[EMAIL PROTECTED] Enviado el: martes, 20 de junio de 2006 21:55 Para: java-user@lucene.apache.org Asunto: Re: Custom ScoreDocComparator and normalized Scores First off: why do you need the normalized scores in your equation? for the purpo

RE: Custom ScoreDocComparator and normalized Scores

: Thanks Chris, I didn't know the "solr" package, it is not in the release : distribution, isn't? I'm going to read about it to see if it matchs our : needs. Solr is a seperate (incubation) project, that builds on top of Lucene, but the FunctionQuery classes have no dependencies outside of the Lu