Discussing the strategy VECTORIAL DAX (M5)

Forums ProRealTime English forum ProOrder support Discussing the strategy VECTORIAL DAX (M5)

Viewing 15 posts - 991 through 1,005 (of 1,261 total)
  • #147998

    Hi Fifi, that concept can be expanded in multiple ways.

    with above example, i.e. when lowest[barindex-tradeindex](close) was below another line, which means there was a fast run-up where you prevent buying near the top. If prevented buying on the top, it could still be considered to close a short position.

    Also for exits, although then it’s best to have the code below the entry , something like this

    Although all this would not give a greater equitycurve, maybe if programmed well could results in an algo with a smaller stoploss like 0.5 to 1%.

     

     

     

     

    #148004

    Hi Paul,
    I will test.
    Lowering the SL A 1 is good, I don’t think underneath.

    #148032

    i’am was optimistic 🙂 lowering it to 1% would be nice for this timeframe. For now I keep it for testing at 2%.

    I did had a look at the reversal exit code.

    While I splitted short in 3 sections, there are all the same.

    The problem was long which didn’t work before, there splitting worked. Ofcourse all curvefitting after the fact.

    It’s not robust, because i.e. slippage & high spread could influence this too. But I always like to try something new even if it fails.

    The idea; if the position doesn’t gain ground after opening,  the criteria for the range is lower which increases the chance for an early exit.

    Also a gap rewrite.

     

    3 users thanked author for this post.
    #148058

    That looks promising 🙂

     

    Can you update us with the .itf file @Paul? 😉

    #148075

    This setup is working very unklucky the last 7 days. Every time switching the position on low/high and turn into the other side. 9 SL in a row is not normal for that strategy. Hope it will work  better the next days.

    Attached the new itf.

    #148086

    @Tanou not as this moment, the posted v5b is fine.

    #148088

    Hi, I have added a routine that close position if loss or profit aftert X bar and I have optimize the variable longexit (for reversal)…it seems to have some improvement. Thanks

    #148091

    funny, by mistake I’ve loaded up v5p on the dax 10s

    with these settings ;

     

    #148094

    @Paul

    Its 10s yes, but on DJ, not DAX right?

    #148095

    @Paul

    Its 10s yes, but on DJ, not DAX right?

    It´s DAX

    #148096

    no loaded on the dax 10s, the dj version for 3 min v3p5

    #148097

    Interesting Paul! If one were to optimise this strategy weekly / monthly, which parameters would you then optimise? I had a pretty bad week recently and wondering if it would be better to run it with weekly / monthly optimisations?

    #148107

    @volpiemanuele, thanks for all yours algos. I launch the DJ-3m-Vectorial-V3p5_v1, but it crashed.

    #148127

    Hi @Paul, shouldn’t the code:

    (range>(close/1000)*minrangedist– or range[1]>(close[1]/1000)*minrangedist– or range[1]>(close[1]/1000)*minrangedist–)

    be

    (range>(close/1000)*minrangedist– or range[1]>(close[1]/1000)*minrangedist– or range[2]>(close[2]/1000)*minrangedist–)

    on all occurences (–) in the code you posted?

    #148146

    @Nicoeni1: I was wrong to share the file … this is the correct one that I also use in real. Thanks

    1 user thanked author for this post.
Viewing 15 posts - 991 through 1,005 (of 1,261 total)

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