Skip to content

Latest commit

 

History

History
148 lines (108 loc) · 10.3 KB

regressions-dl19-passage.unicoil.md

File metadata and controls

148 lines (108 loc) · 10.3 KB
Raw

Anserini Regressions: TREC 2019 Deep Learning Track (Passage)

Model: uniCOIL (with doc2query-T5 expansions)

This page describes regression experiments, integrated into Anserini's regression testing framework, using uniCOIL (with doc2query-T5 expansions) on the TREC 2019 Deep Learning Track passage ranking task. The uniCOIL model is described in the following paper:

Jimmy Lin and Xueguang Ma. A Few Brief Notes on DeepImpact, COIL, and a Conceptual Framework for Information Retrieval Techniques. arXiv:2106.14807.

The experiments on this page are not actually reported in the paper. However, the model is the same.

Note that the NIST relevance judgments provide far more relevant passages per topic, unlike the "sparse" judgments provided by Microsoft (these are sometimes called "dense" judgments to emphasize this contrast). For additional instructions on working with MS MARCO passage collection, refer to this page.

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 and then run bin/build.sh to rebuild the documentation.

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 dl19-passage.unicoil

We make available a version of the MS MARCO Passage Corpus that has already been processed with uniCOIL, i.e., we have applied doc2query-T5 expansions, performed model inference on every document, and stored the output sparse vectors. Thus, no neural inference is involved.

From any machine, the following command will download the corpus and perform the complete regression, end to end:

python src/main/python/run_regression.py --download --index --verify --search --regression dl19-passage.unicoil

The run_regression.py script automates the following steps, but if you want to perform each step manually, simply copy/paste from the commands below and you'll obtain the same regression results.

Corpus Download

Download the corpus and unpack into collections/:

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

To confirm, msmarco-passage-unicoil.tar is 3.4 GB and has MD5 checksum 78eef752c78c8691f7d61600ceed306f. With the corpus downloaded, the following command will perform the remaining steps below:

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

Indexing

Sample indexing command:

bin/run.sh io.anserini.index.IndexCollection \
  -collection JsonVectorCollection \
  -input /path/to/msmarco-passage-unicoil \
  -generator DefaultLuceneDocumentGenerator \
  -index indexes/lucene-inverted.msmarco-v1-passage.unicoil/ \
  -threads 16 -impact -pretokenized -storeDocvectors \
  >& logs/log.msmarco-passage-unicoil &

The path /path/to/msmarco-passage-unicoil/ 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 doclengths into Lucene's norms (which is the default) and the second option says not to apply any additional tokenization on the uniCOIL 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 here, which is linked to the Anserini repo as a submodule. The regression experiments here evaluate on the 43 topics for which NIST has provided judgments as part of the TREC 2019 Deep Learning Track. The original data can be found here.

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.unicoil/ \
  -topics tools/topics-and-qrels/topics.dl19-passage.unicoil.0shot.tsv.gz \
  -topicReader TsvInt \
  -output runs/run.msmarco-passage-unicoil.unicoil-cached_q.topics.dl19-passage.unicoil.0shot.txt \
  -impact -pretokenized &

bin/run.sh io.anserini.search.SearchCollection \
  -index indexes/lucene-inverted.msmarco-v1-passage.unicoil/ \
  -topics tools/topics-and-qrels/topics.dl19-passage.unicoil.0shot.tsv.gz \
  -topicReader TsvInt \
  -output runs/run.msmarco-passage-unicoil.unicoil-cached_q+rm3.topics.dl19-passage.unicoil.0shot.txt \
  -impact -pretokenized -rm3 &

bin/run.sh io.anserini.search.SearchCollection \
  -index indexes/lucene-inverted.msmarco-v1-passage.unicoil/ \
  -topics tools/topics-and-qrels/topics.dl19-passage.unicoil.0shot.tsv.gz \
  -topicReader TsvInt \
  -output runs/run.msmarco-passage-unicoil.unicoil-cached_q+rocchio.topics.dl19-passage.unicoil.0shot.txt \
  -impact -pretokenized -rocchio &

