Skip to content

Latest commit

 

History

History
74 lines (55 loc) · 4.47 KB

regressions-msmarco-v1-passage.wp-tok.md

File metadata and controls

74 lines (55 loc) · 4.47 KB
Raw

Anserini Regressions: MS MARCO Passage Ranking

Models: bag-of-words approaches with WordPiece tokenization

This page documents regression experiments on the MS MARCO passage ranking task, which is integrated into Anserini's regression testing framework. Here we are using WordPiece tokenization (i.e., from BERT). In general, effectiveness is lower than with "standard" Lucene tokenization for two reasons: (1) we're losing stemming, and (2) some terms are chopped into less meaningful subwords.

The exact configurations for these regressions are stored in this YAML file. Note that this page is automatically generated from this template as part of Anserini's regression pipeline, so do not modify this page directly; modify the template instead.

From one of our Waterloo servers (e.g., orca), the following command will perform the complete regression, end to end:

python src/main/python/run_regression.py --index --verify --search --regression msmarco-v1-passage.wp-tok

Indexing

Typical indexing command:

bin/run.sh io.anserini.index.IndexCollection \
  -threads 9 \
  -collection JsonCollection \
  -input /path/to/msmarco-passage-wp \
  -generator DefaultLuceneDocumentGenerator \
  -index indexes/lucene-inverted.msmarco-v1-passage.wp-tok/ \
  -storePositions -storeDocvectors -storeRaw -pretokenized \
  >& logs/log.msmarco-passage-wp &

The directory /path/to/msmarco-passage-wp/ should be a directory containing the corpus in Anserini's jsonl format.

For additional details, see explanation of common indexing options.

Retrieval

Topics and qrels are stored here, which is linked to the Anserini repo as a submodule. The regression experiments here evaluate on the 6980 dev set questions; see this page for more details.

After indexing has completed, you should be able to perform retrieval as follows:

bin/run.sh io.anserini.search.SearchCollection \
  -index indexes/lucene-inverted.msmarco-v1-passage.wp-tok/ \
  -topics tools/topics-and-qrels/topics.msmarco-passage.dev-subset.wp.tsv.gz \
  -topicReader TsvInt \
  -output runs/run.msmarco-passage-wp.bm25-default.topics.msmarco-passage.dev-subset.wp.txt \
  -bm25 -pretokenized &

Evaluation can be performed using trec_eval:

bin/trec_eval -c -m map tools/topics-and-qrels/qrels.msmarco-passage.dev-subset.txt runs/run.msmarco-passage-wp.bm25-default.topics.msmarco-passage.dev-subset.wp.txt
bin/trec_eval -c -M 10 -m recip_rank tools/topics-and-qrels/qrels.msmarco-passage.dev-subset.txt runs/run.msmarco-passage-wp.bm25-default.topics.msmarco-passage.dev-subset.wp.txt
bin/trec_eval -c -m recall.100 tools/topics-and-qrels/qrels.msmarco-passage.dev-subset.txt runs/run.msmarco-passage-wp.bm25-default.topics.msmarco-passage.dev-subset.wp.txt
bin/trec_eval -c -m recall.1000 tools/topics-and-qrels/qrels.msmarco-passage.dev-subset.txt runs/run.msmarco-passage-wp.bm25-default.topics.msmarco-passage.dev-subset.wp.txt

Effectiveness

With the above commands, you should be able to reproduce the following results:

AP@1000 BM25 (default)
MS MARCO Passage: Dev 0.1836
RR@10 BM25 (default)
MS MARCO Passage: Dev 0.1752
R@100 BM25 (default)
MS MARCO Passage: Dev 0.6231
R@1000 BM25 (default)
MS MARCO Passage: Dev 0.8263