Heiken Ashi/line break bars issue

[rdaune]

Hello,

I am using since a few the Heiken Ashi indicator, with linebreak bars.
But I noticed an issue that impeaches me to use it correctly in my trading :
If I let a few bar plotting, then "reload all historical data", the new bars are different, generating different signals. And it does that all day long.

Any idea to have more stable bars?

Thanks a lot.

[NinjaTrader_Bertrand]

Hi rdaune, thanks for the post here - what broker / data feed providers are you using in your setup please?

[rdaune]

Hi Bertrand,

My broker is Mirus Futures and the technology is Zen-Fire.
All the other charts are always correct.

Thanks

[NinjaTrader_Bertrand]

rdaune, thanks for the info - looked into and unfortunately this is typical and expected for the 3 LineBreak chart that you use as base.

To get as close as possible realtime vs reload / historical behavior from those, please use a 1 Tick interval as base.

[rdaune]

Thank you so much, I am going to try it.

[rdaune]

Hi Bertrand,



I tried it the whole day with the parameter set to 1, same issue, chart is always changing if I reload historical data. I cannot trade.

Look at the screenshots please.

Thanks

[NinjaTrader_Bertrand]

rdaune, this would still be a 13 tick chart as base, correct? Anything other than a 1 tick chart will show unfortunately differences when reloaded after the fact.

[rdaune]

Well, yes it's a 13 ticks chart.
But why give the opportunity to load charts bigger than 1 tick if it does not work?
Don't tell me please that we can only load 1 tick chart? These are completely unuseful...

Anyway, thanks for your answers.

[NinjaTrader_AdamP]

rduane,

These charts do work, however since they are time independent there is no fixed time scale to reference. There are a variable number of ticks per minute which is why plotting 13 ticks cannot be specifically scaled to time intervals. Time independent charts are sensitive to the initial starting point as a consequence. This is inherent in all time independent charts and is expected behavior.

I would suggest loading your chart with its starting point as the exact same date/time and it should alleviate some of your issue here.