| clear query|facets|time |
Search criteria: relevant computing.
Results from 1 to 10 from
36 (4.538s).
|
|
|
Did you mean:
|
|
Loading phrases to help you
refine your search...
|
|
|
RE: Relevance percentage - Lucene - [mail # user]
|
|
...Query.BooleanWeight.explain(), which has the code to recompute coord on a result (specifically it computes overlap and maxoverlap and then calls Similarity.coord()). You could cut and paste this code to just compute coord...
|
|
... with > > >generating the rest of the explanation). If you support the full > Lucene > > >query language, then you need to look at all the query types and > decide > > >what exactly you want to compute...
|
|
|
Author: Chuck Williams,
2004-12-23, 08:56
|
|
|
RE: Relevance percentage - Lucene - [mail # user]
|
|
... support the full Lucene query language, then you need to look at all the query types and decide what exactly you want to compute (as coord is not always well-defined). I'm on the West Coast...
|
|
|
Author: Chuck Williams,
2004-12-20, 17:31
|
|
|
RE: Relevance and ranking ... - Lucene - [mail # user]
|
|
...Another issue will likely be the tf() and idf() computations. I have a similar desired relevance ranking and was not getting what I wanted due to the idf() term dominating the score...
|
|
|
Author: Chuck Williams,
2004-12-17, 19:32
|
|
|
RE: Relevance and ranking ... - Lucene - [mail # user]
|
|
... in the computation of lengthNorm to something much flatter. E.g., you might use: public float lengthNorm(String fieldName, int numTerms) { return (float)(1.0 / Math.log10(1000+numTerms)); } I...
|
|
.... You need to reindex when you change the Similarity (it is used for indexing and searching -- e.g., the lengthNorm's are computed at index time). 2. Be careful not to overtune your scoring...
|
[+ show more]
[- hide]
| ... an inverse-log lengthNorm with > a high base (like the formula for idf I posted earlier). > > The other thing that can bite you is the tf and idf computations. E.g., > if manual is a more... |
|
|
Author: Chuck Williams,
2004-12-20, 18:06
|
|
|
RE: Relevance and ranking ... - Lucene - [mail # user]
|
|
... base (like the formula for idf I posted earlier). The other thing that can bite you is the tf and idf computations. E.g., if manual is a more common term than the others, this could cause...
|
|
|
Author: Chuck Williams,
2004-12-18, 17:43
|
|
|
RE: structuring a multifield query - Lucene - [mail # user]
|
|
...FieldQueryParser method to parse my > query.. > > basically I have several fields.. title, contents, and a few others... > and I would like a query such as "super computer" to do the > standard...
|
|
... in the title > and "computer" in the content, but they must match somewhere.... I > obviously was able to do this when I queried a single field, is there > a schema to apply this to multiple...
|
|
|
Author: Chuck Williams,
2004-12-04, 21:24
|
|
|
Re: How to proceed with Bug 31841 - MultiSearcher problems with Similarity.docFreq() ? - Lucene - [mail # dev]
|
|
... point is that allocations could be reduced in MultiSearcher.prepareWeight (e.g., a simple one is to use a single HashMap rather than a HashSet and a HashMap for computing the cumulative doc...
|
|
|
Author: Chuck Williams,
2005-03-31, 19:26
|
|
|
RE: How to proceed with Bug 31841 - MultiSearcher problems with Similarity.docFreq() ? - Lucene - [mail # dev]
|
|
... use the Similarity to compute idf from docFreq. This Similarity in MultiSearcher would remain specializable by the application as today. One way to do achieve this would be to add a new...
|
|
|
Author: Chuck Williams,
2005-01-27, 17:19
|
|
|
RE: A question about scoring function in Lucene - Lucene - [mail # user]
|
|
.... > If you drop it, the score information is not correct > anymore or it not space vector model anymore. Could > you explain it a little bit. > > I think that it's expensive to computed...
|
|
.... > > > > 2 is a difference. Lucene uses Norm_q instead of > > Norm_d because Norm_d is too expensive to compute, > > especially in the presence of incremental indexing. > > E.g., adding...
|
|
|
Author: Chuck Williams,
2004-12-15, 17:05
|
|
|
RE: How to proceed with Bug 31841 - MultiSearcher problems with Similarity.docFreq() ? - Lucene - [mail # dev]
|
|
...It's a good point that the aggregate idf table holds enough information to do the rewrite()'s. So MultiSearcher can compute the Weights, which avoids the need to distribute the aggregate...
|
|
... tables to the remote nodes. It is still necessary to compute them and keep them current under index updates on the remote nodes, for which a delta-docFreq table still seems to me to be a good...
|
[+ show more]
[- hide]
| ... within the range. So, the Weight cannot be computed in > the > > MultiSearcher, as it does not have direct access to the remote index. > > > > This seems to put the viability... |
| ...Freqs and sum them). > > > > We need an aggregate docFreq table, and it needs to be on the remote > > nodes since the Weight's cannot be computed until after the Query is > > rewritten, which... |
|
|
Author: Chuck Williams,
2005-01-13, 16:52
|
|
|
|
|
|
Search results for computing :
|
|
|
Re: adding "explicit commits" to Lucene? - Lucene - [mail # dev]
|
|
|
|
Author: Chuck Williams,
2007-01-16, 05:19
|
|
|
Re: Results ranking on filtered multi-field query - Lucene - [mail # user]
|
|
|
|
Author: Chuck Williams,
2005-05-02, 18:31
|
|
|
Re: Include BM25 in Lucene? - Lucene - [mail # dev]
|
|
|
|
Author: Chuck Williams,
2006-10-17, 19:41
|
|
|
Re: categorized search - Lucene - [mail # user]
|
|
|
|
Author: Chuck Williams,
2005-04-24, 17:06
|
|
|
Re: wildcarded phrase queries - Lucene - [mail # user]
|
|
|
|
Author: Chuck Williams,
2005-04-06, 06:19
|
|
|
Re: Query.combine() - Lucene - [mail # dev]
|
|
|
|
Author: Chuck Williams,
2006-05-30, 21:55
|
|
|
RE: How to proceed with Bug 31841 - MultiSearcher problems with Similarity.docFreq() ? - Lucene - [mail # dev]
|
|
|
|
Author: Chuck Williams,
2005-01-13, 17:37
|
|
|
RE: How to proceed with Bug 31841 - MultiSearcher problems with Similarity.docFreq() ? - Lucene - [mail # dev]
|
|
|
|
Author: Chuck Williams,
2005-01-28, 17:30
|
|
|
RE: Relevance percentage - Lucene - [mail # user]
|
|
...Query.BooleanWeight.explain(), which has the code to recompute coord on a result (specifically it computes overlap and maxoverlap and then calls Similarity.coord()). You could cut and paste this code to just compute coord...
|
|
... with > > >generating the rest of the explanation). If you support the full > Lucene > > >query language, then you need to look at all the query types and > decide > > >what exactly you want to compute...
|
|
|
Author: Chuck Williams,
2004-12-23, 08:56
|
|
|
Correct of Query.combine() bugs with new MultiSearcher - Lucene - [mail # dev]
|
|
|
|
Author: Chuck Williams,
2005-04-26, 20:58
|
|
|
|
