Skip to content

Latest commit

 

History

History
141 lines (96 loc) · 8.25 KB

regressions-msmarco-passage-unicoil-tilde-expansion.md

File metadata and controls

141 lines (96 loc) · 8.25 KB
Raw

Anserini Regressions: MS MARCO Passage Ranking

Model: uniCOIL (with TILDE expansions)

This page describes regression experiments, integrated into Anserini's regression testing framework, using uniCOIL (with TILDE expansions) on the MS MARCO passage ranking task. The uniCOIL+TILDE model is described in the following paper:

Shengyao Zhuang and Guido Zuccon. Fast Passage Re-ranking with Contextualized Exact Term Matching and Efficient Passage Expansion. arXiv:2108.08513.

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-passage-unicoil-tilde-expansion

Corpus

We make available a version of the MS MARCO passage corpus that has already been processed with the model (i.e., with inference applied to generate the lexical representations). Thus, no neural inference is involved.

Download the corpus and unpack into collections/:

wget https://rgw.cs.uwaterloo.ca/JIMMYLIN-bucket0/data/msmarco-passage-unicoil-tilde-expansion.tar -P collections/

tar xvf collections/msmarco-passage-unicoil-tilde-expansion.tar -C collections/

To confirm, msmarco-passage-unicoil-tilde-expansion.tar is 3.9 GB and has MD5 checksum 1685aee10071441987ad87f2e91f1706.

With the corpus downloaded, the following command will perform the complete regression, end to end, on any machine:

python src/main/python/run_regression.py --index --verify --search --regression msmarco-passage-unicoil-tilde-expansion \
  --corpus-path collections/msmarco-passage-unicoil-tilde-expansion

Alternatively, you can simply copy/paste from the commands below and obtain the same results.

Indexing

Sample indexing command:

target/appassembler/bin/IndexCollection \
  -collection JsonVectorCollection \
  -input /path/to/msmarco-passage-unicoil-tilde-expansion \
  -index indexes/lucene-index.msmarco-passage-unicoil-tilde-expansion/ \
  -generator DefaultLuceneDocumentGenerator \
  -threads 16 -impact -pretokenized \
  >& logs/log.msmarco-passage-unicoil-tilde-expansion &

The path /path/to/msmarco-passage-unicoil-tilde-expansion/ should point to the corpus downloaded above.

The important indexing options to note here are -impact -pretokenized: the first tells Anserini not to encode BM25 doc lengths into Lucene's norms (which is the default) and the second option says not to apply any additional tokenization on the SPLADEv2 tokens. Upon completion, we should have an index with 8,841,823 documents.

For additional details, see explanation of common indexing options.

Retrieval

Topics and qrels are stored in src/main/resources/topics-and-qrels/. 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:

target/appassembler/bin/SearchCollection \
  -index indexes/lucene-index.msmarco-passage-unicoil-tilde-expansion/ \
  -topics src/main/resources/topics-and-qrels/topics.msmarco-passage.dev-subset.unicoil-tilde-expansion.tsv.gz \
  -topicreader TsvInt \
  -output runs/run.msmarco-passage-unicoil-tilde-expansion.unicoil-tilde-expansion.topics.msmarco-passage.dev-subset.unicoil-tilde-expansion.txt \
  -impact -pretokenized &

Evaluation can be performed using trec_eval:

tools/eval/trec_eval.9.0.4/trec_eval -c -m map src/main/resources/topics-and-qrels/qrels.msmarco-passage.dev-subset.txt runs/run.msmarco-passage-unicoil-tilde-expansion.unicoil-tilde-expansion.topics.msmarco-passage.dev-subset.unicoil-tilde-expansion.txt
tools/eval/trec_eval.9.0.4/trec_eval -c -M 10 -m recip_rank src/main/resources/topics-and-qrels/qrels.msmarco-passage.dev-subset.txt runs/run.msmarco-passage-unicoil-tilde-expansion.unicoil-tilde-expansion.topics.msmarco-passage.dev-subset.unicoil-tilde-expansion.txt
tools/eval/trec_eval.9.0.4/trec_eval -c -m recall.100 src/main/resources/topics-and-qrels/qrels.msmarco-passage.dev-subset.txt runs/run.msmarco-passage-unicoil-tilde-expansion.unicoil-tilde-expansion.topics.msmarco-passage.dev-subset.unicoil-tilde-expansion.txt
tools/eval/trec_eval.9.0.4/trec_eval -c -m recall.1000 src/main/resources/topics-and-qrels/qrels.msmarco-passage.dev-subset.txt runs/run.msmarco-passage-unicoil-tilde-expansion.unicoil-tilde-expansion.topics.msmarco-passage.dev-subset.unicoil-tilde-expansion.txt

Effectiveness

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

AP@1000 uniCOIL (with TILDE expansions)
MS MARCO Passage: Dev 0.3561
RR@10 uniCOIL (with TILDE expansions)
MS MARCO Passage: Dev 0.3496
R@100 uniCOIL (with TILDE expansions)
MS MARCO Passage: Dev 0.8678
R@1000 uniCOIL (with TILDE expansions)
MS MARCO Passage: Dev 0.9646

The above runs are in TREC output format and evaluated with trec_eval. In order to reproduce results reported in the paper, we need to convert to MS MARCO output format and then evaluate:

python tools/scripts/msmarco/convert_trec_to_msmarco_run.py \
   --input runs/run.msmarco-passage-unicoil-tilde-expansion.unicoil-tilde-expansion.topics.msmarco-passage.dev-subset.unicoil-tilde-expansion.txt \
   --output runs/run.msmarco-passage-unicoil-tilde-expansion.unicoil-tilde-expansion.topics.msmarco-passage.dev-subset.unicoil-tilde-expansion.tsv --quiet

python tools/scripts/msmarco/msmarco_passage_eval.py \
   tools/topics-and-qrels/qrels.msmarco-passage.dev-subset.txt \
   runs/run.msmarco-passage-unicoil-tilde-expansion.unicoil-tilde-expansion.topics.msmarco-passage.dev-subset.unicoil-tilde-expansion.tsv

The results should be as follows:

#####################
MRR @10: 0.34957184927457136
QueriesRanked: 6980
#####################

This corresponds to the effectiveness reported in the paper.

Reproduction Log*

To add to this reproduction log, modify this template and run bin/build.sh to rebuild the documentation.