From 46d489fe9291a182109668a6e66d6d28a2f1e594 Mon Sep 17 00:00:00 2001 From: Bagatur <22008038+baskaryan@users.noreply.github.com> Date: Mon, 23 Dec 2024 06:01:48 -0500 Subject: [PATCH] Update docs/evaluation/tutorials/backtesting.mdx Co-authored-by: Tanushree <87711021+tanushree-sharma@users.noreply.github.com> --- docs/evaluation/tutorials/backtesting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/evaluation/tutorials/backtesting.mdx b/docs/evaluation/tutorials/backtesting.mdx index 896703dc..9dde703c 100644 --- a/docs/evaluation/tutorials/backtesting.mdx +++ b/docs/evaluation/tutorials/backtesting.mdx @@ -6,7 +6,7 @@ sidebar_position: 5 Deploying your application is just the beginning of a continuous improvement process. Typically, you'll want to refine your system by enhancing prompts, language models, tools, and architectures. -Backtesting involves assessing new versions of your application using this historical data and comparing the new outputs to the original ones. +Backtesting involves assessing new versions of your application using historical data and comparing the new outputs to the original ones. This approach can offer a clearer indication of whether the new version is an improvement over the current deployment compared to evaluations using pre-production datasets. Here are the basic steps for backtesting: