right, but the problem is when something is currently ranked as doc 20 but should be in the top 1, 5, or 10, and you aren't seeing it.
so I think if you are judging top-N docs from an existing system, you should look a little farther ahead than the top-N you care about. I think you should also index your data a few different ways and judge those top-N too, for example, use n-gram tokenizer. It doesn't have to be crazy like a formal trec-like pooling process, but I think you need to introduce enough variation that you have judgements for docs that should be ranked higher than they currently are. > Perfectly reasonable as well. I've seen some people who only care about > p...@5 and even p...@1 and others who do much more. The important thing is to > think about what makes sense for your application and users. Much of this > can be found through basic log analysis (assuming an existing system) or > some reasoning about use cases (new system) and users (how sophisticated > they are, etc.) > > -Grant > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > -- Robert Muir rcm...@gmail.com
