[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 - 136 through 150 (of 288 total)
  • #77140

    Both of my MTF Systems have been rejected with the error message attached.

    I have sent in a Technical Report. Anybody else getting this?

    #77348

    Hello Grahal,

    I hope you’re doing well.

    This was due to a technical issue which has been corrected yesterday.

    Please re-start your strategies.

     

    Best regards,

    Maria

    1 user thanked author for this post.
    #77352

    Great to hear that a report has been dealt with, even better when the outcome is successful!

    1 user thanked author for this post.
    #77486

    Hello,
    I want to code in multi timframe. 3 UT = 15 minutes and 5 minutes to confirm the trend and 1 minute to take a position.
    example AT SALE
    The system is simple if in M15 and M5: the MM100, the MM200, the MM600 and the MM100 + the daily pivot point are below the price.
    In 1 MINUTE the same conditions + the stochastic crosses down the 80.
    However, I have error messages in my coding. Prorelatime does not know the variables “MM1000” and “downtrend”.
    Thanks for your help.

     

    #77494

    SHORTONMARKET cannot be used how you have used it – are you trying to say:

    SHORTONMARKET is a condition. If you have a short trade open then SHORTONMARKET = true otherwise it equals false.

    #77565
    Abz

    if you are using a 30 min or 15 min strategy and want to check the trailing stop on a 1 min basis , how to do that?

     

     

    #77568

    You are doing right, provided your current chart is set on the lowest TF you are using and all TF’s are multiple of the lowest one.

    Lines 25 and 38 are not necessary; you need to write the keyword TIMEFRAME only when you want to use a different one from the previous.

    #77569

    This is how it should look – and then run your strategy on a 1 minute chart. If decisions are made further up in the code on conditions and values found on slower time frame charts such as the 15 and 5 that you mention then the code for those will need to be put under TIMEFRAME(15 minutes,default) etc (or updateonclose instead of default if you want on the fly values/conditions).

     

    #77571
    Abz

    ok thanks for info , but then the backtest Would be on very little data  when setting the chart to 1 min.

    #77573

    Yes, the lower the TF used, the less data history you have!

    #77574

    I suggest using sort of a template like this:

    you develop and probacktest your strategy on a 1-hour TF, thus granting you more data. When you are ready to launch it, switch to a 1-minute chart and run it without backtesting (you could backtest it, but results would be much different!).

    This way you do not need to change your code, since ProOrder will assign the current TF on the chart to DEFAULT timeframe, initially 1 hour to develop it, then 30 minutes, 1 minute or whatever (provided all TFs used are a multiple of the lowest one, you wouldn’t be allow, say 25 or 7 minutes).

     

    5 users thanked author for this post.
    #77756

    Just updated the documentation with the new automatic trading specific TIMEFRAME instruction: TIMEFRAME (ProBacktest / ProOrder)

    2 users thanked author for this post.
    #77769

    Hello, is it possible to use the Multiframe to manage the trailing stop code?

    #77770

    Yes of course. Just like the example I made in the documentation TIMEFRAME (ProBacktest / ProOrder) with a 1 hour strategy but with a position management made in the 1 minute timeframe.

     

    #77772
Viewing 15 posts - 136 through 150 (of 288 total)

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