You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+78-29Lines changed: 78 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,17 @@ The **Retrieval Optimizer** from Redis is designed to bring focus back to what m
15
15
16
16
Beyond accuracy alone, it also supports evaluating critical tradeoffs between **cost, speed, and latency**, helping you understand how different embedding models, retrieval strategies, and index configurations impact overall system performance. The ultimate goal is to enable **metrics-driven development** for your search application—ensuring that decisions are grounded in data, not assumptions.
17
17
18
+
# Example notebooks
19
+
20
+
For complete code examples see the following notebooks:
21
+
22
+
| Topic | Notebook |
23
+
| ------ | ------- |
24
+
| Basic grid study |[00_grid_study.ipynb](https://github.com/redis-applied-ai/redis-retrieval-optimizer/blob/dfc36382efd7e5e06903482a8a23a32bc047f1e9/docs/examples/grid_study/00_grid_study.ipynb)|
25
+
| Custom grid study |[01_custom_grid_study.ipynb](https://github.com/redis-applied-ai/redis-retrieval-optimizer/blob/dfc36382efd7e5e06903482a8a23a32bc047f1e9/docs/examples/grid_study/01_custom_grid_study.ipynb)|
| Embedding model comparison |[00_comparison.ipynb](https://github.com/redis-applied-ai/redis-retrieval-optimizer/blob/main/docs/examples/comparison/00_comparison.ipynb)|
28
+
18
29
# Quick Start
19
30
20
31
The Retrieval Optimizer supports two *study* types: **Grid** and **Bayesian Optimization**. Each is suited to a different stage of building a high-quality search system.
@@ -33,13 +44,15 @@ Once you've identified a solid starting point, use Bayesian optimization to **fi
33
44
#### Define study config
34
45
```yaml
35
46
# paths to necessary data files
36
-
corpus: "data/nfcorpus_corpus.json"# optional if from_existing
47
+
corpus: "data/nfcorpus_corpus.json"
37
48
queries: "data/nfcorpus_queries.json"
38
49
qrels: "data/nfcorpus_qrels.json"
39
50
40
51
# vector field names
41
52
index_settings:
42
53
name: "optimize"
54
+
vector_field_name: "vector"# name of the vector field to search on
55
+
text_field_name: "text"# name of the text field for lexical search
search_methods: ["basic_vector", "pre_filter_vector"]# must match what is passed in search_method_map
225
276
```
226
277
227
278
---
228
279
229
280
### Writing Custom Search Methods
230
281
231
-
Search methods can be anything you want—as long as they accept a `SearchMethodInput` and return a `SearchMethodOutput`. This allows you to test new retrieval strategies, add filters, or layer on post-processing logic.
282
+
Search methods can be anything you wantas long as the function accepts a `SearchMethodInput` and returns a `SearchMethodOutput`. This allows you to test new retrieval strategies, add filters, or layer on post-processing logic.
Here's a polished and clearer version of your **Data Requirements** section, matching the tone and structure of the rest of the content. It emphasizes flexibility while giving users a concrete foundation to build from:
0 commit comments