The customer document D (from the aux
index) is supposed to be the top result. Ignore all
other scores from the aux index. Use this (max) score
of D to normalize all the scores of film docs from the
classification index.
HTH,
Doron
"Daniel Einspanjer" <[EMAIL PROTECTED]> wrote on
wrote:
"Daniel Einspanjer" <[EMAIL PROTECTED]> wrote on 30/05/2007 11:20:51:
> I want to keep the ability to specify how far part something is
> allowed to be, but from what I understood of Doron's response, I might
> lose that if I overrode sloppyFreq.
Just to cla
This may be a five year old explaining to a four year old why the sky
is blue, but I'll share some of the stuff I've picked up. :)
My application isn't so much a search engine as a matching engine. I
take a large list of movie documents from a customer like a movie
channel or a cable provider an
On 4/11/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: Not really. The explain scores aren't normalized and I also couldn't
: find a way to get the explain data as anything other than a whitespace
: formatted text blob from Solr. Keep in mind that they need confidence
the defualt way Solr du
Thank you both for the assistance.
I ended up going the tf(float) override route rather than sloppyFreq.
I want to keep the ability to specify how far part something is
allowed to be, but from what I understood of Doron's response, I might
lose that if I overrode sloppyFreq.
Because my applicatio
I've got a field that is indexing people names. The field is
multivalued and I'm using Solr with a positionIncrementGap of 100.
I've found that trying to specify a near query using something like:
actor_name_mv:"Foster, Jody"~2
matches "Foster, Jody" with a tf score of 1, but it matches "Jody
Fo
Oops. I do indeed have omitNorms turned on. I will re-read the
documentation on it and look at turning it off.
Sorry for the bother. :/
On 5/17/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: Terminator 2
: Terminator 2: Judgment Day
:
: And I score them against the query +title:(Terminator
If I have two items in an index:
Terminator 2
Terminator 2: Judgment Day
And I score them against the query +title:(Terminator 2)
they come up with the same score (which makes sense, it just isn't
quite what I want)
Would there be some method or combination of methods in Similarity
that I could
On 5/7/07, Doron Cohen <[EMAIL PROTECTED]> wrote:
With a query parser set to allowLeadingWildcard, this should do:
( +item -price:* ) ( +item +price:[0100 TO 0150] )
or, to avoid too-many-cluases risk:
( +item -price:[MIN TO MAX]) ( +item +price:[0100 TO 0150] )
where MIN and MAX cover (at least)
On 5/6/07, Erick Erickson <[EMAIL PROTECTED]> wrote:
On 5/5/07, Daniel Einspanjer <[EMAIL PROTECTED]> wrote:
>
> The query syntax reference page talks about the NOT and the - operators,
> but
> it wasn't clear to me what exactly the difference is between
them. Co
The query syntax reference page talks about the NOT and the - operators, but
it wasn't clear to me what exactly the difference is between them. Could
someone tell me briefly what that difference might be or point me at some
further docs that describe it?
Is there a way to require a portion of a
On 4/11/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
A custom Similaity class with simplified tf, idf, and queryNorm functions
might also help you get scores from the Explain method that are more
easily manageable since you'll have predictible query structures hard
coded into your application
& I
Penelope Spheeris
2005
.6 0
.1 0.7
B5The Kid
Jon Turteltaub
2000
On 4/11/07, Da
0.7
B5The Kid
Jon Turteltaub 2000
On 4/10/07, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
On Apr 10, 2007, at 8:03 PM, Daniel Einspanjer wrote:
> The people reviewing this matching process need some way of
> determining why a
eas.
Thank you very much for your time,
Daniel
-- Forwarded message ------
From: Daniel Einspanjer <[EMAIL PROTECTED]>
Date: Apr 10, 2007 8:04 AM
Subject: Ideas for a relevance score that could be considered stable
across multiple searches with the same query structure?
To: solr-
15 matches
Mail list logo
