Discussing the strategy VECTORIAL DAX (M5)
Forums › ProRealTime English forum › ProOrder support › Discussing the strategy VECTORIAL DAX (M5)
- This topic has 1,260 replies, 124 voices, and was last updated 1 month ago by Greger2346.
-
-
12/11/2019 at 10:10 AM #114624
Have not read the entire thread ( i will ) but enough to get the gist of it . Seems to be a lot of optimization of optomization which rarely ends well . The mother of all curve fits BUT . With just a brief look at the logic of the OP i think he has something and i would like to explore it .
Will clean up the code and get into the nuts and bolts of it , seems to be a bit of a regime filter base to it and i like that aspect . His initial curve is still pretty rocksolid and thats a decent positive after many months of OOS . Could be a good thing imo . I will be back
12/11/2019 at 10:47 AM #114628Thank you for all your enthusiasm and sharing around the original version of the code proposed by Balmora! Forks versions are inevitable and I encourage them, even if over-optimization is very often the cause of the abandonment of a project, it also allows to educate the nice programmers of automatic trading systems on this aspect which is the more important in this discipline! 😉
1 user thanked author for this post.
12/12/2019 at 2:19 PM #114743Hi everyone. Many thanks for sharing this amazing code. The v1 is running in test with very few changes and seems to work good. Indeed, seems very powerful with Dax M5. Not yet read the 39 pages…
1 user thanked author for this post.
12/15/2019 at 8:13 AM #114918Hi
i’am looking at a variation on the trailing stop used in v2.
This modification has its upside (closing in on gains & quicker profit taking) and downside (missing out on a bigger ride because took profit to quick in hindsight) .
Didn’t test it yet live and don’t know if it’s 100% correct.
This is the part which is change on the top of the trailing stop code.
12345678910111213141516171819202122232425262728293031323334once steps=0.05once minatrdist=3once atrtrailingperiod = 14 // atr parameter valueonce minstop = 10 // minimum trailing stop distanceif barindex=tradeindex thentrailingstoplong = 4 // trailing stop atr relative distancetrailingstopshort = 4 // trailing stop atr relative distanceelsif prezzouscita>0 thenif longonmarket thenif trailingstoplong>minatrdist thenif prezzouscita>prezzouscita[1] thentrailingstoplong=trailingstoplongelsetrailingstoplong=trailingstoplong-stepsendifelsetrailingstoplong=minatrdistendifendifif shortonmarket thenif trailingstopshort>minatrdist thenif prezzouscita<prezzouscita[1] thentrailingstopshort=trailingstopshortelsetrailingstopshort=trailingstopshort-stepsendifelsetrailingstopshort=minatrdistendifendifendif12/15/2019 at 8:51 AM #114921here’s it complete
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283// trailing stop atr [adjusted reset]once enablets=1once displayts=1if enablets then//once steps=0.05once minatrdist=3once atrtrailingperiod = 14 // atr parameter valueonce minstop = 10 // minimum trailing stop distanceif barindex=tradeindex thentrailingstoplong = 5 // trailing stop atr relative distancetrailingstopshort = 5 // trailing stop atr relative distanceelsif prezzouscita>0 thenif longonmarket thenif trailingstoplong>minatrdist thenif prezzouscita>prezzouscita[1] thentrailingstoplong=trailingstoplongelsetrailingstoplong=trailingstoplong-stepsendifelsetrailingstoplong=minatrdistendifendifif shortonmarket thenif trailingstopshort>minatrdist thenif prezzouscita<prezzouscita[1] thentrailingstopshort=trailingstopshortelsetrailingstopshort=trailingstopshort-stepsendifelsetrailingstopshort=minatrdistendifendifendif//atrtrail=averagetruerange[atrtrailingperiod]((close/10)*pipsize)/1000trailingstartl=round(atrtrail*trailingstoplong)trailingstarts=round(atrtrail*trailingstopshort)tgl=trailingstartltgs=trailingstarts//if not onmarket or ((longonmarket and shortonmarket[1]) or (longonmarket[1] and shortonmarket)) then//or (longonmarket and condsell) or (shortonmarket and condbuy) thenmaxprice=0minprice=closeprezzouscita=0endif//if longonmarket then//and not condsell thenmaxprice=max(maxprice,close)if maxprice-tradeprice(1)>=tgl*pointsize thenif maxprice-tradeprice(1)>=minstop thenprezzouscita=maxprice-tgl*pointsizeelseprezzouscita=maxprice-minstop*pointsizeendifendifendif//if shortonmarket then//and not condbuy thenminprice=min(minprice,close)if tradeprice(1)-minprice>=tgs*pointsize thenif tradeprice(1)-minprice>=minstop thenprezzouscita=minprice+tgs*pointsizeelseprezzouscita=minprice+minstop*pointsizeendifendifendif//if onmarket and prezzouscita>0 thenexitshort at prezzouscita stopsell at prezzouscita stopendifif displayts thengraphonprice prezzouscita coloured(0,0,255,255) as "trailingstop atr"endifendif12/15/2019 at 11:48 AM #11492612/16/2019 at 1:01 PM #11497312/17/2019 at 6:56 PM #115117Hi all, with my broker (IG) on CFD, after several days of optimization in demo, at the moment where i wanted to push it to live, ProOrder tells me it needs a stop… The ‘customized’ trailing stop musn’t be well recognized. Has this subjet ever been evoked through the 39 pages ? Many thanks
12/18/2019 at 11:13 AM #11514612/18/2019 at 5:42 PM #115189That happen if you are on a limited risk account. All orders must have stoploss attached. I suggest you add a SET STOP PLOSS instruction at the end of the code.
Indeed thank you, i only added this instruction SET STOP PLOSS 100 at the end and my code is online. But a warning (cf. attached snapshot) tells me trailing stop are not allowed with risk limited contracts. Impossible to simulate with the proback test which gives me the same result with and without the final instruction SET STOP PLOSS 100. Only live could give me the answer… I push it live.
12/19/2019 at 1:01 PM #11524812/20/2019 at 10:47 AM #11528912/20/2019 at 8:02 PM #115323Good afternoon, I update the evolution of the strategy in the Nasdaq, it is working in real account, I am waiting for it to do 2 bad operations to increase a position, but it does not fail, I only carry a losing operation. Regarding the results of Strategy 6.1 on the Dax in November, I think it was an accident, a robot that has been making good numbers in a period of 32 months that is what gives the backtest does not stop working at night In the morning, I understand that if the market changes, it should progressively have worse results, but not always start losing. This month of December is in positive and the last operations are very good …. Good weekend and Merry Christmas!
12/22/2019 at 6:52 AM #115360Thanks Gubben and ALZ fit your replies. It seems to work with only adding a ploss at the end ! Which doesn’t prevent the custom trailing to work. A good week on DAX. I’m going to push US 100 v5 to live too.
Balmora, Many thanks for the geometric philosophy of your first idea of this bot, which is very “pure”.
1 user thanked author for this post.
12/28/2019 at 2:36 PM #115520Been running the us100 v5.0p and dax v5.0p since aug 14th.
The us100 has been doing really good. But DAX is still at a loss.
Are there any new versions of DAX that work better?
-
AuthorPosts
Find exclusive trading pro-tools on