From a239e5f72593dd99a2cc218f8a28b424a4705e39 Mon Sep 17 00:00:00 2001 From: Matthias Date: Sat, 13 Nov 2021 12:57:51 +0100 Subject: [PATCH] Add segment on colliding signals --- docs/strategy-customization.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/strategy-customization.md b/docs/strategy-customization.md index d54bae710..aeb837e16 100644 --- a/docs/strategy-customization.md +++ b/docs/strategy-customization.md @@ -1016,6 +1016,10 @@ The following lists some common patterns which should be avoided to prevent frus - don't use `dataframe['volume'].mean()`. This uses the full DataFrame for backtesting, including data from the future. Use `dataframe['volume'].rolling().mean()` instead - don't use `.resample('1h')`. This uses the left border of the interval, so moves data from an hour to the start of the hour. Use `.resample('1h', label='right')` instead. +### Colliding signals + +When buy and sell signals collide (both `'buy'` and `'sell'` are 1), freqtrade will do nothing. This is to avoid trades that buy, and sell immediately. Obviously, this can lead to both missed entries, as well as missed exits. + ## Further strategy ideas To get additional Ideas for strategies, head over to the [strategy repository](https://github.com/freqtrade/freqtrade-strategies). Feel free to use them as they are - but results will depend on the current market situation, pairs used etc. - therefore please backtest the strategy for your exchange/desired pairs first, evaluate carefully, use at your own risk.