katib
katib copied to clipboard
feat(rag): Auto-RAG
/kind feature
Ref https://arxiv.org/pdf/2404.01037.pdf
Auto-RAG: The idea of automatically optimizing RAG systems, akin to Auto-ML’s approach in traditional machine learning, presents a significant opportunity for future exploration. Currently, selecting the optimal configuration of RAG components — e.g., chunking strategies, window sizes, and parameters within rerankers — relies on manual experimentation and intuition. An automated system could systematically explore a vast space of RAG configurations and select the very best model (Markr.AI, 2024).
RAG requires some hyperparameters e.g. chunking strategies, and window sizes for sentence window retrieval. It should be done automatically.
Love this feature? Give it a 👍 We prioritize the features with the most 👍
Maybe we could add an example to showcase how to use Katib and LlamaIndex to AutoRAG.
Not sure if there is any new feature to be implemented.
Related: https://github.com/Marker-Inc-Korea/AutoRAG
Are you thinking of adding an example that uses the proposed tuning API for LLMs to demonstrate Auto-RAG?
@tariq-hasan It should work. But I do not have the bandwidth for it. I'm simply presenting the idea for consideration at this point.
Thanks for creating this @gaocegege. Are there any differences to optimize these HPs for RAG (e.g. chunking strategies and window sizes) compare to our current optimization flow with Experiment -> Suggestion -> Trials? I guess, Trials can consume prompt and produce the metrics.
The workflow should be similar. I think. We could make a demo based on llama index to see if there is anything we miss.
Hi! I'm the developer of AutoRAG. Do you still interested in implement AutoRAG or use it? Make demo for this? We are open for any kind of collaboration.
Nice to meet you @vkehfdl1! Sure, that would be great, maybe you can attend one of our upcoming AutoML and Training WG community calls to give a demo and we can discuss how we can collaborate. cc @kubeflow/wg-training-leads
Hi @andreyvelich Nice to meet you.
First, It will be hard to attend the community call today because the timezone. It is 2:00 a.m. here so hard to attend. Maybe other community call two weeks later in 2:00 UTC can be fine, or we can book another call.
Thanks!
Sure, that sounds great! I added you to the meeting agenda on July 24th.
Hi @vkehfdl1, just a reminder that our community call starts in 10 minutes, if you want to give AutoRAG demo.
/area llm