Probable inconsistency in the streaming data
-
@rjbanna agreed with you we can use ltp of tvalue response to build the candle
@admin @bhaveshjain Will it not be possible to just give us the following line as tick response continuously
[{"to":"7128494980.08","lo":"1970.05","e":"nse_cm","sp":"1977.05","c":"1974.35","ltp":"1977.00","ltq":"47","tk":"2885","bs":"6","ltt":"16/12/2020 11:10:44","tsq":"955550","v":"3597688","bp":"1977.00","cng":"02.65","bq":"53","ap":"1981.41","nc":"00.13","name":"sf","tbq":"468907"}]and include the timeframe also in this response and get rid of the following data
[{"tvalue":"16/12/2020 11:10:44","name":"tm"},{"e":"nse_cm","name":"sf","ltp":"1977.05","ltq":"40","tk":"2885","ltt":"NA"}]It would make us developers life easier
If we want we can make do with the existing format as well but i don't want to work too hard on rearranging the data that i got from the API , the data should come in clean and consistent way
-
@taleevaalam1 @bhaveshjain hi bhavesh this is the issue i was speaking to you during conversation held with you, day before yesterday.
also @taleevaalam1 @rjbanna i need to ask you how many scripts data you can stream at a time cause i have subscribed for 50 scripts but i'm able to get data of only few scripts.
-
@dorje Will have to check that , you can run more than one program and divide the number of scrips among them
i.e : Run 5 programs with 10 scrips each
-
@dorje said in Probable inconsistency in the streaming data:
hi bhavesh this is the issue i was speaking to you during conversation held with you, day before yesterday.
Noted. I have asked my development team to work on the feedback shared on this post. We will keep you posted.
-
@rajanprabu Yes it would be helpful if we receive timestamp in every tick, but I don't think so it is necessary. Because if there's no tickdata from the exchange, then you won't be able to confirm whether you should complete one candle formation or not. There are many scrips in which you won't get tickdata if there is no buyer/seller. It might happen that you won't get tickdata even after 10 minutes. In this case if you are using M5 timeframe, you won't be able to know when to close your candle and this will raise many issues. So I would suggest you not to use tickdata timestamps. Create your own timer function for it.
-
@dorje I have to check. I'm using the tickdata with 4 scrips and I'm receiving quotes for all of them. I'll add more to it and let you know the outcome.
-
@rjbanna Thanks for your views. Algo trading is done on scrips which has lots of liquidity/volume. I would assume no algo trader would touch illiquid scrip that has no trades for 10 minutes. so Its mostly index and stocks listed under FnO. Algorithms are backtested using data with true timestamp from an authorised vendor. All brokers subscribe to 1 sec snapshot from NSE and relay it to the users as it is. I am using one international broker ( for US/Europe Markets ) and one large Indian broker for the same. I have always used timestamp of the ticks for making my candles.
-
@rajanprabu Yes I know, no one would choose illiquid stocks for algos but I just suggested you how you can overcome this issue for this API. As I mentioned earlier, I totally agree that every tick should get the timestamp and I also request developers to do the same. You can wait for the fix if they are going to do this or else you can use workaround.
-
@rajanprabu I don't think we should have any kind of limitations due to the liquidity of the stocks, whatever the volatility of the stock it should be treated in a same manner.
@rjbanna we should see the tick response for any non-volatile stock and then determine how the response should be
Can you guys share any token id for some nonvolatile stock
-
@taleevaalam1 You can try any commodity like copper, lead, zinc or any currency derivatives. They don't move that much.