I’ve thought I was losing it a few times today!
I set up a few Systems on Friday with good equity curves etc. When I tested earlier today … zero trades!
After a few tries on all TF’s from 1 min to 1 H in case my memory is failing (:) ) I put the .itf into my WIP folder.
Got mad when I thought about it, so I tried again a short while ago … still the same … zero trades!
I thought I’m not having this, so I exited and logged in again and hey presto, everything has sparked into life!
I had exited and logged in several times previously today, but got zero trades every time!
Why o Why can’t PRT have a Splash Screen with a Status Warning?
It could well be an IG data problem, in which case IG should advise PRT who could then put up a Splash Screen?
Rant over!
Anybody else had the above problem today ?
I haven’t, but showing a spalsh screen warning/notice would be beneficial!
An additional point … the zero trades Issue was on my SB Platform only as I recall.
Also I remembered on several occasions yesterday, I could not select more than 10,000 bars.
Same thing just happened again, but Close and Log back in again and 100,000 bars is now available to me … well weird!?
Yip I experienced similar chaos. Strategies that still back-tested fine on the 14th just suddenly stopped backtesting with a generic error saying “An error has occurred during execution of your ProBacktest”. Nothing changed in the code, no syntax errors nothing. So after nearly an hour of my own troubleshooting I realized that the issue was the fact that I used the variable name ‘KijunSen’ and apparently starting Friday this is now a ‘Reserved’ keyword. What I don’t understand is why would PRT do this? Anything in PRT version 11 shouldn’t affect previous versions. It’s really terrible, as I now have to update many of my PRT v10.3 strategies that contain ‘reserved’ keywords and always worked fine.
I now have to update many of my PRT v10.3 strategies
And if in Forward Test – Live or Demp – you will lose record of past performance.
I sympathise!
What I don’t understand is why would PRT do this
Some useful (NOT!) idea by some PRT techie?