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
      23,020
    • Total Posts
      95,393
    • Total Members
      43,639
    • Most Online
      7,522
      10/06/21 10:53

    Newest Member
    SenaVie
    Joined 27/09/23 22:00
  • Posts

    • Hi buddy, from my experience m, you sounded like you're setting a life goal for yourself in the crypto trading journey while some only treat it as a side gain where they only trade to make some profits, but seeing your eagerness, I'll say you should take it slow and do some due research.  You can try copy trading, it seems people make a lot from it following experts' trades. Please ensure you do your research and don't just take words from people you meet online. Be consistent with your savings of profits and see how you'll grow.
    • Lam Research Corp., Elliott Wave Technical Analysis Lam Research Corp., (LRCX:NASDAQ): Daily Chart, 27 September 23 LRCX Stock Market Analysis: Looking for upside into wave {v} as we seem to be near the end of the correction into wave {iv}. We could find support on the base channel before turning higher.   LRCX Elliott Wave Count: Wave (c) of {iv}. LRCX Technical Indicators: Between 20 and 200EMA.   LRCX Trading Strategy: Looking for longs into wave {v}. TradingLounge Analyst: Alessio Barretta         Lam Research Corp., LRCX: 4-hour Chart, 27 September 23 Lam Research Corp., Elliott Wave Technical Analysis LRCX Stock Market Analysis: Looking for wave (c) to end within equality and 1.618 (c) vs.(a). We can also look at the current RSI divergence we are seeing.   LRCX Elliott Wave count:  Wave v of (c). LRCX Technical Indicators: Below al averages.   LRCX Trading Strategy: Looking for longs into wave {v} after upside confirmation.
    • AUDJPY Elliott Wave Analysis Trading Lounge Day  Chart, 27 September 23 Australian Dollar / Japanese Yen(AUDJPY) Day Chart AUDJPY Elliott Wave Technical Analysis Function: Counter Trend Mode: impulsive Structure: blue wave 3 of C Position:  black wave C Direction Next lower Degrees: wave (3 of C) continue Details: blue corrective wave 2 looking completed at 96.083.now blue wave 3 started and strong move expected . Wave Cancel invalid level:96.081   The AUD/JPY Elliott Wave Analysis on 27 September 23, examines the Day Chart of the Australian Dollar/Japanese Yen (AUD/JPY) currency pair. This analysis utilizes Elliott Wave theory to provide insights into potential market trends and price movements.   The analysis identifies its Function as "Counter Trend," indicating a focus on identifying and interpreting market movements that run contrary to the prevailing trend. In this context, "counter trend" suggests an emphasis on potential reversals or corrective movements within the market.   The Mode is characterized as "impulsive," which implies an anticipation of strong and directional price movement. Specifically, the analysis expects an impulsive wave sequence within the market, suggesting the potential for significant and decisive price shifts.   The Market Structure is described as "blue wave 3 of C." This highlights the importance of the third wave within a broader C-wave structure in the Elliott Wave sequence. It signifies that the analysis is centered on the development of this specific wave.   The Position specifies that the analysis pertains to "black wave C," indicating that the entire C-wave structure is of interest in the analysis. This means that the broader context of the C-wave is taken into consideration.   The Direction Next Lower Degrees points to "wave (3 of C) continue," signifying that the analysis is focused on the continuation of the third sub-wave within the larger C-wave structure.   In the Details section, it is observed that "blue corrective wave 2" is deemed to have completed its course at the level of 96.083. The market is now in the phase of "blue wave 3," and a strong price movement is expected as part of this impulsive phase. The "Wave Cancel invalid level" is specified as 96.081, serving as a reference point for risk management and potential trade entry points.   In summary, the AUD/JPY Elliott Wave Analysis on 27 September 23, suggests that the market is currently undergoing a counter-trend phase with an anticipated impulsive price movement in the form of "blue wave 3 of C." Traders are advised to closely monitor this wave for potential trading opportunities, with the specified invalid level serving as a reference for risk management within their trading strategies.
×
×
  • Create New...
us