From 50596e1a6a3b9eb0a60b0d175feab9cd47e3b2b8 Mon Sep 17 00:00:00 2001 From: hippocritical Date: Sun, 4 May 2025 17:53:23 +0200 Subject: [PATCH] fixed typo --- docs/lookahead-analysis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/lookahead-analysis.md b/docs/lookahead-analysis.md index 9ff3ed792..7ad869369 100644 --- a/docs/lookahead-analysis.md +++ b/docs/lookahead-analysis.md @@ -69,7 +69,7 @@ You might be able to salvage it partially if the biased indicators or parts are - shift(-10) looks 10 candles into the future. - iloc[] accesses a specific row in the dataframe, be very careful with this. - For-loops are prone to introduce lookahead-bias if you don't tightly control which numbers are looped through. -- Aggregation funktions like .mean() .min(), .max(), without a rolling window, +- Aggregation functions like .mean() .min(), .max(), without a rolling window, will show you the respective pointers of the **whole** dataframe. A non-biased example of .mean() would be the following line. It just looks back 12 candles and takes its mean instead of the mean of the whole dataframe.