If you’re using MTF, which other TF apart from Daily are you referring to?
it’s daily with updateonclose and daily without updateonclose as a test. The question is how do we get a trailingstop working in 1 daily candle, where then entry & exit are in that same bar? (and without going to lower timeframes).
How would the code be written for Renko ML1 to actually self optimise and try out and step through those 5 values in lines 95 to 110? I can’t picture it.
So those values in those lines 95-110 you put in manually you found in the optimisation sheet. On a 5s timeframe you could daily add 1 or 2. The engine start which valuex which uses that specific boxsize for l&s. If results are good it should stick to it, if not it should take another valuex which has 2 other boxsizes assigned, so it cycles to those 5 or more numbers from valuex. 2ML is better obviously but still I find above interesting.
Good to see work started on ML3. We got ML working in a backtest as graph showed, have you seen a difference trying live with and without 2 ML engines?
