lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Commented: (LUCENE-1540) Improvements to contrib.benchmark for TREC collections
Date Thu, 17 Feb 2011 16:02:24 GMT


Robert Muir commented on LUCENE-1540:

Hi guys, this is just a feature request (we can open a new issue if anyone is up for it).

I was wondering if we could do a simple write-up and put it in the website notes for 3.1,
whenever we can get to it, with some basic instructions on how to use this functionality.

I noticed with more research-oriented search engines, there are simple instructions for
how to index trec collections, run relevance experiments, and get trec_eval results... I feel
like if we had these it would be really beneficial towards getting new folks involved with

Some examples (some are simpler than others, but at least they all describe how to build the
* Terrier:
* Zettair:
* MG4J:
* Indri:

> Improvements to contrib.benchmark for TREC collections
> ------------------------------------------------------
>                 Key: LUCENE-1540
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: contrib/benchmark
>            Reporter: Tim Armstrong
>            Assignee: Doron Cohen
>            Priority: Minor
>             Fix For: 3.1, 4.0
>         Attachments: LUCENE-1540.patch, LUCENE-1540.patch, LUCENE-1540.patch, LUCENE-1540.patch,
> The benchmarking utilities for  TREC test collections ( are quite
limited and do not support some of the variations in format of older TREC collections.  
> I have been doing some benchmarking work with Lucene and have had to modify the package
to support:
> * Older TREC document formats, which the current parser fails on due to missing document
> * Variations in query format - newlines after <title> tag causing the query parser
to get confused.
> * Ability to detect and read in uncompressed text collections
> * Storage of document numbers by default without storing full text.
> I can submit a patch if there is interest, although I will probably want to write unit
tests for the new functionality first.

This message is automatically generated by JIRA.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message