Hi GraHal
yes it’s a new approach in testing and I just picked a new version number to start off.
I don’t like to share it because it could be garbage but I can explain a bit more my effort.
A few posts back I mentioned that it could be out of sync when restarting a system or manually taking profit.
Not only that, I experienced it live, taking profit (small in hindsight), restarting the system and then it bought on a new signal on the very top before a drop and voila exit on stoploss. It would have been better to have let the original position running on trailing stop but then you wouldn’t have seen the bad buy signal on the top.
I wanted to see action on every signal. If in long position and get a signal in the same direction, close it regardless profit or loss and restart it again instantly.
Maybe that sounds wrong, but it gives different importance to every signal. The original code has be adapted a little not have many signals in a very short timeframe. The end result is a combination of pingpong between signals between 0800 to 2230 and the last position carried over to next trading day. The results in the pic are only less then 70 lines of code.
So it’s this approach above or separating long and short and still applying concept above, with normal exit-criteria like a ts and close & re-enter on same signal.
