-
Notifications
You must be signed in to change notification settings - Fork 185
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
supertrend output is not correct this is not matching with leading portal calculations #5
Comments
The problem seems to be while calculating EMA over TR. This gives a wrong ATR which in turn gives a wrong supertrend value |
Can you please correct it to get right superTrend value.
If this is corrected your logic will be the best optimized logic.
…On Mon, Apr 30, 2018 at 1:19 AM, tryrt4ms ***@***.***> wrote:
The problem seems to be while calculating EMA over TR. This gives a wrong
ATR which in turn gives a wrong supertrend value
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AgXQdV3VzJkzuuN-_oA4WnfAvR_lOs0aks5tthk4gaJpZM4SCnaf>
.
--
Regards,
Marx Chidambara Babu M.B
|
ATR calculation is already supported by TALIB library and it is a built-in function. To get a very accurate calculation of the trend, you should use ATR from the standard library. Nowhere i have seen EMA period is given as input for ATR calculation. |
Actually EMA module needs some corrections looks like. |
@Prchakr never mind code works absolutely fine |
Hi I am getting an error, Can anyone please help me to resolve this? Getting an Error--- |
Attached one works for me without issues and it matches Zerodha Kite chart. |
Checked the output for differrent parameter and it looks the accuracy is missing in the output.
try to run your code and compare the result with tradingview or with chartink.com the outputs are not matching at all.
Need correction so that accurate output can be obtained.
The text was updated successfully, but these errors were encountered: