DAX Mtf strategy using a custom trend indicator

Forums ProRealTime English forum ProOrder support DAX Mtf strategy using a custom trend indicator

Tagged: , , ,

Viewing 14 posts - 1 through 14 (of 14 total)
  • #89658

    User @Alessio posted a custom indicator on the italian forum, to tell Trending from Ranging markets (https://www.prorealcode.com/topic/indicatore-per-laterale-laterale-inclinato-trend/).

    I liked it and wanted to give it a try on DAX, 1-hour TF, with Nicolas’trailing stop code on the 20-second TF. I decided to embed the indicator in the strategy, instead of CALLing it.

    The indicators returns 1 for ranging market, 2 for sloping ranges and 3 for trending markets. I decided to enter a position (based on the direction of each candle) whenever it rises from 2 to 3.

    Performance seems rewarding:

     

    5 users thanked author for this post.
    #90863

    the trend phase, I thought only for the exit, nice trailing

     

    #184519

    Dear fellow traders,

    First, thanks to robertogozzi for this very effective trailing stop. You can see from the screenshot very little difference between MFE and exit price.

    I was impressed with the effectiveness of the indicator shared by Alessio on the Italian forum, so I called it “Da Vinci”. Thank you Alessio!

    I’m stuck with an MTF issue. I’m testing this H1 System run on 5min chart, which I’m testing only on 2k for the example. I expect the signals to be taken on the 1 hour basis. However, some of the trades are taken outside of this rule. For example, on 4 Jan. 2022 at 12:15 the System took a Long trade, while there is no Signal on the H1 chart between 11 and 13 and the Signal is Short on the 5min chart.

    Can you please help to fix this MTF issue?

    Any suggestions how to this strategy? Your ideas or comments are welcome!

     

     

    #184524

    I expect the signals to be taken on the 1 hour basis

    TIMEFRAME(DEFAULT) will read the signal from the TF you are running on (5 minute). You can either run it on 1 hour, or delete TIMEFRAME(DEFAULT)

    1 user thanked author for this post.
    #184525

    A LONG signal occurred at the 11:00 candle, which closes at 11:59, so it is valid till 12:59.

    A LONG trade was entered at 12:00 (as soon as the 11:00 candle closed) and, since it was exited quite soon, it entered another one according to the same signal.

     

    1 user thanked author for this post.
    #184526

    Thank you robertogozzi and nonetheless!

    Do you think of any filter I can add to avoid this or to improve the strategy overall?

    #184529

    Just a trade per H1 candle maybe?

    1 user thanked author for this post.
    #184535

    Thank you phoentzs

    I tried to limit to 1 trade per hour on H1/M1 TF, but results were not satisfactory.

    I kept H1/M1 and optimized Trailing Stop, Stop Loss and Exit Strategy and I now have a reasonable outcome on 5k, R/R 2.28, Sharpe 1.2, Win Rate 69% and Net Gain/Drawdown = 6.4. Now, time to test on 100k and see.

    #184539

    I am excited. I always find it very difficult to track trends on the DAX. SP500 or Nasdaq are easier there.

    #184551

    Choppy market is THE PROBLEM !

    #184565

    I know that’s why I don’t like Dax anymore. Or I’m doing something wrong.

    #184567

    I trade manually only Dow (usually directional and you can capture 50 to 100pts quickly), and I have one Algo on NQ (because usually volatile), which I tested in Demo mode for one year, it generated 500% with 1 lot and an SL of 140pts. I’m trying to write an Algo targeting moves of 200pts on Dow, but it requires large SL (200pts)… Lately, I found myself letting the NQ Algo take the trade, then manage the rest manually. The Algo does usually better than me: Psychology is key! The NQ Algo is extremly simple (39 lines), Stoch + MACD with a few filters.

    #184585

    Hello – thank you for posting this.  What time zone are you running it on, as my results are negative when I run a backtest?  I know I must be doing something wrong  🙂   Thank you

    I am testing on an IG CFD demo account, UK time zone on the NASDAQ 5m time frame

    #184587

    The last screenshot is NQ, (k units, H1/1M TF, which is different from the code I posted above (H1/M5), But when I switched to H1M5, I adapted the SL, Trailing Stop, etc. I’m running under French time zone.

    Please note the System above is meant to be an example, it’s not a finished, so please feel free to tweak it and let us know how you improved it.

Viewing 14 posts - 1 through 14 (of 14 total)

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