Capreolus
Capreolus is a toolkit for conducting end-to-end ad hoc retrieval experiments. Capreolus provides fine control over the entire experimental pipeline through the use of interchangeable and configurable modules.
Read the documentation for a detailed overview.
Quick Start
- Prerequisites: Python 3.7+ and Java 11. See the installation instructions
- Install the pip package:
pip install capreolus - Train a model:
capreolus rerank.traineval with benchmark.name=nf reranker.name=KNRM reranker.trainer.niters=2 - If the
traincommand completed successfully, you've trained your first Capreolus reranker on NFCorpus! This command created several outputs, such as model checkpoints and TREC-format run files. To learn about these files, read about running experiments with Capreolus. - To learn about different configuration options, try:
capreolus rerank.print_config with benchmark.name=nf reranker.name=KNRM - To learn about different modules you can use, such as
reranker.name=DRMM, try:capreolus modules - Learn about running experiments via the Python API
Environment Variables
Capreolus uses environment variables to indicate where outputs should be stored and where document inputs can be found. Consult the table below to determine which variables should be set. Set them either on the fly before running Capreolus (export CAPREOLUS_RESULTS=...) or by editing your shell's initialization files (e.g., ~/.bashrc or ~/.zshrc).
| Environment Variable | Default Value | Purpose |
|---|---|---|
CAPREOLUS_RESULTS |
~/.capreolus/results/ | Directory where results will be stored |
CAPREOLUS_CACHE |
~/.capreolus/cache/ | Directory used for cache files |
CUDA_VISIBLE_DEVICES |
(unset) | Indicates GPUs available to PyTorch, starting from 0. For example, set to '1' the system's 2nd GPU (as numbered by nvidia-smi). Set to '' (an empty string) to force CPU. |
Metadata
Release files for capreolus 0.2.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| capreolus-0.2.6.tar.gz | 10.5 MB | Without provenance | Details for capreolus-0.2.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| capreolus-0.2.6-py3-none-any.whl | Python 3 | none | any | Details for capreolus-0.2.6-py3-none-any.whl |
Total release size: 21.3 MB
Release files / capreolus-0.2.6.tar.gz
| Download URL | capreolus-0.2.6.tar.gz |
|---|---|
| Size | 10.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c616525f291d333acf71429f95bfe6256bb75f9d7f32034bf924ad4a3c9175b
|
|
BLAKE2b-256 checksum How to use checksums |
dbdcbb17b1354adf3c2e7a8d82821218eb5225d75b847e706d56463b362ae8eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.24.0 setuptools/50.3.1.post20201107 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.7.9
|
Release files / capreolus-0.2.6-py3-none-any.whl
| Download URL | capreolus-0.2.6-py3-none-any.whl |
|---|---|
| Size | 10.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a8746aa0dd114e9fadd3c32762a7d014efb53df34feee29d1e439598041e50d
|
|
BLAKE2b-256 checksum How to use checksums |
a2269ec7e8ec0ca42887a13351b59d52b17099732cb313a4a2264cfb2104ad00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.24.0 setuptools/50.3.1.post20201107 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.7.9
|
Security for capreolus 0.2.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.