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 2 weeks ago by Greger2346.
-
-
10/27/2020 at 11:39 AM #148647
The “DAX 10s -vectoril v3p5 v2” is crashing for me when it takes a position, it just did. Does anyone else encounter the same problem ?
Mine says running and the last was position took was at 9:13 that exited at 9:59.
10/27/2020 at 11:43 AM #14864810/27/2020 at 12:03 PM #148650@paisantrader Thnx I see you left the stop-loss at 2%. That’s too much for a 10s timeframe I think.
Fortunately if it’s changed to 0.4 or 0.5% it has no or very minimal impact on results, that’s on the dow version.
I realize that I was too focused on the trailing stop and wasn’t 100% how it worked. Thought it set it already from the start and the regular SL was there just to set a default value. But after a test, I see a big difference. Thank you for pointing out our mistakes, much appreciated!
2% -> 0.4% doubled the profit.
10/27/2020 at 1:16 PM #148652@Paisantrader can you post your itf files? 🙂
10/27/2020 at 3:26 PM #148673@Paisantrader can you post your itf files? 🙂
What I posted above was just sll and sls. Changed it from 2 to 0.4.
I’m running 3 version on Dow today, since I’m quite sure that what worked yesterday, will not work today or at least far from yesterdays numbers.
- The one already posted here
- Optimized before opening today and 100k bars
- Optimized before opening today and 5k bars, roughly 22:00 – before opening
Just a little testing for my own sake 🙂
10/27/2020 at 4:12 PM #148680Hi, so if there’s a stoploss of 0.4 or 0.5% why not use as backup an atr stoploss or/and profit target.
I prefer to leave the original setting for the % stoploss with set the set command intact
Here’s a quick code. I’ve doubt if it should close[0] or close[1].
1234567891011121314151617181920212223242526272829303132// ATR Stops and targetsIF LONGONMARKET THENatrstop = positionprice - (10* AverageTrueRange[14](CLOSE)[0])atrtarget = positionprice +(10* AverageTrueRange[14](CLOSE)[0])Endifif shortonmarket thenatrstop = positionprice + (10* AverageTrueRange[14](CLOSE)[0])atrtarget = positionprice -(10* AverageTrueRange[14](CLOSE)[0])endifif longonmarket thenif high crosses over atrtarget thensell at marketendifif low crosses under atrstop thensell at marketendifgraphonprice atrstopgraphonprice atrtargetendifif shortonmarket thenif low crosses under atrtarget thenexitshort at marketendifif high crosses over atrstop thenexitshort at marketendifgraphonprice atrstopgraphonprice atrtargetendif10/27/2020 at 7:23 PM #148715Hi, so if there’s a stoploss of 0.4 or 0.5% why not use as backup an atr stoploss or/and profit target.
I prefer to leave the original setting for the % stoploss with set the set command intact
Here’s a quick code. I’ve doubt if it should close[0] or close[1].
Thank you, much appreciated. I see there’s similarities to the one in use right now . I’ll test them side by side to compare.
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109// trailing atr stoponce trailingstoptype1 = 1 // trailing stop - 0 off, 1 onif trailingstoptype1 then//========================once tsatrdistlong = 2.3 //3 // ts atr distanceonce tsatrdistshort = 2.3 //3 // ts atr distanceonce tsincrements = 0.05 // set to 0 to ignore tsincrementsonce tsminatrdist = 2once tsatrperiod = 14 //14 // ts atr parameteronce tsminstop = 10 //10 // ts minimum stop distanceonce ts1sensitivity = 2 // [0]close;[1]high/low;[2]low;high//========================if barindex=tradeindex thentrailingstoplong = tsatrdistlongtrailingstopshort = tsatrdistshortelseif longonmarket thenif tsnewsl>0 thenif trailingstoplong>tsminatrdist thenif tsnewsl>tsnewsl[1] thentrailingstoplong=trailingstoplongelsetrailingstoplong=trailingstoplong-tsincrementsendifelsetrailingstoplong=tsminatrdistendifendifendifif shortonmarket thenif tsnewsl>0 thenif trailingstopshort>tsminatrdist thenif tsnewsl<tsnewsl[1] thentrailingstopshort=trailingstopshortelsetrailingstopshort=trailingstopshort-tsincrementsendifelsetrailingstopshort=tsminatrdistendifendifendifendiftsatr=averagetruerange[tsatrperiod]((close/10)*pipsize)/1000//tsatr=averagetruerange[tsatrperiod]((close/1)*pipsize) // (forex)tgl=round(tsatr*trailingstoplong)tgs=round(tsatr*trailingstopshort)if not onmarket or ((longonmarket and shortonmarket[1]) or (longonmarket[1] and shortonmarket)) thentsmaxprice=0tsminprice=closetsnewsl=0endifif ts1sensitivity=1 thents1sensitivitylong=hights1sensitivityshort=lowelsif ts1sensitivity=2 thents1sensitivitylong=lowts1sensitivityshort=highelsets1sensitivitylong=closets1sensitivityshort=closeendifif longonmarket thentsmaxprice=max(tsmaxprice,ts1sensitivitylong)if tsmaxprice-tradeprice(1)>=tgl*pointsize thenif tsmaxprice-tradeprice(1)>=tsminstop thentsnewsl=tsmaxprice-tgl*pointsizeelsetsnewsl=tsmaxprice-tsminstop*pointsizeendifendifendifif shortonmarket thentsminprice=min(tsminprice,ts1sensitivityshort)if tradeprice(1)-tsminprice>=tgs*pointsize thenif tradeprice(1)-tsminprice>=tsminstop thentsnewsl=tsminprice+tgs*pointsizeelsetsnewsl=tsminprice+tsminstop*pointsizeendifendifendifif barindex-tradeindex>1 thenif longonmarket thenif tsnewsl>0 thensell at tsnewsl stopendifif tsnewsl>0 thenif low crosses under tsnewsl thensell at marketendifendifendifif shortonmarket thenif tsnewsl>0 thenexitshort at tsnewsl stopendifif tsnewsl>0 thenif high crosses over tsnewsl thenexitshort at marketendifendifendifendifendif1 user thanked author for this post.
10/28/2020 at 11:27 AM #14876910/31/2020 at 4:18 PM #14908811/07/2020 at 12:09 AM #14973511/07/2020 at 12:17 AM #149737@BobOgden, that’s a fantastic job! 😃
However, this system doesn’t seems to perform well on 10s for now.. I optimised it for 3 minutes at the enhance.
on what schedule did you ran it as I see that you’ve wrote 15/15:30 to 22?
1 user thanked author for this post.
11/07/2020 at 7:08 PM #149794@Tanou it should be the same as the original code, only changed to fit EU time (well, at least I think, I’m not even sure it does fit EU time now).
I’ll try and update it in two week’s time to get a full month or so. As you said, it has performed pretty baldy lately, especially on US election day
The text box is just to remind me to check whether DJ opening hours wouldn’t be better than from 5:00 to 23:00
Positionsize is 0.2 btw
I’ve been running the 3min version, hopefully it does well 🙂
11/07/2020 at 9:53 PM #149806Has anyone tried using this as a mean reversing strategy?
11/09/2020 at 6:50 PM #149937Here’s a version which uses the heuristics engine, but not aggressively.
The way I used the heuristics engine & modified it, while it works in the backtest, i’am not convinced about using it. The engine can easily be switched off.
I had it with he on/off running side by side for a short while and results were identical, but didn’t look into it too much.
Actually I had already deleted this version because it grew too big and curvefitted.
11/09/2020 at 9:12 PM #149947 -
AuthorPosts
Find exclusive trading pro-tools on