Evaluate and improve your Retrieval-Augmented Generation (RAG) pipelines with open-rag-eval
, an open-source Python evaluation toolkit.
Evaluating RAG quality can be complex. open-rag-eval
provides a flexible and extensible framework to measure the performance of your RAG system, helping you identify areas for improvement. Its modular design allows easy integration of custom metrics and connectors for various RAG implementations.
Out-of-the-box, the toolkit includes:
- An implementation of the evaluation metrics used in the TREC-RAG benchmark.
- A connector for the Vectara RAG platform.
- Standard Metrics: Provides TREC-RAG evaluation metrics ready to use.
- Modular Architecture: Easily add custom evaluation metrics or integrate with any RAG pipeline.
- Detailed Reporting: Generates per-query scores and intermediate outputs for debugging and analysis.
- Visualization: Compare results across different configurations or runs with plotting utilities.
This guide walks you through an end-to-end evaluation using the toolkit. We'll use Vectara as the example RAG platform and the TRECRAG evaluator.
- Python: Version 3.9 or higher.
- OpenAI API Key: Required for the default LLM judge model used in some metrics. Set this as an environment variable:
export OPENAI_API_KEY='your-api-key'
- Vectara Account: To enable the Vectara connector, you need:
- A Vectara account.
- A corpus containing your indexed data.
- An API key with querying permissions.
- Your Customer ID and Corpus key.
In order to build the library from source, which is the recommended method to follow the sample instructions below you can do:
$ git clone https://github.com/vectara/open-rag-eval.git
$ cd open-rag-eval
$ pip install -e .
If you want to install directly from pip, which is the common method if you want to use the library in your own pipeline instead of running the samples, you can run:
pip install open-rag-eval
After installing the library you can follow instructions below to run a sample evaluation and test out the library end to end.
Edit the eval_config.yaml file. This file controls the evaluation process, including connector details, evaluator choices, and metric settings. Update the connector
section with your Vectara customer_id
and corpus_key
.
In addition, make sure you have VECTARA_API_KEY
and OPENAI_API_KEY
available in your environment. For example:
- export VECTARA_API_KEY='your-vectara-api-key'
- export OPENAI_API_KEY='your-openai-api-key'
You need the results (answers and retrieved contexts) from your RAG system for the queries you want to evaluate.
open-rag-eval will automatically query your Vectara corpus and retrieve the results, as defined in your eval_config.yaml
file.
Create a CSV file named queries.csv
in the root directory. It should contain a single column named query
, with each row representing a query you want to test against your RAG system.
Example queries.csv
:
query
What is a blackhole?
How big is the sun?
How many moons does jupiter have?
With everything configured, now is the time to run evaluation! Run the following command from the root folder of open-rag-eval:
python open_rag_eval/run_eval.py --config eval_config.yaml
and you should see the evaluation progress on your command line. Once it's done, detailed results will be saved to a local CSV file where you can see the score assigned to each sample along with intermediate output useful for debugging and explainability.
You can use the plot_results.py
script to plot results from your eval runs. Multiple different runs can be plotted on the same plot allowing for easy comparison of different configurations or RAG providers:
To plot one result:
python open_rag_eval/plot_results.py open_eval_results.csv
Or to plot multiple results:
python open_rag_eval/plot_results.py results_1.csv results_2.csv results_3.csv
If you are using RAG outputs from your own pipeline, make sure to put your RAG output in a format that is readable by the toolkit (See data/test_csv_connector.csv
as an example).
Update the eval_config.yaml
as follows:
- Comment out or delete the connector section
- uncomment input_results and point it to the CSV file where your RAG results are stored.
With everything configured, now is the time to run evaluation! Run the following command:
python open_rag_eval/run_eval.py --config eval_config.yaml
and you should see the evaluation progress on your command line. Once it's done, detailed results will be saved to a local CSV file where you can see the score assigned to each sample along with intermediate output useful for debugging and explainability.
You can use the open_rag_eval/plot_results.py
script to plot results from your eval runs. Multiple different runs can be plotted on the same plot allowing for easy comparison of different configurations or RAG providers. For example if the output evaluation results from two runs are saved in open_eval_results_1.csv
and open_eval_results_2.csv
you can plot both of them as follows:
python open_rag_eval/plot_results.py open_eval_results_1.csv open_eval_results_2.csv
The visualization in step 3. above shows you the aggregated metrics across one or more runs of the evaluation on several queries. If you want to deep dive into the results, we have a results viewer which enables easy viewing od the produced metrics CSV where you can look at the intermediate results and detailed breakdown of scores and metrics on a per query basis. To do this:
cd open_rag_eval/viz/
streamlit run visualize.py
Note that you will need to have streamlit installed in your environment (which should be the case if you've installed open-rag-eval). Once you upload your evaluation results CSV (open_eval_results.csv
by default) you can select a query to view detailed metrics for such as the produced nuggets by the AutoNuggetizer, the UMBRELA scores assigned to each retrieved result and so on.
The open-rag-eval
framework follows these general steps during an evaluation:
- (Optional) Data Retrieval: If configured with a connector (like the Vectara connector), call the specified RAG provider with a set of input queries to generate answers and retrieve relevant document passages/contexts. If using pre-existing results (
input_results
), load them from the specified file. - Evaluation: Use a configured Evaluator to assess the quality of the RAG results (query, answer, contexts). The Evaluator applies one or more Metrics.
- Scoring: Metrics calculate scores based on different quality dimensions (e.g., faithfulness, relevance, context utilization). Some metrics may employ judge Models (like LLMs) for their assessment.
- Reporting: Generate a detailed report (typically CSV) containing the scores for each query, along with intermediate data useful for analysis and debugging.
- Metrics: Metrics are the core of the evaluation. They are used to measure the quality of the RAG system, each metric has a different focus and is used to evaluate different aspects of the RAG system. Metrics can be used to evaluate the quality of the retrieval, the quality of the (augmented) generation, the quality of the RAG system as a whole.
- Models: Models are the underlying judgement models used by some of the metrics. They are used to judge the quality of the RAG system. Models can be diverse: they may be LLMs, classifiers, rule based systems, etc.
- Evaluators: Evaluators can chain together a series of metrics to evaluate the quality of the RAG system.
- RAGResults: Data class representing the output of a RAG pipeline for a single query (input query, generated answer, retrieved contexts/documents). This is the primary input for evaluation.
- ScoredRAGResult: Data class holding the original
RAGResults
plus the scores assigned by theEvaluator
and itsMetrics
. These are typically collected and saved to the output report file.
For programmatic integration, the framework provides a Flask-based web server.
Endpoints:
/api/v1/evaluate
: Evaluate a single RAG output provided in the request body./api/v1/evaluate_batch
: Evaluate multiple RAG outputs in a single request.
Run the Server:
python open_rag_eval/run_server.py
See the API README for detailed documentation for the API.
π€ Vectara
- Website: vectara.com
- Twitter: @vectara
- GitHub: @vectara
- LinkedIn: @vectara
- Discord: @vectara
Contributions, issues and feature requests are welcome and appreciated!
Feel free to check issues page. You can also take a look at the contributing guide.
Give a βοΈ if this project helped you!
Copyright Β© 2025 Vectara.
This project is Apache 2.0 licensed.