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.
-
-
02/27/2019 at 1:38 PM #92464
I have attached 2 indicator that correspond to the display of the angle (in degree) in form of histograms and the slope of the moving average (in radius) and its moving average
Nice! Would you mind if I had them in the library too? Angle of MA is an indicator very often asked by people.
02/27/2019 at 1:46 PM #92467I have attached 2 indicator that correspond to the display of the angle (in degree) in form of histograms and the slope of the moving average (in radius) and its moving average
Nice! Would you mind if I had them in the library too? Angle of MA is an indicator very often asked by people.
@Nicolas
Yes you can had it into the library 🙂02/27/2019 at 2:03 PM #92468My computer/PRT froze in the middle of the night, so i started it again at work today, but sadly PRT shutdown cus it had been “on” for so long. I didnt manage to save any pics.. Results where a 24% walk forward, so not supergreat. Each period had about 20K combinations so obviously it was a huge test and much that could go wrong. Overall the equitycurve didnt look too shabby, i ran 5 periods, only 1 was negative, rest was positive and OK looking.
Was really hoping to analyze it more, might run the test again later.
At the same time i ran an optimization of the same variables from 2016 june -> 2018 July, and kept rest as out of sample. it looked surprisingly good. But then again, i ran optimization on already optimized variables so.. why wouldnt it look good.
All in all, if it keeps performing good for the next 6 months i might as well run it live. My main issue is the “very little” data (few years) that we got..
02/28/2019 at 10:14 PM #92567i had the same idea weeks ago and i used this formula, i don’t know if could help if is similar or mine is completely wrong 😀
12ema15=average[15,ave](typicalprice)c2 = (sin(atan((ema15-ema15[1])/ema15[1]*100)))*10001 user thanked author for this post.
02/28/2019 at 10:50 PM #925731 2 ema15=average[15,ave](typicalprice)
c2 = (sin(atan((ema15-ema15[1])/ema15[1]*100)))*1000
What is the variable “ave” ? I think the best thing it to create a indicator with the instruction “RETURN” and after watching the price action.
You also can test it manually and / or make a bactkest.
02/28/2019 at 11:10 PM #92576‘ave’ is any value from 0 to 6 for the average type.
See here:
https://www.prorealcode.com/documentation/average/
02/28/2019 at 11:14 PM #9257702/28/2019 at 11:29 PM #92587@Giancula @Vonasi
This is my method to calcutate the angle of EM10 on 20 periods. The result is in degree and thick headed between – 90° and + 90° (see the picture below).
1234567Periode = 10 //EMA PeriodnbChandelier= 20 // Number of CandlesMM = Exponentialaverage[Periode](close)ADJASUROPPO = (MM-MM[nbchandelier]*pipsize) / nbChandelierANGLE = (ATAN(ADJASUROPPO)) //ARC TANGENT trignometric functionRETURN angle as "Angle"When i try with your code i don’t have the same result ans the same curve…
1 user thanked author for this post.
02/28/2019 at 11:39 PM #92591Balmora74 – Please use the ‘Insert PRT Code button when posting code. I tidied it up for you!
We should all be aware that it is impossible to calculate a slope in degrees as we do not know what the x value is. All we can do is give the slope a relative value that is an indication of the amount of gradient up or down.
02/28/2019 at 11:50 PM #92592Please use the ‘Insert PRT Code button when posting code. I tidied it up for you! We should all be aware that it is impossible to calculate a slope in degrees as we do not know what the x value is. All we can do is give the slope a value that is an indication of the amount of gradient up or down.
So there is a mistake in my approach ?
03/01/2019 at 12:12 AM #92596So there is a mistake in my approach ?
Only if you think that you are calculating degrees. The only thing we know about the value x is that it is the distance from one bar to the next bar but how do we give that a quantity in pips? We can however know the value of y which we can at least measure in pips.
1 user thanked author for this post.
03/01/2019 at 12:33 AM #9259703/01/2019 at 9:21 AM #92602which variables are you guys optimizing when you choose a new index or forex for this system?
I would like to have this system for eur/usd and for france. Anyone can check if its possible? Thanks a lot!
03/01/2019 at 11:13 AM #92625which variables are you guys optimizing when you choose a new index or forex for this system?
I would like to have this system for eur/usd and for france. Anyone can check if its possible? Thanks a lot!
All answers and ideas are in the answers above of this file of discussion…
03/03/2019 at 12:51 PM #92751Here is the indicator as I was already testing it:
1234567p = 15 //Average periodtype = 0 //0 to 6ma=average[p,type](typicalprice)c = (sin(atan((ma–ma[1])/ma[1]*100)))*1000return 0, ci am using it as a filter in many trategies and for me is working very good.
you can also use the R2 function and results are also good. this is the code12once PERIODO = 90i1 = R2[PERIODO](close) -
AuthorPosts
Find exclusive trading pro-tools on