Currently, there are some hard-coded configurations and other issues in the pooling code:
The Elasticsearch connection and index to get passage IDs by document ID are hard-coded
Some paths are hard-coded.
The set of retrieval models and re-rankers is hard-coded.
I believe we should move the configuration to the CLI options and ideally not directly rely on Elasticsearch at all (e.g., by directly retrieving from the segmented corpus).
Currently, there are some hard-coded configurations and other issues in the pooling code:
I believe we should move the configuration to the CLI options and ideally not directly rely on Elasticsearch at all (e.g., by directly retrieving from the segmented corpus).