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.
-
-
10/21/2020 at 2:19 PM #147998
Hi Fifi, that concept can be expanded in multiple ways.
with above example, i.e. when lowest[barindex-tradeindex](close) was below another line, which means there was a fast run-up where you prevent buying near the top. If prevented buying on the top, it could still be considered to close a short position.
Also for exits, although then it’s best to have the code below the entry , something like this
12345678910if tradeprice(1)>fibobear62b and highest[barindex-tradeindex](close)<fibobull62b thenif close crosses under fibobear62b thensell at marketendifendifif tradeprice(1)<fibobull62b and lowest[barindex-tradeindex](close)>fibobear62b thenif close crosses over fibobull62b thenexitshort at marketendifendifAlthough all this would not give a greater equitycurve, maybe if programmed well could results in an algo with a smaller stoploss like 0.5 to 1%.
10/21/2020 at 4:16 PM #14800410/21/2020 at 8:10 PM #148032i’am was optimistic 🙂 lowering it to 1% would be nice for this timeframe. For now I keep it for testing at 2%.
I did had a look at the reversal exit code.
While I splitted short in 3 sections, there are all the same.
The problem was long which didn’t work before, there splitting worked. Ofcourse all curvefitting after the fact.
It’s not robust, because i.e. slippage & high spread could influence this too. But I always like to try something new even if it fails.
The idea; if the position doesn’t gain ground after opening, the criteria for the range is lower which increases the chance for an early exit.
Also a gap rewrite.
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374// reversal exitonce longexit =1once shortexit=1if longexit thenif longonmarket and highest[barindex-tradeindex](high)-tradeprice(1)<25 thenminrangedistL1=1cl1=close<open and close[1]<open[1] and close[2]<open[2]cl2=(close=low or close[1]=low[1] or close[2]=low[2])cl3=(range>(close/1000)*minrangedistL1 or range[1]>(close[1]/1000)*minrangedistL1 or range[1]>(close[1]/1000)*minrangedistL1)if cl1 and cl2 and cl3 and (high>high[1] or low<low[1]) and barindex-tradeindex>=3 thensell at marketendifendifif longonmarket and (highest[barindex-tradeindex](high)-tradeprice(1)>=25 and highest[barindex-tradeindex](high)-tradeprice(1)<50) thenminrangedistL2=3cl1a=close<open and close[1]<open[1] and close[2]<open[2]cl2a=(close=low or close[1]=low[1] or close[2]=low[2])cl3a=(range>(close/1000)*minrangedistL2 or range[1]>(close[1]/1000)*minrangedistL2 or range[1]>(close[1]/1000)*minrangedistL2)if cl1a and cl2a and cl3a and (high>high[1] or low<low[1]) and barindex-tradeindex>=3 thensell at marketendifendifif longonmarket and highest[barindex-tradeindex](high)-tradeprice(1)>=50 thenminrangedistL3=4cl1b=close<open and close[1]<open[1] and close[2]<open[2]cl2b=(close=low or close[1]=low[1] or close[2]=low[2])cl3b=(range>(close/1000)*minrangedistL3 or range[1]>(close[1]/1000)*minrangedistL3 or range[1]>(close[1]/1000)*minrangedistL3)if cl1b and cl2b and cl3b and (high>high[1] or low<low[1]) and barindex-tradeindex>=3 thensell at marketendifendifendifif shortexit thenif shortonmarket and tradeprice(1)-lowest[barindex-tradeindex](low)<25 thenminrangedistS1=1.5cs1=close>open and close[1]>open[1] and close[2]>open[2]cs2=(close=high or close[1]=high[1] or close[2]=high[2])cs3=(range>(close/1000)*minrangedistS1 or range[1]>(close[1]/1000)*minrangedistS1 or range[1]>(close[1]/1000)*minrangedistS1)if cs1 and cs2 and cs3 and (high>high[1] or low<low[1]) and barindex-tradeindex>=3 thenexitshort at marketendifendifif shortonmarket and (tradeprice(1)-lowest[barindex-tradeindex](low)>=25 and tradeprice(1)-lowest[barindex-tradeindex](low)-tradeprice(1)<50) thenminrangedistS2=1.5cs1a=close>open and close[1]>open[1] and close[2]>open[2]cs2a=(close=high or close[1]=high[1] or close[2]=high[2])cs3a=(range>(close/1000)*minrangedistS2 or range[1]>(close[1]/1000)*minrangedistS2 or range[1]>(close[1]/1000)*minrangedistS2)if cs1a and cs2a and cs3a and (high>high[1] or low<low[1]) and barindex-tradeindex>=3 thenexitshort at marketendifendifif shortonmarket and tradeprice(1)-lowest[barindex-tradeindex](low)>=50 thenminrangedistS3=1.5cs1b=close>open and close[1]>open[1] and close[2]>open[2]cs2b=(close=high or close[1]=high[1] or close[2]=high[2])cs3b=(range>(close/1000)*minrangedistS3 or range[1]>(close[1]/1000)*minrangedistS3 or range[1]>(close[1]/1000)*minrangedistS3)if cs1b and cs2b and cs3b and (high>high[1] or low<low[1]) and barindex-tradeindex>=3 thenexitshort at marketendifendifendifif onmarket thenif dayofweek=0 and (hour=0 and minute>=57) thenif shortonmarket and close>dopen(0) and dopen(0)-dclose(1)>50 thenexitshort at marketendifif longonmarket and close<dopen(0) and dclose(1)-dopen(0)>50 thensell at marketendifendifendif3 users thanked author for this post.
10/22/2020 at 9:20 AM #14805810/22/2020 at 11:29 AM #148075This setup is working very unklucky the last 7 days. Every time switching the position on low/high and turn into the other side. 9 SL in a row is not normal for that strategy. Hope it will work better the next days.
Attached the new itf.
10/22/2020 at 1:54 PM #14808610/22/2020 at 2:07 PM #148088Hi, I have added a routine that close position if loss or profit aftert X bar and I have optimize the variable longexit (for reversal)…it seems to have some improvement. Thanks
10/22/2020 at 2:30 PM #148091funny, by mistake I’ve loaded up v5p on the dax 10s
with these settings ;
1234once tradetype = 1 // [1]long/short [2]long [3]shortonce reenter = 1 // [1]on [0]off (off ignores positionperftype/value below)once positionperftype = 1 // [0]loss/gain [1]loss [2]gainonce positionperfvalue = 0 // % (0 or higher)10/22/2020 at 2:44 PM #14809410/22/2020 at 2:55 PM #148095Its 10s yes, but on DJ, not DAX right?
It´s DAX
10/22/2020 at 2:56 PM #14809610/22/2020 at 3:04 PM #148097Interesting Paul! If one were to optimise this strategy weekly / monthly, which parameters would you then optimise? I had a pretty bad week recently and wondering if it would be better to run it with weekly / monthly optimisations?
10/22/2020 at 4:48 PM #148107@volpiemanuele, thanks for all yours algos. I launch the DJ-3m-Vectorial-V3p5_v1, but it crashed.
10/22/2020 at 8:33 PM #148127Hi @Paul, shouldn’t the code:
(range>(close/1000)*minrangedist– or range[1]>(close[1]/1000)*minrangedist– or range[1]>(close[1]/1000)*minrangedist–)
be
(range>(close/1000)*minrangedist– or range[1]>(close[1]/1000)*minrangedist– or range[2]>(close[2]/1000)*minrangedist–)
on all occurences (–) in the code you posted?
10/23/2020 at 6:51 AM #148146 -
AuthorPosts
Find exclusive trading pro-tools on