ok, that was a wrong copy paste, Here's the actual traceback:
=========
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.5/dist-packages/kiteconnect/__init__.py", line 522, in historical
"continuous": 1 if…
Here's the python traceback for reference. A call to kite.historical() was made with appropriate parameters.
============
user = kite.request_access_token(request_token=ACCESS_TOKEN,secret=SECRET)
File "/usr/local/lib/python3.5/dist-packages/…
@Sujith
I'm commenting on behalf of Vaga:
We're doing quite normal operations such as using historical data every 15 mins, doing some processing, and then sleeping and waking up again after 15 mins. We login every day in the morning, but after a …
@Vivek could you please provide some update. As a paying customer, considering you do charge us separtely for historical data APIs, we do expect some quality. As @yousuf mentioned, these are quite basic errors which IMHO, should be easy to catch at…
Hello @vivek ,
I am accessing the data through python. I requested the data for the instrument id 271363, and here's the data from the dataframe i recieved:
271363
2017-08-09 14:35:00 63.967503
2017-08-09 14:40:00 63.9675…
I am seeing the same issues. I get a NaN which messes up all my trading signals. Can someone from the KITE team recommend a minimum buffer time after which the signals can be expected to be reliable?
