Breakeven- en trailingstop on different securities & indexes & forex

Forums ProRealTime English forum ProOrder support Breakeven- en trailingstop on different securities & indexes & forex

  • This topic has 79 replies, 15 voices, and was last updated 4 years ago by avatarPaul.
Viewing 15 posts - 16 through 30 (of 80 total)
  • #126143

    Above added as Log 206 to here …

    Snippet Link Library

    Also a Note added re the LOADS of TS in this Topic

    3 users thanked author for this post.
    #126152

    Hi,

    first a humble thanks for sharing all these cool codes!
    I’ve been looking for a suitable protect-your-money-system and have been playing around with some Money Management-, Stop Loss-, Trailing Stop-, Breakeven-, Profit Target-systems and so on. There’s a lot of topics of the same subject with similar methods and I feel a bit overwhelmed of all the information. So I figured, why not ask someone who actually knows 🙂

    So Paul and other Jedi-coders. If you would rekommend a setup of protect-your-money-system for a padawan, what would it be and why? I would love to hear your thoughts about MM, SL, TS, BE, PT and such.

    Keep up the awesome work! I hope to contribute in the future…

    #126153

    Hi Paul, thanks very much for posting this. Are these to be used in conjunction with the code you posted earlier, April 2019? or they’re designed to work independently of that?

    1 user thanked author for this post.
    #126278

    @keewee Thanks! My advise, don’t use too many things. Check if something works as you think it should work (display the lines). Only work on mm if you already have a succesfull proven code. Don’t use a big stoplos (depended on timeframe) as in live trading they will occur more frequent then in an optimised backtest. Trailing stop there are a few, like posted before which used %.  A.t.m. I prefer an atr based trailing stop. Also the atr breakeven is a nice edition. a pt is sometimes usefull. Too many things though lead quickly to over optimisation!

    @nonetheless It’s different. The ones from april use %, this one uses atr. Also the % based uses the underlaying value to make it work on different assets. Probably it can work together if there are no code overlapping, but it’s not the goal. I thought the atr breakeven would be a nice addition, but not worth of a topic so that’s why I posted it here.

    1 user thanked author for this post.
    #126280

    Thanks for the clarification, I thought that was prob the case. Going back to the underlaying code, would you mind having a look at this strategy to see if I’ve applied it correctly?

    (BTW, how does it feel to be a Jedi-Coder? sounds pretty cool to me. Personally, I’m struggling to get beyond the Jar Jar Binks level)

     

    2 users thanked author for this post.
    #126281

    It was a very cool way of saying! Still got a lot of work to do to feel like that!

    I’ve loaded up your code on the dji 5min and looking at the lines, it looks correct!

    You have trailingstop & the breakeven almost go active at the same level, which makes the breakeven not effective.

    how about increasing the trailingstop slightly and using the breakeven to reduce the stoploss?

    (optimised without spread)

    try activate ts at 0.5%, besg at 0.3 and besl at -0.3 and still >90% winchance.

    or ts at 0.5, besg at 0.3 and besl at 0.05%

    that’s also great with 97% winchance.

    #126284

    Excellent, thanks ever so much. I haven’t even begun to play with the numbers as I wanted to be sure I had it set up right (just copied in what I had) .

    And your ATR TS should also work as a variation, replacing the %TS?

    #126314

    i cannot run the code because the instruction “Graph”…may somebody help me? thank you

    #126319

    You just have to rem out any line that says graph, or graphonprice etc. For example:

     

    #126326

    And your ATR TS should also work as a variation, replacing the %TS?

    yes but i’am not too sure about the atr trailingstop combined with % Breakeven, as both have  something in common, like newsl.

    1 user thanked author for this post.
    #126334

    Hi!

    I am backtesting “Vectorial us100 v5” and want to test it on different instruments. On some instrument it runs the backtest as it should. On others it stops taking positions after a few trades or makes no trades at all.

    This is a part of the original code:
    // used for sl/pt/ (not used for ts); not to be optimized!
    // forex use 0.01; securities use 1, index use 100
    // profittargets and stoploss have to match the lines with displaysl/tp/ts set to 1
    underlaying=100

    If I for example try Forex with the setting 0.01 instead of 100 it still doesn´t work.

    “profittargets and stoploss have to match the lines with displaysl/tp/ts set to 1”
    Is this the problem and what does it mean to match the lines?

    #126373

    @OboeOpt match the lines means what it says.

    if a stoploss is x% and you have the entryprice, the red line should exactly be there where you have your stoploss. If displayed at another (crazy) level, then you need to adjust the underlaying value.

    Sometimes a strategy isn’t suitable for every market on any timeframe, because of range or volume etc.

    You can post your itf file , with info on which market & timeframe , so I can quickly look if you put in right

    1 user thanked author for this post.
    #126435

    Thanks for your answer Paul!

    I´m just experimenting with
    https://www.prorealcode.com/wp-content/uploads/2019/07/vectorial-us100-v5.0p-5m.itf

    For example gbp/usd and other Forex mini with underlaying=0.01 I don´t get any trades (no other Changes to the code).
    Same problem for stocks with underlaying=1. Works for most index with value 100.

    I use IG as broker and timeframe 5 minutes.

    #126437

    oke had a look on gbp/usd.

    to test if the core code is right, I removed ts/sl/pt etc and and just used a default small stoploss&pt.

    The core code of the vectorial dax doesn’t create a trade so it has nothing to do with the exit criteria which use the underlaying value.

    1 user thanked author for this post.
    #126438

    Ok, so there is no Quick fix to change just to scan through instruments looking for candidates where vectorial can work?

    Is there anything in perticular in the core code that does that no signal is triggered for some instruments? Just tested several Swedish stocks and didn´t get any trades.

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

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