Why Nifty Bank ticks have 1 second resolution?

Developer API
1

2024-12-12 12:04:56,231 - DEBUG - on message message{‘type’: ‘live_feed’, ‘feeds’: {‘NSE_INDEX|Nifty Bank’: {‘ltpc’: {‘ltp’: 53287.1, ‘ltt’: ‘1733985296000’, ‘cp’: 53391.35}}}, ‘currentTs’: ‘1733985296229’}

2024-12-12 12:04:56,831 - DEBUG - on message message{‘type’: ‘live_feed’, ‘feeds’: {‘NSE_INDEX|Nifty Bank’: {‘ltpc’: {‘ltp’: 53287.9, ‘ltt’: ‘1733985296000’, ‘cp’: 53391.35}}}, ‘currentTs’: ‘1733985296829’}

2024-12-12 12:04:57,130 - DEBUG - on message message{‘type’: ‘live_feed’, ‘feeds’: {‘NSE_FO|67074’: {‘ltpc’: {‘ltp’: 879.1, ‘ltt’: ‘1733985294936’, ‘ltq’: ‘45’, ‘cp’: 847.25}}}, ‘currentTs’: ‘1733985297129’}

I have highlighted the relevant log in bold.

The ticks for Nifty bank have 1 second resolution. Last three digits of ltt is always zero. Why is it so?

But for Nifty Bank options, ltt has 1 millisecond resolution.

2

Thank you for bringing up this question. We will consult with the concerned team and get back to you.

3

@Pradeep_Jaiswar do we have an update for this?

4

@Pradeep_Jaiswar Do we have an update?

5

Hi @Kislay,

We are checking this internally and will get back to you with an update soon, thanks.

6

@Kislay an index is not a directly tradable entity, so the LTT fields for the index are not significant. However, to maintain consistency and generate chart data, we use a 1-second resolution.

For tradable scripts, the LTT is derived from the exchange is accurate.

7

@Pradeep_Jaiswar understandable. But currently two ticks per second are sent as can be seen in the log above. and two ticks have same ltt, if we want to save ticks, we would lose half of ticks as two ticks have same ltt.
if the ltt can have 0.5 second resolution since two ticks are sent per second, that will solve this issue.

8

I will pass this information to the relevant team, but I’m not sure if it can be modified for custom logic since the same platform is used across the system. For indexing, you can use currentTs if that helps.

9

but I’m not sure if it can be modified for custom logic since the same platform is used across the system.

Ideally, the ltt should be the time index value was captured. Each tick should have unique ltt value, I am sure this must have caused inconvenience to other API users too.

For indexing, you can use currentTs if that helps.

yes, that’s what I am doing currently.

10

@Pradeep_Jaiswar
Also when constructing ohlc candle with "currenTs’ leads to incorrect outcome. This is a major issue. Kindly get it fixed. Thanks.