-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TEMA200 to long? #10201
Comments
What is your startup_candle_count? |
You are using too much candle history for your indicator. You can add informative pairs by Following instructions from the informative pair documentation |
it's not "too much". I'm using that length as well. As long as they use the proper startup_candle_count, then there would be no issue |
Glad to hear that @stash86 , you are right the live default ohlcv_candle_limit is 500. |
actually it's 1000 for binance, which is the necessary length for TEMA200. If they are on different exchange, then yes they may have issues |
I thank you for your inputs. I was told, that informative pairs need to "warm up" after Bot start first. To access the value instantly, I may use the formula, to calculate TEMA from EMA: |
there is no such thing as warm up. All data and indicators are ready immediately |
Ok, in that case, I have a look at it, I thank you :) |
Sorry for my late reply, I thank you for your detailed answer. Absolutely great your table :) Here it is easy to see, what time the bot is consuming. I see, that after about 600 minutes, I would have had the desired result. Now I used the workaround of TEMA40 on informative timeframe 5m. Here I have no issue anymore. EMA200 would be far more easy, but after my analysis on Tradingview, if I want to enter only, when the line is below the price-action, I have less opportunities, during the bullish period, when the trend grows. TEMA200 lets me buy lower. (This is only one of multiple conditions). |
Describe your environment
python -V
)pip freeze | grep ccxt
)freqtrade -V
ordocker compose run --rm freqtrade -V
for Freqtrade running in docker)Your question
While EMA 200 or TEMA 3 for example works correctly, it seems, that TEMA 200 is something like "out of bounds". Do you know the issue, is there a workaround, (different notation?)
This notation works fine for timeperiod 3, for example, but not for 200:
dataframe['tema200'] = ta.TEMA(dataframe, timeperiod=200)
I get no error, but for .iloc[-1] there is nan as the value, even after multiple hours (1m timeframe).
For EMA200 I get the correct float value.
Background: I prefer TEMA200 instead of EMA200, due to its fast behavior.
Ask the question you have not been able to find an answer in the Documentation
The text was updated successfully, but these errors were encountered: