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.
-
-
05/10/2020 at 4:12 PM #130956
Here is my modification of Balmora’s original. I went back to the beginning and made a few small changes with in mind it had to be a lite version.
Besides that, the trailing stop kicks in when atr distance is 8 and quickly moves to 4 when there are no new high/low made in an effort not to surrender too much gains.
With 2% stoploss and a trailingstop there are lot’s off signals which aren’t visible when in a position. So it’s important to be able to include those, especially in the optimisation!
Inserted reenter, so every true conditions to enter the market could be tested, even when current position was in loss, profit or both. (selectable) Then it’s closed and opened again in same direction.
It means more trades and smaller average losses/gains and still this strategy is maintaining a similar result despite more trades. a good indication for robustness!
10 users thanked author for this post.
05/10/2020 at 9:34 PM #13103105/10/2020 at 10:52 PM #13104105/11/2020 at 8:45 PM #13120305/12/2020 at 1:12 PM #13130005/13/2020 at 12:54 PM #13149305/13/2020 at 5:44 PM #13153505/15/2020 at 2:26 PM #131778one thing to point out.
running it for long only and short only, both performances with current settings are poor. Long & short work together with eachother and both have in part optimised settings. That is one major reliability issue regardless how the performance looks if both are active at the same time, is it not?
05/16/2020 at 7:24 PM #131885on 121p, simply selecting long/short only resulted in (very) poor performance.
It uses the stoploss of 2% and a big trailingstop.
So new test, the focus is long/short only, it needed a smaller stoploss and changed it to 0.5%
Made the trailingstop faster (atr 6), optimised the settings (and went back to the original values) and optimised the angle. Without the trend detection.
5 users thanked author for this post.
05/17/2020 at 12:53 PM #13195405/17/2020 at 1:51 PM #13196505/17/2020 at 10:41 PM #132037Paul this is the last version of the code i’m running since one month and the results seems quite good. I added ATR + Daily / Weekly and Monthly Pivot for calculating the PositionSize and as a filter for entry point. Perhaps a idea to improve the your excellent v130p version of Vectorial Dax…
05/18/2020 at 1:22 AM #13205005/20/2020 at 11:47 PM #132490Maybe it’s curve fitting guys, but I get best results when using 5 instead of 11 and 20 instead of 36 for the ATR position sizing. Tested the robustness and it looks quite alright, let me know what you think 🙂
@Balmora74, how did you found the ATR values ? I’m working on a more gradual sizing position on your “basic” version.Anyhow, even older versions are working quite well despite the crash, I’m very surprised, i honestly thought there was some overfitting in the air, but apparently not so much ! Good job guys!
1 user thanked author for this post.
05/21/2020 at 10:55 AM #132557Hi, yeah that’s it.
here’s the latest, I don’t know how to improve with only few extra criteria significantly for only short & only long.
Hi @Paul
Why do you separate long/short robots ? Do you think it ameliorate something ?Cheers
-
AuthorPosts
Find exclusive trading pro-tools on