Bar Discrepancy Strategy Analyzer vs Live Chart

I’ve attached two screenshots, both of the same time window today. Both use 100-volume bars.

One is from the Strategy Analyzer. The other is a standard chart. Take a second and look at how different the bar sequences are.

I’m backtesting and live-testing a strategy that measures and counts bars, so this is mission critical. I initially noticed this because the live test made different trades from the backtest.

Why does this happen, and what/how do I need to adjust, so that my backtests and live tests - using identical data series - reflect identical data?
edit: “new users are limited to one photo” so I will add the second in the thread.

The second screenshot

That’s a strange issue. I ran a quick test on my setup using MNQ and Volume 100 charts and both the analyzer and live chart aligned 100%. Enabling tick replay on either chart had no impact on their alignment. A couple of things you might want to check/try:

  1. While connected to you data feed, press Ctrl+Shift+R in your live chart to reload data. Maybe it’s displaying stale values.
  2. The x axis only shows the time. Are you sure you’re looking at the same day (I’m sure you are, but it’s worth verifying)?
  3. Is the date you’re looking at within the new contract window (to avoid any back adjusting behaviors)?
  4. What version are you running? My tests were in version 8.1.5.2, the later versions have been quite buggy.

Hey Mark, thanks for the ideas.

  1. Tried reloading historical data, no impact.
  2. Yes, same day. I re-ran the backtest for only today, and I was looking at the live chart for today, I took, the screenshots within an hour of the times on the chart.
  3. Yes, both on NQ 03-26
  4. version 8.1.5.2 64-bit

I had also tried seeing if tick replay made a difference, with the same observation as you.

I’ve attached another screenshot, running it again with the final trade (I guess) it measured for the day, and the live chart scrolled back a couple hours to the right time window, on top.

After updating to 8.1.6.2, this discrepancy seems to be fixed, for now at least.

What version was causing issues for you?

version 8.1.5.2 64-bit

1 Like