Jump to content
  • 0

Streaming - remote date of tick data not synchronised with local date


Marcipops

Question

I am using Lightstreamer to stream tick data: https://labs.ig.com/streaming-api-reference

There is an issue when receiving ticks through midnight as you can see from this data extract below.

UPDATE_TIME Publish time of last price update (UK local time, i.e. GMT or BST)
BID Bid price
OFFER Offer price

 

23:59:40 7317.9 7321.9
23:59:41 7317.7 7321.7
23:59:42 7317.4 7321.4
23:59:48 7317.1 7321.1
23:59:52 7317.4 7321.4
23:59:59 7317.2 7321.2
23:59:59 7317.1 7321.1
23:59:59 7317.2 7321.2
00:00:00 7317.1 7321.1
00:00:00 7316.7 7320.7
00:00:01 7317.2 7321.2
00:00:01 7317.1 7321.1
00:00:01 7317.2 7321.2
00:00:01 7317.1 7321.1

For each tick, I am recording the date of each tick from my local clock, so I can know the exact date time of the tick.

The data marked in amber is being labelled by my program as belonging to the same date as the data in black, when it should be labelling it belonging to the next day.  From this, it seems that like my local clock is a couple of seconds behind the ig clock.

For example tick data received with UPDATE_TIME = 00:00 is for the next day, but is being recorded as the same day by my program using current date from local clock.

I was therefore looking on labs.ig.com for a way of obtaining the date of the tick message, so I could record the ig date of the tick against its time.  But that approach would have a problem if the date changes after fetching the date and before collecting the tick.

Presume the opposite is also true, someone's local computer clock might be ahead of ig. Therefore with the extract above, incorrectly labelling the tick received at UPDATE_TIME = 23:59:40 with the date of the next day.

This could be completely resolved of course if the tick data had date as well as time.

Is there a workaround?

Many thanks

Link to comment

3 answers to this question

Recommended Posts

  • 0
20 hours ago, Marcipops said:

I am using Lightstreamer to stream tick data: https://labs.ig.com/streaming-api-reference

There is an issue when receiving ticks through midnight as you can see from this data extract below.

UPDATE_TIME Publish time of last price update (UK local time, i.e. GMT or BST)
BID Bid price
OFFER Offer price

 

23:59:40 7317.9 7321.9
23:59:41 7317.7 7321.7
23:59:42 7317.4 7321.4
23:59:48 7317.1 7321.1
23:59:52 7317.4 7321.4
23:59:59 7317.2 7321.2
23:59:59 7317.1 7321.1
23:59:59 7317.2 7321.2
00:00:00 7317.1 7321.1
00:00:00 7316.7 7320.7
00:00:01 7317.2 7321.2
00:00:01 7317.1 7321.1
00:00:01 7317.2 7321.2
00:00:01 7317.1 7321.1

For each tick, I am recording the date of each tick from my local clock, so I can know the exact date time of the tick.

The data marked in amber is being labelled by my program as belonging to the same date as the data in black, when it should be labelling it belonging to the next day.  From this, it seems that like my local clock is a couple of seconds behind the ig clock.

For example tick data received with UPDATE_TIME = 00:00 is for the next day, but is being recorded as the same day by my program using current date from local clock.

I was therefore looking on labs.ig.com for a way of obtaining the date of the tick message, so I could record the ig date of the tick against its time.  But that approach would have a problem if the date changes after fetching the date and before collecting the tick.

Presume the opposite is also true, someone's local computer clock might be ahead of ig. Therefore with the extract above, incorrectly labelling the tick received at UPDATE_TIME = 23:59:40 with the date of the next day.

This could be completely resolved of course if the tick data had date as well as time.

Is there a workaround?

Many thanks

Hi @Marcipops,

Feel free to reach out to webapisupport@ig.com for API support.

All the best - Arvin

Link to comment
  • 0

Hey ArvinIG,

No answer yet from webapisupport@ig.com

Interestingly https://www.ig.com/en/trading-platforms/trading-apis/how-to-use-ig-api says "Effective API use requires previous development or coding experience. However, we do have a team of experts ready to help you."
 

So I also tried support@ig.com.  But they said

"As we do not provide programming support for API related issues, you should follow the data timings provided by our API.
If you have any further queries, please do not hesitate to contact us. Alternatively, we've recently launched our new Help & Support site which gives you answers from our huge knowledge-base, online community, and education hub."

So ending up back here again - IG is as much help so far as a chocolate fireguard....

(I understand Pepperstone have solved this issue by including the date in their tick stream.)

Edited by Marcipops
Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • General Statistics

    • Total Topics
      21,664
    • Total Posts
      91,989
    • Total Members
      41,954
    • Most Online
      7,522
      10/06/21 10:53

    Newest Member
    Lassim
    Joined 29/03/23 23:16
  • Posts

    • Stock Market Content: SP500, Apple (AAPL),Tesla (TSLA), Amazon (AMZN), Nvidia (NVDA), Microsoft MSFT, Berkshire Hathaway (BRK/B), Block, Inc (SQ), Meta Platforms, Netflix (NFLX), Enphase (ENPH), Alphabet GOOGL and Bank of America BAC. Stock Market Summary: NASDAQ 100 to 13,000 Apple to 165, so in a nutshell Another new high for most stocks, that said, this next new high is being viewed as Wave v) top. Elliott Wave Analysis: Wave v) Trading Strategy: On the long side for a good few sessions Video Chapters 00:00 SP500 / NASDAQ 100 10:13 Apple (AAPL) 13:40 Amazon (AMZN) 17:32 NVIDIA (NVDA) 18:29 Meta Platforms (META) 19:28 Netflix (NFLX)  22:00 Enphase (ENPH) 26:02 Alphabet (GOOGL)  30:31 Microsoft (MSFT) 32:04 Berkshire Hathaway (BRK.B) 33:22 Tesla (TSLA) 35:40 Block Inc. (SQ)  38:08 Bank of America BAC 41:21 Thanks for supporting Analyst Peter Mathers TradingLounge™ Australian Financial Services Licence - AFSL 317817 Source: tradinglounge com  Level Up - Test the Trial Service!  
    • #EURJPY: Detailed Structure AnalysisHere are my latest structure analysis for ⚠️EURJPY.Support 1: 138.80 - 139.25 areaSupport 2: 137.38 - 138.18 areaResistance 1: 143.19 - 143.6 areaResistance 2: 145.00 - 145.58 areaResistance 3: 146.40 - 146.7 areaConsider these structures for pullback/breakout trading.
    • #USDCAD: Important Breakout   USDCAD broke and closed below a solid horizontal demand cluster on a daily. The broken structure turned into resistance now.   Probabilities will be high to see a bearish move from that. Goals will be 1.356 / 1.346 For Additional confirmation use: the best mt4 indicators
×
×
  • Create New...