forked from castorini/anserini
-
Notifications
You must be signed in to change notification settings - Fork 0
/
msmarco-v1-passage.bge-base-en-v1.5.hnsw.template
89 lines (56 loc) · 3.83 KB
/
msmarco-v1-passage.bge-base-en-v1.5.hnsw.template
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
# Anserini Regressions: MS MARCO Passage Ranking
**Model**: [BGE-base-en-v1.5](https://huggingface.co/BAAI/bge-base-en-v1.5) with HNSW indexes (using pre-encoded queries)
This page describes regression experiments, integrated into Anserini's regression testing framework, using the [BGE-base-en-v1.5](https://huggingface.co/BAAI/bge-base-en-v1.5) model on the [MS MARCO passage ranking task](https://github.com/microsoft/MSMARCO-Passage-Ranking), as described in the following paper:
> Shitao Xiao, Zheng Liu, Peitian Zhang, and Niklas Muennighoff. [C-Pack: Packaged Resources To Advance General Chinese Embedding.](https://arxiv.org/abs/2309.07597) _arXiv:2309.07597_, 2023.
In these experiments, we are using pre-encoded queries (i.e., cached results of query encoding).
The exact configurations for these regressions are stored in [this YAML file](${yaml}).
Note that this page is automatically generated from [this template](${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:
```bash
python src/main/python/run_regression.py --index --verify --search --regression ${test_name}
```
We make available a version of the MS MARCO Passage Corpus that has already been encoded with cosDPR-distil.
From any machine, the following command will download the corpus and perform the complete regression, end to end:
```bash
python src/main/python/run_regression.py --download --index --verify --search --regression ${test_name}
```
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/`:
```bash
wget ${download_url} -P collections/
tar xvf collections/${corpus}.tar -C collections/
```
To confirm, `${corpus}.tar` is 59 GB and has MD5 checksum `${download_checksum}`.
With the corpus downloaded, the following command will perform the remaining steps below:
```bash
python src/main/python/run_regression.py --index --verify --search --regression ${test_name} \
--corpus-path collections/${corpus}
```
## Indexing
Sample indexing command, building HNSW indexes:
```bash
${index_cmds}
```
The path `/path/to/${corpus}/` should point to the corpus downloaded above.
Upon completion, we should have an index with 8,841,823 documents.
Note that here we are explicitly using Lucene's `NoMergePolicy` merge policy, which suppresses any merging of index segments.
This is because merging index segments is a costly operation and not worthwhile given our query set.
## Retrieval
Topics and qrels are stored [here](https://github.com/castorini/anserini-tools/tree/master/topics-and-qrels), which is linked to the Anserini repo as a submodule.
The regression experiments here evaluate on the 6980 dev set questions; see [this page](${root_path}/docs/experiments-msmarco-passage.md) for more details.
After indexing has completed, you should be able to perform retrieval as follows using HNSW indexes:
```bash
${ranking_cmds}
```
Evaluation can be performed using `trec_eval`:
```bash
${eval_cmds}
```
## Effectiveness
With the above commands, you should be able to reproduce the following results:
${effectiveness}
Note that due to the non-deterministic nature of HNSW indexing, results may differ slightly between each experimental run.
Nevertheless, scores are generally within 0.005 of the reference values recorded in [our YAML configuration file](${yaml}).
## Reproduction Log[*](${root_path}/docs/reproducibility.md)
To add to this reproduction log, modify [this template](${template}) and run `bin/build.sh` to rebuild the documentation.