-
Notifications
You must be signed in to change notification settings - Fork 992
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
Most of the indicators returns NaN. #626
Comments
Hello @benimadimkadir, Interesting. 🤔 Could you share some 500 rows of your csv? Kind Regards |
Also, Talib returns same results. I tried with dataframe has 1000 rows, it works in both Pandas_ta and Talib functions. I am not sure, but I think they both have this problem with the algorithms they have in common. Talib doesn't have Vortex indicator, therefore Pandas_ta's Vortex indicator works. For now I'm dividing the data into small parts and using them as input and than combine the results. This is the first 500 row: |
I do not understand. What works? All the indicators? You ran Pandas TA indicators separate from TA Lib indicators and go the same results? It only works with up to 1000 rows? How many rows does it work up to? 1500? 2000? 3000? 5000? 10000?
I dubious of that claim without hard evidence. KJ |
ok i thought i faced the same issue until i changed the number of rows i fed to the library |
I was about to open a issue then I saw this post for me every indicator I wanted worked but EOM only gets calculated instead of returning a all NaN dataframe if length of the data is smaller here is what I found. 2022-11-18 18:49:59.999 -0.608464 2022-11-18 18:49:59.999 NaN There is something between 43.3k bars input and 50.5k bars input that makes the library spit out all NaN, just wanted to give feedback also tested with different csv's acts the same when length is above 43.3k bars. |
Pandas_ta version: 0.3.14b0
Python version: Python 3.8.10
Ta-Lib is installed. Ta-Lib version: 0.4.24
Most of the indicators return Nan. Only a few indicators work.
Vortex works:
The text was updated successfully, but these errors were encountered: