Strategy DayOpen Straddle for DAX

Forums ProRealTime English forum ProOrder support Strategy DayOpen Straddle for DAX

Viewing 15 posts - 106 through 120 (of 242 total)
  • #86208

    thanks vonasi
    and thanks to you Paul
    eugenio

    #86312

    Thank you Paul for this great strategy !

    I noticed that the months of July and August are performing badly and i would like to add something in the code to exclude trading during these months, each year.

    Could someone help me with writing the lines of code needed to do that ? I have tried a few things but i am not able to make it work.

    Thanks !

    #86314

    Hi,

    Just replace the existing part with this.

     

    1 user thanked author for this post.
    #86315

    Works fine, thank you !

    #95107
    reb

    Hi

    I’ve just found this topic about an interesting strategy,

    is somebody using it ?

    Reb

    #95223

    I am using it for DAX and also Brent Crude 1 min since the 8th March and its working really well

    #95231

    Which code are you using for brent crude 1min? Could you please share to check?

    Or just the same code implemented on 1min?

    I am using 3min for DAX in demo live since last 21st march and working well. Some cancelled orders sometimes but these are demo live issues, not real live I think.

    And of course thanks to Paul for the strategy!!!

     

    #95275
    reb

    @Ruark Baker

    on Brent 1m , what an interesting idea

    Did you also test on other assets ? (just to avoid to check)

    #95289

    I tried all the major indicies and commodities, this was before I had a system for testing so it’s not written down. From memory it worked well on euro50 and MIB but the MIB drawdowns would have been too high for me to run at present, the code I am currently using is:

     

    3 users thanked author for this post.
    #95330

    Ruark Baker – please use the ‘Insert PRT Code’ button when posting code in any future posts as it makes it far easier for others to read. I have tidied up your post for you. 🙂

    #95422

    Hello Paul,

    Great Idea with the code and thanks for sharing.
    I had a little time to look into your code.
    I might have spotted a mistake for your MFE Trailing Stop calculation

    tradeprice(1) – maxprice > trailingstop instead of maxprice – tradeprice(1)
    You want to start trailing from the moment you have a certain profit level if I am correct.

    Furthermore I dont know what the Williams Trailing is doing. Maybe I just dont understand it.
    But it seems to make no difference whether it is activated or not.

    Kind regards

    1 user thanked author for this post.
    #95430

    @O-jay8 Thanks for the critical look. I’ve no idea where you found that, but you are correct.

    The goal of the wbar 3 trailing stop was not to use an optimized profittarget and a minimal loss of maximum profits.

    This doesn’t have an effect if you use a short timeframe like 1 minute. But i.e. 3 minute it makes a difference.

    It’s not huge, but just a bit better exit points.

    downside with a default trailing stop is that you may surrender some nice points,  but upside is you can get bigger profits.

    upside with a williams 3 bar trailing stop is that get you out of a trade at a fairly good price….at the time, but downside here is you can miss out on bigger profits.

     

    While it’s a williams 3 bar trailing stop, testing it to 4 or 5 can be usefull.

    https://www.prorealcode.com/prorealtime-indicators/williams-3-bar-trailing-stop/

    Just add the indicator to the price-chart.

    1 user thanked author for this post.
    #98234

    Looks like the strategy works best with high volatility!! and looses with low!!

    1 user thanked author for this post.
    #98241

    Yes at the moment doesn’t work good enough! Volatility is a different angle, I will give it a look.

    Few things to consider;

    • higher chance that it doesn’t work if there’s daily gap because of zigzag at opening (and days after)
    • holiday 1 mei tag der arbeid in Germany (volatility), check the holidays and perhaps prevent trading.
    • exit-time 173000 or 223000 on Friday can make a difference. As always the biggest difference is in the most recent day!
    • main criteria uses > instead of crossover, there’s a potential of conflict. That long and short criteria are true at the same time. I use a workaround because I want to use it as is.
    • got criteria which prevent entering the market on new high or low in opposite or same direction.
    • In ways to prevent losing 1% (my stoplos which I don’t optimise on a short timeframe) I’am trying to prevent losing that number
      • when in a position and it breaks previous days dhigh/dlow to close position and not to go on hope. Basically cut losses short but without exiting too much. But there’s more to it then this but that’s the idea.
      • the concept to enter a second position when performance < -0.20% and use trailing stop on 2nd better position to close both and maintaining stoploss of 1st position. But there’re a few cave-cats so binned that idea for now.
        • (but look at Friday when exiting at 22.30. If you had bought with -0.20% and exited on TS on first or second position it would’ve been interesting again)

    All in all, it shows that you should be running more strategy’s at the same time !

    But the concept to enter the market in the first hour remains good.

     

    1 user thanked author for this post.
    #100887

    The Williams trailing stop doesn’t work because there are a couple of errors:

    1. Positionperf is quoted with 4 decimals (0.0050), while WTSMP is set to 0.50 (must be 0.0050)
    2. ref[1] because the last 2 candles must be one above and the other below the signal line “ref” in that moment.

      With these corrections the Williams ts seem to work a little better than the MFE ts

Viewing 15 posts - 106 through 120 (of 242 total)

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