Simple Moving Average Crossover Strategy

Forums ProRealTime English forum ProOrder support Simple Moving Average Crossover Strategy

  • This topic has 95 replies, 12 voices, and was last updated 1 year ago by avatarCRISRJ.
Viewing 15 posts - 46 through 60 (of 96 total)
  • #190799

    Price distance can be set at 2 points with SP500 with a clear conscience.

    #190800

    There are different versions of Roberto’s Trp. I used the version on page 4 (rif: 165976): https://www.prorealcode.com/topic/breakeeven-trailing-profit/page/4/

    Roberto, is there a better one for this TS?

     

    #190811

    Is there a reason why you define TP and SL outside of the if block? Is this better from the encoding or just a coding style?

     

    #190812

    looks interesting, thanks for sharing.

    I tried reworking it on 1m bars but it’s fairly dead before 2018, so here’s a quick treatment on a 5 year backtest. Attached are results for yours and Mauro’s for that same period and you can see that they’re curve-fit to 200k

    SP 5m T4 Multi v4.1 is with Roberto’s trail, but I didn’t change any of the values from Mauro’s version, so that could be worth playing with.

    More room for improvement, I’m sure

    #190817

    itfs

    #190820

    It’s just a coding style, I think the code remains cleaner.

    #190821

    here’s the code for mine, so you can see the changes

     

    #190822

    Thank you for your work. I’ll compare in peace. But it is interesting to see that a suitable system is created with simple indicators without much magic. I think the “problem” with the Roberto Trail is that it uses points instead of percent. I suspect. And that before 2018 the S&P500 was worth half what it is today. Of course, the fluctuations were much smaller than today. 

    #190823

    the Roberto Trail is that it uses points instead of percent

    this version has a % option:

     

    #190824

    Which do you prefer? This one (Robertos) or your own, which I also use? Both of which are by Roberto in terms of construction. 

    #190825

    I mostly use this one (above) – has a few more options and usually gives better results. I added a separate TrailStartShort as it often helps to have different values there.

    #190826

    I have found that separate trailing for long and short is important. But the steps must also be separate. Short trades usually have to be secured faster than long trades.

    #190839

    Thanks for sharing nonetheless

    Agree with you that % is better than fixed.  Given the change in index value over the last 2 years I tend to optimise over a more recent data set to have something more relevant going forwards.

    #190855

    I once again looked at my original version and installed lightweight filter …
    In the H4 time frame I installed a new noTrade-filter that should prevent the strategy enters a covered or oversold market. In addition, I added an entrance timer who should find out if there is a better price after the Ma-Cross.
    All small changes, but … more Profit, Smaller Drawdown.

    1 user thanked author for this post.
    #190862

    I expect you’ve decided that you don’t really care what happened before your test period, but just in case you’re curious:

Viewing 15 posts - 46 through 60 (of 96 total)

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