This is a problem that I encountered early on with the way SierraChart's stores its bars.
For backtesting, one typically wants the [A,B) interval or (A,B] interval covered by the bar to be designated by time B.
That way it is less likely that you will peek into the future during your backtest. At the time B, you are allowed
to observe bars labelled with B or before.
However, because SierraChart is repeatedly re-drawing the bar on the chart as it it is forming, they want to publish the bar
to the internal ACSIL DLL code with a more constant time stamp. At least this is how I rationalize the observation
that they use the "A" timestamp (beginning of bar) everywhere instead of the "B" end-of-bar timestamp.
Last edited by wzschultz; 12/05/19 01:32. Reason: grammar