unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
>
>
--
View this message in context:
http://www.nabble.com/Modifying-score-based-on-tf-and-slop-tp23412168p24460573.html
Sent from the Lucene - Java Users mailing list archive a
Thanks a lot Mark.
Do Correct me if I am wrong. but what this means is tf does not really have
the same meaning as it does in case of other queries.
Also I think I understand better what hossman has told - in the sense that
BC is there in two matching spans , which is why we get higher score - th
tf() is used, just not with the term freq - the length of the matching
Spans is used instead.
The terms from nested Spans will still affect the score (you still get
IDF), but term freq is substituted with matching Span length.
Also, boosts of nested Spans are ignored - only the top level boos
pans method directly on your SpanNearQuery and
> iterate over them yourself, ignoring the ones you want to ignore.
>
>
>
> -Hoss
>
>
> ---
(Disclaimer: i'm not currently looking at the code, this email is entirely
a guess based on what i remember about SpanQueries)
: II ) Using default implementation of tf in Similarity class:
:
: Case 1 - Doc : "AB BC BC CD"
: Result : 4 - Actual score
: % match : ( actual score / max possibl
> >> But this adversely affects 3) as the slop value is factored into the
> >> tf ( as per what I can see in the span scorer)
> >>
> >>
> >> How can I ensure the frequency of a certain term does not affect the
> >> score while at the same ensur
the
>> tf ( as per what I can see in the span scorer)
>>
>>
>> How can I ensure the frequency of a certain term does not affect the
>> score while at the same ensuring that the slop does affect it ?
>>
>>
&g
Hey,
On Thu, May 7, 2009 at 3:51 AM, Radha Sreedharan wrote:
> Hi,
>
> I made tf return a 1.0f but the issue with that is that now the slop
> factor is neglected.
>
> So even if the tow terms in the span near query or far off or nearby
> the score returned is the same.
>
> I want the no of times o
Hi,
I made tf return a 1.0f but the issue with that is that now the slop
factor is neglected.
So even if the tow terms in the span near query or far off or nearby
the score returned is the same.
I want the no of times of the term occurring to be neglected but not the slop.
Radha
On Thu, May 7
Hey,
If I get you right you wanna make tf not affecting the score at all.
if so why don't you just return 1.0f by overriding similarity?
If you just wanna do that for the query you are using you could
override Query#getSimilarity and return a delegate to the actual
similarity.
Hope that helps.
si
Hi all,
All I have is a query running on a document with a single field which
has some search value. This is all which will be present.
No more documents / fields.
I have the following specific requirements
1) Length of document should not affect score - Implemented as per
lucene documentation u
11 matches
Mail list logo