One more average ... - page 4

To add comments, please log in or register
kokoriso7
45
kokoriso7  

To Linuxser

which method are you takling about ?

please could you put link ?

Mladen Rakic
132743
Mladen Rakic  

...

Using low lag averages (smoothers) to correct some of the indicators problems

___________________________

Some normally very useful indicators like RSX, due to the nature of their calculation, tend to narrow ("flatten") the range they are showing if their periods are widened. In the case of RSX (as well as its predecessor RSI) are tending to center values of 50 as the periods are growing. Here is an example (RSX in this case, but keep in mind that RSX is a smoothed RSI)
That is the reason why any serious study is recommending NOT to use periods larger than 10 for RSI (and RSX implicitly) Well, here is one solution that adds no lag to it and corrects that "flattening" problem : instead of using a raw price using a low lag smoothers like one more average. And, see the results :
RSX on OMA :

and RSX on Jurik smooth

As you can see, the crosses are on the same place, but the ranges are dramatically enhanced (to the level that one can almost use the classical 20-80 levels for signals too)

I am including a version that uses Jurik smoothing too (as a comparison, default parameters are set to have the values as similar as possible) I know that it sounds like preaching, but even in this case it is clear that OMA is not lagging behind Jurik smooth (in some cases, quite the opposite) but for the sake of fair comparison I decided to include the both versions.

___________________________

PS: a little advice - the longer the RSX period the longer the smoothing period should be. But do not "oversmooth" : We still need those crosses as early as we can get them. I used smoothing length of 10 for RSX 50, for example

PPS : updated new metatrader 4 compatible rsx on oma posted here https://www.mql5.com/en/forum/179662 . Rsx on jurik smooth does not need updates

MikhaelPankov
60
MikhaelPankov  

Great !!!

Really wonderful work , Mladen !!! A sack of thanks !

Linuxser
5923
Linuxser  
kokoriso7:
To Linuxser

which method are you talking about ?

Could you put link ?
kokoriso7:
which method are you takling about ? please could you put link ?

This one. An oldie.

https://www.mql5.com/en/forum/178487

William Snyder
9470
William Snyder  
mladen:
Using low lag averages (smoothers) to correct some of the indicators problems

___________________________

Some normally very useful indicators like RSX, due to the nature of their calculation, tend to narrow ("flatten") the range they are showing if their periods are widened. In the case of RSX (as well as its predecessor RSI) are tending to center values of 50 as the periods are growing. Here is an example (RSX in this case, but keep in mind that RSX is a smoothed RSI)
That is the reason why any serious study is recommending NOT to use periods larger than 10 for RSI (and RSX implicitly) Well, here is one solution that adds no lag to it and corrects that "flattening" problem : instead of using a raw price using a low lag smoothers like one more average. And, see the results :
RSX on OMA :

and RSX on Jurik smooth

As you can see, the crosses are on the same place, but the ranges are dramatically enhanced (to the level that one can almost use the classical 20-80 levels for signals too)

I am including a version that uses Jurik smoothing too (as a comparison, default parameters are set to have the values as similar as possible) I know that it sounds like preaching, but even in this case it is clear that OMA is not lagging behind Jurik smooth (in some cases, quite the opposite) but for the sake of fair comparison I decided to include the both versions.

___________________________

PS: a little advice - the longer the RSX period the longer the smoothing period should be. But do not "oversmooth" : We still need those crosses as early as we can get them. I used smoothing length of 10 for RSX 50, for example

Nice work Mladen, Thanks a lot!

tinear10
67
tinear10  

My last Indicator request for a long time

Mladen thank you again for your contributions. Your efforts are very much appreciated.

I have a request for an indicator please. I have been using your new RSX on OMA. This is a very impressive and reliable indicator. I have been using it with an EMA placed on top of it. My request would be the RSX on OMA with an OMA of this indicator. Or another way to ask would be to have an OMA of RSX on OMA. A new version of the Moving Average of RSI but using your OMA. I hope that all make sense.

If you could please try this with an alert for a cross of the OMA over/under the RSX on OMA.

Thank you

Mladen Rakic
132743
Mladen Rakic  

tinear,

Here you go Added signal line (oma too, separate settings for it) and alerts.

____________________

PS: if you set the signal length to 1 or less than 1 neither signal line is going to be shown nor will there be an alert. So for both you have to have a signal length greater than 1

PPS: updated version compatible with new metatrader 4 posted here https://www.mql5.com/en/forum/179662

regards

mladen

tinear10
67
tinear10  

Ypu Rock Mladen

I can not believe how fast you coded this. Truly incredible! Thank you very much. It is absolutely perfect. You are a saint

MikhaelPankov
60
MikhaelPankov  
Mladen Rakic
132743
Mladen Rakic  

...

Mikhael,

The one shown on those pictures actually is not OMA but a variation of the one posted in the elite section that uses Jurik (posting it here)
I am working on OMA version too but there are some cases that are happening which I need to solve first (here is the preview of the same period OMA version).
It seems that OMA is "too good" making 3 averages of a high, low and close, and that in some cases something like this can happen (frankly I did not check that thoroughly the jurik version as much as I am checking the OMA version - case like this happens one time on my 1 hour EURUSD, but I want to know exactly why it happens and to prevent it)
As soon as I find the reasons for those and as soon as I have the solution for that, will post it here. Also, I would like to make it a bit "slower" (less sensitive in this case - now I have a funny problem of too much speed with this indicator, the one that I used for comparison is already running on speed 1.5, which as you know, is really not much ) too. These are the reasons why I am still not posting it and why I still did not post it. This time I am asking for a bit of patience (I am the most impatient in this case, but I really would not like to rush with this one, I think it will be worth an extra work on it) Hope you understand me

regards

mladen

To add comments, please log in or register