Discover and explore top open-source AI tools and projects—updated daily.
TIGER-AI-LabRAG framework enhanced with long-context LLMs
Top 100.0% on SourcePulse
LongRAG addresses the performance limitations of traditional Retrieval-Augmented Generation (RAG) frameworks by rebalancing the workload between retrieval and reading components. It introduces a novel approach using significantly longer retrieval units (4K tokens) and supporting advanced long-context Large Language Models (LLMs) as readers. This framework is designed for researchers and practitioners seeking to enhance RAG systems, offering improved information completeness and potentially higher accuracy in complex question-answering tasks.
How It Works
LongRAG replaces the conventional RAG design, which often relies on short retrieval units and burdens the retriever with extensive searching, with a dual "long retriever" and "long reader" architecture. By employing retrieval units that are approximately 30 times longer (4K tokens), the system aims to provide richer context per unit. This allows the reader LLM to process more comprehensive information, reducing ambiguity and improving the overall efficiency and effectiveness of the RAG pipeline. The approach leverages established dense retrieval toolkits and state-of-the-art long-context LLMs.
Quick Start & Requirements
git clone https://github.com/TIGER-AI-Lab/LongRAG.git), navigate into the directory (cd LongRAG), and install dependencies (pip install -r requirements.txt).scripts/run_retrieve_tevatron.sh) suggests a need for multiple GPUs (example uses 4). Evaluating the reader (scripts/run_eval_qa.sh) requires API keys and configurations for supported LLMs (GPT-4o, GPT-4-Turbo, Gemini-1.5-Pro, Claude-3-Opus).Highlighted Details
Maintenance & Community
The project is associated with authors Ziyan Jiang, Xueguang Ma, and Wenhu Chen. The repository is noted as still undergoing polishing. No specific community channels (e.g., Discord, Slack) or roadmap links are provided.
Licensing & Compatibility
Limitations & Caveats
The repository is explicitly stated to be in the process of being polished, indicating potential for ongoing changes. Support for additional LLMs is planned but not yet implemented. Users must configure API keys and settings for specific reader models, and the corpus preparation steps can be complex and resource-intensive.
1 year ago
Inactive
stanford-futuredata