Strategy DayOpen Straddle for DAX
Forums › ProRealTime English forum › ProOrder support › Strategy DayOpen Straddle for DAX
- This topic has 241 replies, 39 voices, and was last updated 3 years ago by Monobrow.
-
-
07/09/2019 at 5:22 PM #102291
here’s compared only ts, only bb, both
All a bit the same result, but as you see you surrendered potential profit last day, which wouldn’t happen if both were active.
also both with safety active with 0.50; lower average loss, lower drawdown
07/14/2019 at 3:57 PM #10255707/15/2019 at 2:37 PM #102617Thanks for all, this strategy is awesome… Could anybody post the latest version of the code ?? Thanks you
07/15/2019 at 4:44 PM #10262507/15/2019 at 6:45 PM #102627Hi again guys,
what about overnight? I tried to add this king of code and it doesn’t seem to be more profitable, but maybe safer with some gap.
12345678910111213//OVERNIGHT BUYIF longonmarket THENIF time >= 210000sellshort at marketENDIFENDIF//OR OVERWEEK BUYIF longonmarket THENIF time >= 210000 and OpenDayOfWeek = 5 THENsellshort at marketENDIFENDIFWhat do you think about it?
Gregg
07/16/2019 at 12:52 PM #102665@AE as it is right know, long could get triggered fast in a downtrend.
@Pablo Jimenez latest version is already posted
@Gregg the strategy doesn’t hold a position in the weekend, which is preferable I think. It only holds overnight during the week.
Adding that code during the week, it closes a long position at 21h and takes a short one.
Safest is change 240000 to something lower so it closes each day all positions. Perhaps turn of trendsafetyexit.
1 user thanked author for this post.
07/19/2019 at 8:30 AM #102880I’m running live Dayopen straddle v4.2 with this settings// Money Management// Money Management
123456// Money ManagementCONSECNOCYCLE = 1CONSECSICYCLE = 0CUMULASICYCLE = 0traditional = 0percentage = 0A curious almost flat evolution since march 2019. And no trades for 3 days now….Paul, you can confirm?
1 user thanked author for this post.
07/20/2019 at 6:45 AM #103000Yeah the strategy didn’t produce any trades and that is good because otherwise you would’ve lost.
The reason is the main criteria which uses the Mid-Level Day indicator.
To avoid certain markets, lines have to be different from each-other and now they are not so that’s the reason no trades are produced.
123c1=(mid1day) //greenc3=(mid3day) //bluec5=(mid5day) //red1c10=abs(c1-c3) > 0 and abs(c3-c5) > 0I included the indicator below. If that is put on a price-chart and you see the same values for green and blue or blue and red it means no trades that day.
1 user thanked author for this post.
07/21/2019 at 4:17 AM #10304107/21/2019 at 12:38 PM #103060Yes there’s a new version, still working on a few question marks though.
i.e. mid level day indicator is based on 5 previous days. To make sure that there are no trades in the first 5 days of a backtest, which works on every timeframe and doesn’t influence live trading.
07/21/2019 at 5:23 PM #10307407/21/2019 at 6:57 PM #10307707/22/2019 at 9:16 AM #10309207/22/2019 at 11:29 AM #10309707/22/2019 at 1:42 PM #103102some info folks.
new version has slightly altered entry. Finally fixed the problem 100% although that doesn’t has great positive impact on results.
Problem was condition for buy could be true and at the same time short could be true.
It mattered if the code had the buy first, or the short first and that influenced results.
The challenge was to make it independed if short or long was first and that the equity-curve was at-least equal or better.
I’ve tested if every criteria is needed. So I compared the main criteria with the extra criteria (latest and first version) and check that with optimised nopl/nops.
As I found out, you can remove the extra criteria completely or just disable it. Run with nopl2 and nops6. Also removed safetyexit, ordertype and lunch.
Version will be published a bit later as I ran into a small issue live.
-
AuthorPosts
Find exclusive trading pro-tools on