Discussion Forum

Data naturally differs between providers, there have been a lot of posts about this in the forums in the past.

Setting the same starting and ending date is not advisable and can yield interesting results. I suspect it's setting the start date to the day before, but I could be wrong. Add the datetime of the incoming data piece to your logs to see what dates the prices correspond to.

Thanks Douglas for your help. Not sure what you mean by data differs between providers! I searched the intenet for historic market data and they all show same open,close,high, and low for same day.

Not having accurate data is fundemental issue, If my algorithm is set to place order few cents above market close price, it will not work since the market close price my algorithm is getting is not accuarete in first place.

I tried to set end date 1 day after start (start date is 1/3 and end date is 1/4) and now I ma getting 3 data points!

There is an additional onData trigger that nobody knows where is it coming from. I searched all document and there is no mention of that. I wasn't sure hopw to add datetime to my log.

data[self.symbol].EndTime gives you the datetime that the incoming bar is ending on. data[self.symbol].Time is the starting time of the bar. This should tell you what days the three log outputs are from. If you don't know what day the prices are from, how can you know they are inaccurate?

Thanks Douglas for following up .. I was corellating the OHLC reported from websites and charting software to the data set prints.

I added the log you suggested and you are right! Data was starting from day eerlier. So If my start date is 1/3 and end date is 1/4, onData is called with 1/2, 1/3, and 1/4 daily bars. Not sure why 1/2 was reported since I didn't ask for it.

Anyhow, reported daily data again didn't match reported data by other sources. I guess my last hope here is to define my own data class and find an accurate data feed to interface with my custom data class.

Wish me luck!

Hi Jared. Thanks for your clarification. According to the documentaion here

https://www.quantconnect.com/docs/algorithm-reference/handling-data#Handling-Data-Data-Formats

If I set resolution to Daily, I should be expecting candlestick data similar to what finencial feeds and charting software provide. What you seem to be trying to imply is, the open price of 1/3 is not known until end of 2/1. If I understand this correctly, you are also inluding after hour stock price of all 1/2!. When I look at the function prototype od AddEquity, 

// Complete Add Equity API - Including Default Parameters:
AddEquity(string ticker, Resolution resolution = Resolution.Minute, string market = Market.USA, bool fillDataForward = true, decimal leverage = 0m, bool extendedMarketHours = false)

ExtendedMarketHours is set to false by default and sisnce I don't see it in my code as shown above, it should not include any after hours pricing.

If you believe there is an issue with the data, you should report a data issue.

However, before you do this, please see the following FAQ on why prices sometimes differ from other providers:

"QuantConnect builds our TradeBars from tick data. While doing this we filter out ticks which our vendor believes are "suspicious". These suspicious trades include ones which are rolled back, reported late, or traded via OTC markets. This makes the bars a more realistic representation of the asset price but it might vary slightly from popular web-portals like Yahoo etc. Although this results in slightly different prices we believe its more important to have realistic backtests than match Yahoo."

Long story short - QC places a heavier focus on making sure the data represents actual, tradable prices at the time of receipt than other data providers might do.