mohammadian7/freqtrade
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update strategy-customization.md

Browse Source 
Shouldn't the timeperiod be 100 when defining a ema100?
This commit is contained in:
konradbeck
2023-11-13 13:50:32 +02:00
committed by GitHub
parent f9d061b648
commit e6663c0304
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/strategy-customization.md
+1 -1
View File
@@ -173,7 +173,7 @@ You can use [recursive-analysis](recursive-analysis.md) to check and find the co
In this example strategy, this should be set to 400 (`startup_candle_count = 400`), since the minimum needed history for ema100 calculation to make sure the value is correct is 400 candles. In this example strategy, this should be set to 400 (`startup_candle_count = 400`), since the minimum needed history for ema100 calculation to make sure the value is correct is 400 candles.
``` python ``` python
dataframe['ema100'] = ta.EMA(dataframe, timeperiod=400) dataframe['ema100'] = ta.EMA(dataframe, timeperiod=100)
``` ```
By letting the bot know how much history is needed, backtest trades can start at the specified timerange during backtesting and hyperopt. By letting the bot know how much history is needed, backtest trades can start at the specified timerange during backtesting and hyperopt.