[beta-testing] multi timeframe support for automatic trading, ideas are welcome!

Forums ProRealTime English forum ProOrder support [beta-testing] multi timeframe support for automatic trading, ideas are welcome!

Viewing 15 posts - 151 through 165 (of 288 total)
  • #77788
    #77878

    Hola together,   this is probably a MTF system for which I need some help from you. Pls find more information attached Rgds Marc

    P.s.: there is already a thread within this forum for this idea I’ve opened yesterday

    #77987

    Offline

    Ok, but i tried with a Daily code like Pathfinder Swing, and using the Timeframe 1h for the trailing stop funcion, PRT said that the the all the timeframes should be multiplies of the main TF.

    #77989

    Yes, they need to be multiple of the main timeframe, which is the lowest one, the one you choose to launch your strategy.

    If you use the daily TF, you are allowed to launch it from a 1-hour chart.

    If you are using Daily+1-hour TF you will not be allowed to launch your strategy from a 4-hour chart because it’s not the lowest TF,

    If you are using 4-hour TF + 15-minute TF you won’t be allowed  to launch your strategy from a 10-minute because 15 is not a multiple of 10, in this case use 5 minutes instead, or change 15 to 30.

    #78355

    BARINDEX always keeps track of the bars in the lowest TF (the one used to launch a strategy, or default TF), so we need to set up variables to count bars on higher TFs as time goes by.

    To avoid this overhead I suggest that, mirroring the TIMEFRAME syntax, also BARINDEX accepts a TF within parenthesis, like:

    and that referencing past bars would still be allowed:

     

    #78548

    It would be nice if we could optimize the time frame. For example:

     

    #78717

    Ok, but results are not the same, i tried to use a 4h strategy in a 30m Timeframe, at the beginning of the code i’ve wrote

    so the strategy should work exactly as a 4hr TF but not, doesn’t happened and results are totally differents, can i post the code?

    #78719

    can i post the code?

    That would be helpful – every problem can be solved with the maximum amount of information! 🙂

    #78720

    Ok, let us take the Pathfinder Code of the Eur/Usd

    BARINDEX always keeps track of the bars in the lowest TF (the one used to launch a strategy, or default TF), so we need to set up variables to count bars on higher TFs as time goes by.

    To avoid this overhead I suggest that, mirroring the TIMEFRAME syntax, also BARINDEX accepts a TF within parenthesis, like:

    and that referencing past bars would still be allowed:

    i think is the problem that i found with the code like pathfinder, but if i change the Barindex as you said there is a sintax error:

    diff-ts

    #78732

    Gianluca, I don’t understand what use is my post for your startegy. Mine were jus suggestions for PRT, what’s wrong with your code?

    You are uning 1 TF (4 hours), not MTF.

    If you want to make it MTF, what TFs would you like to run it?

    #78747

    with: timeframe (4h, default)

    Your strategy has a different behavior than using it without the timeframe instruction in a 4 hours timeframe. “Default” means that the code is read at Close of the timeframe you launch the strategy on.

    #78845

    In order to use the MTF in a trailing stop like using a strategy 4h and a trailing stop code every 30 minutes, we have to launch the default code (originally from 4h) in the 30m TF, then use the function

    Right? First of all i tried to compare the behavior of the sistem (the code i posted) to see if it work in the same way but it didn’t.

    If i launch a code (originally 4h) in the TF 30m or 1h… and i use the function “timeframe (4h)” that should work in the same way of the originally 4h no?

    #78855

    You must put

    and then run the strategy on a 30 minute chart.

    #78889

    You must put

    and then run the strategy on a 30 minute chart.

    yes, and the code of the 4hrs should work normally like in the 4hrs right? and if it doesn’t? should be a bug right?

    #78912

    yes, and the code of the 4hrs should work normally like in the 4hrs right? and if it doesn’t? should be a bug right?

    or it could be that you are not using the correct setting DEFAULT or UPDATEONCLOSE.

    UPDATEONCLOSE will only change the 4 hour codes values, conditions being met etc when the 4 hour candle closes.

    DEFAULT will change them when the candle closes in the timeframe that you are trading on.

Viewing 15 posts - 151 through 165 (of 288 total)

Create your free account now and post your request to benefit from the help of the community
Register or Login