1) Tick data for datetime.datetime(2020, 7, 14, 9, 56, 1) is duplicated. Can this duplication be avoided or else I will have to write logic to detect and then ignore duplicated data from websocket feed?
2) Tick data for datetime.datetime(2020, 7, 14, 9, 56, 3) is missing. Is this expected? If this discrepancy is from the exchange itself, can we assume universally no one got access to tick data for datetime.datetime(2020, 7, 14, 9, 56, 3) for RELIANCE?
The way it works is if there is a change in the data the exchange has published then Kite Ticker will broadcast the same. So there is nothing wrong here. You can also go through this thread once.
The way it works is if there is a change in the data the exchange has published then Kite Ticker will broadcast the same.
@sujith - Could not understand your reply clearly. I went through the thread link. Quite helpful. What I understand by reading it is, - KiteConnect is giving 1 sec snapshot data using couple of ticks per second when you do ws.subscribe([738561]).
1) Now in this 1 sec snapshot result, there could be a duplication of timestamp as you might have captured multiple tick data points. And you are giving it all in API call and not discarding any data as the price of the instrument in these duplicated timestamps may differ? Is this understanding correct?
2) I still could not understand how a timestamp like datetime.datetime(2020, 7, 14, 9, 56, 3) can be missing above. Is this a failover scenario where Kite Connect could not fetch 1 sec snapshot data from the exchange?
@mlearner, It is the pub-sub mechanism wherein the publisher(exchange) publishes the data and we receive data and forward data to all the Kite Ticker subscribers. The timestamp is a data associated with the tick by the exchange and not appended by us. Like Nithin has mentioned in the above thread it is not possible for any platform to receive all the ticks over the internet.
For an illiquid instrument, you may receive only one or two ticks a day or no tick at all.
You will have to be co-located at the exchange to get all the ticks. You can write to kiteconnect(at)zerodha.com someone from our team will get back to you if you are interested in that. It costs around 18lakhs+/annum for the setup.
You can also go through this thread once.
1) Now in this 1 sec snapshot result, there could be a duplication of timestamp as you might have captured multiple tick data points. And you are giving it all in API call and not discarding any data as the price of the instrument in these duplicated timestamps may differ? Is this understanding correct?
2) I still could not understand how a timestamp like datetime.datetime(2020, 7, 14, 9, 56, 3) can be missing above. Is this a failover scenario where Kite Connect could not fetch 1 sec snapshot data from the exchange?
It is the pub-sub mechanism wherein the publisher(exchange) publishes the data and we receive data and forward data to all the Kite Ticker subscribers.
The timestamp is a data associated with the tick by the exchange and not appended by us. Like Nithin has mentioned in the above thread it is not possible for any platform to receive all the ticks over the internet.
For an illiquid instrument, you may receive only one or two ticks a day or no tick at all.
You will have to be co-located at the exchange to get all the ticks. You can write to kiteconnect(at)zerodha.com someone from our team will get back to you if you are interested in that.
It costs around 18lakhs+/annum for the setup.