Evaluation can be performed using trec_eval:

bin/trec_eval -m map -c -l 2 tools/topics-and-qrels/qrels.dl19-passage.txt runs/run.msmarco-passage-unicoil.unicoil-cached_q.topics.dl19-passage.unicoil.0shot.txt
bin/trec_eval -m ndcg_cut.10 -c tools/topics-and-qrels/qrels.dl19-passage.txt runs/run.msmarco-passage-unicoil.unicoil-cached_q.topics.dl19-passage.unicoil.0shot.txt
bin/trec_eval -m recall.100 -c -l 2 tools/topics-and-qrels/qrels.dl19-passage.txt runs/run.msmarco-passage-unicoil.unicoil-cached_q.topics.dl19-passage.unicoil.0shot.txt
bin/trec_eval -m recall.1000 -c -l 2 tools/topics-and-qrels/qrels.dl19-passage.txt runs/run.msmarco-passage-unicoil.unicoil-cached_q.topics.dl19-passage.unicoil.0shot.txt

bin/trec_eval -m map -c -l 2 tools/topics-and-qrels/qrels.dl19-passage.txt runs/run.msmarco-passage-unicoil.unicoil-cached_q+rm3.topics.dl19-passage.unicoil.0shot.txt
bin/trec_eval -m ndcg_cut.10 -c tools/topics-and-qrels/qrels.dl19-passage.txt runs/run.msmarco-passage-unicoil.unicoil-cached_q+rm3.topics.dl19-passage.unicoil.0shot.txt
bin/trec_eval -m recall.100 -c -l 2 tools/topics-and-qrels/qrels.dl19-passage.txt runs/run.msmarco-passage-unicoil.unicoil-cached_q+rm3.topics.dl19-passage.unicoil.0shot.txt
bin/trec_eval -m recall.1000 -c -l 2 tools/topics-and-qrels/qrels.dl19-passage.txt runs/run.msmarco-passage-unicoil.unicoil-cached_q+rm3.topics.dl19-passage.unicoil.0shot.txt

bin/trec_eval -m map -c -l 2 tools/topics-and-qrels/qrels.dl19-passage.txt runs/run.msmarco-passage-unicoil.unicoil-cached_q+rocchio.topics.dl19-passage.unicoil.0shot.txt
bin/trec_eval -m ndcg_cut.10 -c tools/topics-and-qrels/qrels.dl19-passage.txt runs/run.msmarco-passage-unicoil.unicoil-cached_q+rocchio.topics.dl19-passage.unicoil.0shot.txt
bin/trec_eval -m recall.100 -c -l 2 tools/topics-and-qrels/qrels.dl19-passage.txt runs/run.msmarco-passage-unicoil.unicoil-cached_q+rocchio.topics.dl19-passage.unicoil.0shot.txt
bin/trec_eval -m recall.1000 -c -l 2 tools/topics-and-qrels/qrels.dl19-passage.txt runs/run.msmarco-passage-unicoil.unicoil-cached_q+rocchio.topics.dl19-passage.unicoil.0shot.txt

Effectiveness

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

AP@1000 uniCOIL (with doc2query-T5 expansions) +RM3 +Rocchio
DL19 (Passage) 0.4612 0.4641 0.4603
nDCG@10 uniCOIL (with doc2query-T5 expansions) +RM3 +Rocchio
DL19 (Passage) 0.7024 0.6761 0.6658
R@100 uniCOIL (with doc2query-T5 expansions) +RM3 +Rocchio
DL19 (Passage) 0.6054 0.6207 0.6211
R@1000 uniCOIL (with doc2query-T5 expansions) +RM3 +Rocchio
DL19 (Passage) 0.8292 0.8598 0.8515

Note that retrieval metrics are computed to depth 1000 hits per query (as opposed to 100 hits per query for document ranking). Also, for computing nDCG, remember that we keep qrels of all relevance grades, whereas for other metrics (e.g., AP), relevance grade 1 is considered not relevant (i.e., use the -l 2 option in trec_eval). The experimental results reported here are directly comparable to the results reported in the track overview paper.

Reproduction Log*

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