Please see in a new thread - Boosting query - debuging
Thanks!
2009/5/2 Chris Hostetter
>
> : Sorry, you can see the script below:
>
> uh ... ok. so now you've posted a bunch of your code, but you still
> haven't addresed the root of what Erick and I were both getting at...
>
> : > Erick means
: Sorry, you can see the script below:
uh ... ok. so now you've posted a bunch of your code, but you still
haven't addresed the root of what Erick and I were both getting at...
: > Erick means we need to see *all* of your code (inlcuding how you get the
: > score and the Explanation you are pr
Sorry, you can see the script below:
Thanks
// Index Method
**/
public void index(DoubleMap doubleMap, String dirPath, String originalPath)
throws IOException
{
File f = new File(dirPath);
IndexWriter writer = null;
if(f.exists(
Erick means we need to see *all* of your code (inlcuding how you get the
score and the Explanation you are printing) to understand why they don't
match.
All you've shown is the output of your program and the generation of a
Hits object.
-Hoss
--
Hi,
You can see the output below:
1.0 * (this is the score)
4817674 5664274 6361333 (query)
4817674 5664274 6361333 (doc 0)
0.0 = (NON-MATCH) product of:
0.0 = (NON-MATCH) sum of:
0.0 = coord(0/3)
0.13811989 *
4817674
Well, let's see the results of toString and/or Explain *from your code*.
Otherwise, you haven't given us much to go on.
Best
Erick
On Fri, Apr 17, 2009 at 1:07 AM, liat oren wrote:
> Thanks for the answer.
>
> In Luke, I used the WhiteSpaceAnalyzer as well. The scores AND the explain
> method w
Thanks for the answer.
In Luke, I used the WhiteSpaceAnalyzer as well. The scores AND the explain
method worked perfectly.
In my application, I checked for the query - it contains the numbers
splitted in different term queries so it prepares it well. Also the scoring
is good. However the explain
Hmmm, try query.toString() and/or query.explain().
Also, try using Luke to see what is actually in the document.
BTW, what analyzer did you use in Luke? Luke also has an
explain (tab?) that will show you what Luke does, which may
be useful.
The default operator should be "OR", but looking at the
I wanted to add also that I index it tokenized and that when I use Luke to
do this search, it gives the correct results.
Should I run the query differntly than the way I do?
2009/4/16 liat oren
> Hi,
>
> I try to understand why the following query gives the scoring below:
>
> document 1 : a b
Thank you Chris. That seems like a good suggestion. I will try to pass a
different Query object to the Highlighter api that the one used for
searching.
I plan to break down the HTML document and store the title/sub
title/content in different fields of the index. So if I create a new
query com
: My requirement is to show the relevant fragments of the news article for
: each company along with the search results. But the highlighter api
: sometimes picks up the fragments which are not so relevant to the news
: article/company. I would like to know if there is anyway that I can
: modify t
Yes I was refering to how IDF is used in the Highlighter code to find
out how to prioritize fragments of the documents.
My requirement is to show the relevant fragments of the news article for
each company along with the search results. But the highlighter api
sometimes picks up the fragments
Sorry to contradict, Erik, but the Highlighter's QueryScorer will make
use of IDF, given a reader, in order to better prioritise which are the
"best" bits of a document.
However, In the particular example given, the criteria includes several
non-text fields which are not useful for IDF and gener
Harini,
I'm not sure I understand what you're asking. IDF doesn't factor
into highlighting.
IDF calculations are useful in scoring documents during a search,
such that the most relevant documents are returned, but again this is
unrelated to highlighting.
Could you elaborate on what you
14 matches
Mail list logo
