New strategy template

Forums ProRealTime English forum ProOrder support New strategy template

Viewing 15 posts - 16 through 30 (of 36 total)
  • #169896

    Hi palettofix, thanks for that – your suggestion makes perfect sense. In fact I recently tried making that same change, but it gave me an unexpected result in tests so I left it with the full calculation each time – even though it looks like it should be unnecessary.

    #185900

    nonetheless

    Good morning Nonetheless, Thank you very much for this valuable contribution. I’m wondering is line 139 shouldn’t read “>=” rather than “<=”

    Thanks

    #185909

    yes, you’re right, that looks like a typo – sorry!

    This is the version of that snippet I now use – sets a max number of bars whether the position is winning or losing.

     

     

    1 user thanked author for this post.
    #185913

    I’ve no doubt it was a typo. Thanks for the update. Cheers!

    #185916

    Actually that was already corrected in the later versions – v5 for example.

    but looking at that template, the main thing I would change is the Money Management. This is the one I’m now using, although there are many others in the Snippet library.

     

    2 users thanked author for this post.
    #185918

    Please keep sharing your treasure. I learnt a lot from you. THANK YOU!

    #186179

    Hi nonetheless,

    I’m running tests on this simple strategy to better get grasp on how your BE/TrailingStop work. The code is below. It’s tested on DJ on 1 min chart (10k). The issue I’ve is after multiple runs of optimization, there are a few trades where the actual performance is way below the MFE, a few other reach a decent positive MFE and then end up negative.

    I wonder if you can give me some advice on how to reduce the difference between MFE and actual performance and how to avoid finishing red after making 30pts positive. Do you use in your live systems a sort of staged parameters for each level of profit for example (eg. if positionperf >30 and <100 then tsl = x1 and tss=y1 // if positionperf >100 and <200 then tsl = x2 and tss=y2, etc.)?

    Thanks

     

    #186187

    Hi Khaled, without looking at the actual strategy, the first thing i notice is that using breakeven with that trail is an odd choice as the % trail already has a breakeven

    (compare lines 108-115 with lines 195 – 200)

    I only use the breakeven code in conjunction with the ATR trail, which does not have that component.

    But even in that case, using besg = 0.01 would be impossible on the DJ as that would be only 3.5 points. The IG minimum is 10.

    Lastly, ts2sensitivity = 3 is also an odd choice as that means that the low of the candle has to be above the breakeven level (when long). This is the hardest combination to achieve, esp with your settings means a v long wait for the trail to start. I normally use 2, (high/low)

     

    1 user thanked author for this post.
    #186188

    esp with your settings means a v long wait for the trail to start

    actually when i wrote that, I had mistaken your tpl/tps values for tsl/tss  … but I would still recommend using ts2sensitivity = 2 (without the breakeven)

    1 user thanked author for this post.
    #186189

    Thanks for your quick feedback.

    I actually sensitivity = 3 was the result of the backtest. I kept the % trailing system only and removed all the rest. I’ll test.

    Again Thank you!

    #186190

    sensitivity = 3 was the result of the backtest

    you mean you optimized it, with values 1 – 4 ?

    #186191

    Exactly. I simulated values for tsl with ts2sensitivity (1 to 4), then tss with ts2sensitivity (1 to 4), and best result came out with ts2sensitivity = 3.

    #186731

    @nonetheless , I am learning and developing a few strategies and robertogozzi, Nicolas, GraHal have been helping me over the last few weeks. Very keen to get my strategy working on PRT and I hope to go through your template and adopt the code where relevant, test them and feedback. I appreciate that you are sharing this template to help new members.

    1 user thanked author for this post.
    #186862

    @Khaled, can you share your latest code as I am not getting the same result as your screen shots.

    #186874

    @micquan, As I mentioned in my previous post, it was a test to check and understand how the Trailing Stop shared by nonetheless works. I didn’t update this particular “simple” strategy, as I’ll not use it. If you don’t get the same results, may be you didn’t use same TF or not same dates (start/end) or may be you picked the Dow 1pound, while I used Dow 1 euro. The idea behind my post was to understand why there is a big gap between actual performance and MFE and nonetheless explained that I was using two times breakeven system together with inappropriate choice of ts2sensitivity option.

    Happy to discuss further and/or to help testing an idea.

Viewing 15 posts - 16 through 30 (of 36 total)

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