You could do something like below, this is the way I would pursue and initially seems to work!
I’ve not used this technique for anything myself yet but, other than using the Timeframe command, the only other way would be to multiple up values to represent other timeframes.
Though depending on the complexity of what your doing , you could run into issues or limits, here’s some:
How many multi timeframes can be used, and the mTF(s) have to be a multiple of the chart/default timeframe.
How many units needed to calculate indicator values, if default TF is small and mTF is large.
If larger amount of units used, will it exceed the tick by tick limit in backtest.
There maybe others.
PRT keeps it’s users on a short leash, don’t want them running on the grass, or get up enough speed, for when they run into the inevitable brick wall of limitations!
Also certain values most probably, need to be different for different TF’s i.e. stops and targets etc.
Maybe good to get an initial view over a number of TF’s. Then filter down to a number of TF’s covering a smaller range, or do several on narrow ranges etc.
Note, you need to set up a optimisation variable, spec at top of code.
To help us continually offer you the best experience on ProRealCode, we use cookies. By clicking on "Continue" you are agreeing to our use of them. You can also check our "privacy policy" page for more information.Continue