Mother of Dragons trading strategy…

Forums ProRealTime English forum ProOrder support Mother of Dragons trading strategy…

Viewing 15 posts - 196 through 210 (of 523 total)
  • #129405

    Never add to a losing position

    I agree, but something I do is if I have a loser and I judge that price is going back up (vice versa for shorts) then I would buy same lot size so I get back to breakeven or very small loss in half the price distance it took to lose (and hopefully before I go to bed! 🙂 )

    Works surprisingly often!

     

    #129409

    Yes, I confess I sometimes do that too, in manual trading. Hard to resist the temptation of maybe getting out of a stinker at breakeven. I think the question you have to ask is, ‘if I didn’t have an open position, would I buy here?’ If the answer is a confident Yes, then averaging down can be a good tactic. At least manually you have full control over the extra risk. But it would take some v clever coding to get it right in an algo.

    1 user thanked author for this post.
    #129503

    Here a Dax version with BreakEven fonction, no modifications with the main MTF values

    It’s far from the original version in terms of performances i just adapted it to my needs…

    Thanks @nonetheless

    8 users thanked author for this post.
    #129512

    Here’s my adaptation to @Moda version above – with added @JuanJ ML (to adjust sl / pt) and @Paul ML (to adjust StartBreakevenLong/Short) including @Vonasi MM. Improved win rate and less losing trades.

    9 users thanked author for this post.
    #129514

    backtest results for the above.

    2 users thanked author for this post.
    #129520

    Hi eckaw,

    Im new and trying to learn to program in prc. What do I need to remove to get it working because I dont know what to remove from backtest code to make it work.

    #129541

    Here’s my adaptation

    I can’t wait until tomorrow to try these last 2 versions … even if they are only half as good as the backtest  … they should be winners!!?? 🙂

    Thank You @Moda and @eckaw for being magnanimous and sharing with us all!

    Thanks also to JuanJ, Paul and Vonasi and Nonetheless for the original MoD strategy, and Jan and Laurenzo for the original 69 MA definitions.

    1 user thanked author for this post.
    #129543

    The ML version is very interesting, also reduces all the noise of the little profit trades. What if applied on the original trailing stop version and not on the less performing breakeven one?

    #129548

    How come i get these results on  MoD-Dax-4.x ML

    look at the DD from dec 27 2019, its huuuge… just me that thinks this is not ready to live?

    #129550

    just me that thinks this is not ready to live?

    We all check out Systems on Demo Live / Forward Test for a certain number of trades / ups and downs period in price levels etc.

    Unless there are other folk like me, who like the excitement of putting a System Real Live following good backtests / walk forward etc?

    BUT I would always then watch each and every trade like a hawk and would only do above if I was sitting at my desk doing other tasks on one monitor whilst the trade develops on No 2 monitor in my peripheral vision.

    I might then exit a trade / close the System down within a few seconds or when it reaches a logical exit point which may not be  catered for by the coded strategy.

    I don’t see above as any more risky than manual trading?  But if you are not comfortable manual trading then don’t do above! 🙂

    EDIT / PS

    There’s an even bigger drawdown on 13 March … see attached.

    #129564

    my point was that it wasnt even a point in putting it on demo whit this huge drawdowns with no protection at all..

    the point of automatic systems is to not have to look at the monitor all the time.

    if u want to trade manual then just have the system as an alert?

    #129568

    with no protection at all..

    Are you able to do anything to improve the System to get it more to what you would like?

    #129569

    Hi @eckaw, I think there’s an error at line 421 – should be HeuristicsAlgo4, no?

    Also, testing should be really done with MM switched off, so line 43 needs to be MM2ndType = 0

    Nice work with the ML application, are you sure there’s no crosstalk between them?

    1 user thanked author for this post.
    #129570

    backtest results for the above.

    I do not get the same results as you with the original ML code, did you optimize more? Spread?

    #129576

    Also, @vonasi produced a more sophisticated version of that MM code, if you’re interested – includes a fuse to quit the algo if x% DD:

     

    1 user thanked author for this post.
Viewing 15 posts - 196 through 210 (of 523 total)

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