I’m just speculating here, but it’s possible to draw a correlation between indicator code and backtest, and the final proOrder strategy code because of the call instruction.
A backtest code only allows a subset of command to be valid in its file, however, it can call an indicator code file that uses other commands, for indicators.
I guess that when a indicator is called from the backtest, only the results of the indicators returned variable’s are used in the backtest and not the different indicator only commands , however, they influence the indicator calculations.
These also, come up when you query the current version of the proOrder Strategy file.
So this could account for why the general proBuilder lauguage commands incorporate the code for indicators, and I guess it’s would be the same for screeners.
This may be why when looking back from the backtest that indicator code is invalid, but not if it’s called!
Or looking forward from an indicator and requiring other commands for the backtest.
Just a thought that came into my head while all the other comments were flying over it.
Regards
Hi druby,
Thank you for taking the time to reply.
Yep, I am noticing a similar line too, where the ProBacktest Code calls into use, an indicator or the proprietary PRT code.
This is similar to Python code, calling pandas_ta library.
Having said that, some of the code syntax errors encountered are not always in relation to that of the indicator in use.
Hence, my search for a specific ProBacktest code library.
I have yet to look into anything (Modules of the ProRealTime Platform) other than, the backtest, as this is always my first port of call when using a trading platform.
Onwards…
Please feel free to comment, its much appreciated.
NT