Elite indicators :) - page 374

 

Thanks again Bill..

mrtools:
No problem Valeo.

Many thanks, Bill. Much appreciated. Enjoy the rest of your weekend.

Best wishes.

 

ValeoFX

It is a "measure" or a "criteria" for "stepping". You actually have 2 ways of "choosing" ATR - first it is ATR (average true range - the stress is on average) and if you use period 1 for average true range it becomes a true range (no averaging done) and then a minimal and maximal ATR or TR is cheeked for in the last WindowSize data (the window size limitation is used in order to prevent "infinite length" checking as well as implicit repainting - to remind that it does not repaint any more nor does it deform due to "infinite length" search). Value found that way is then used for further calculations (no linear values used in stochastic calculation, but already "stepped" values)

Hope this clarifies what is ATR used for in step stochastic

regards

Mladen

ValeoFX:
Hi Mladen,

Would you mind telling me how the ATR in the "Step stochastic pre-smoothed" actually works, plse?

I have had tremendous success with low settings such a 1 (would you believe it), but discovered since that it is actually better set @ 20 (your default was @ 10), but with tweaks to the K.Slow.

Just a short explanation would be great please.

Thanking you in advance.
 

Corrected average

Here is one more indicator


Original idea for it is from Andreas Uhl. It seems that professor Uhl is a rather interesting person. For some further links regarding him, here are a couple of pages page which can be used for further searches : http://www.cosy.sbg.ac.at/~uhl/ or Multimedia Signal Processing and Security Lab . And as it is seen from this post, he occasionally takes part in the TA too.

The corrected average should not be used as a regular average. It is more a support / resistance study than an average and, in my opinion, its primary usage should be that. In the original idea the only average that is used is the simple moving average but I decided to experiment with a couple of other averages to see what results are other "basic" averages going to produce. Also, in order to see how could the functionality of it be extended, decided to ad a mode (MiltiColormode) which is a cross of corrected average and its basic average (ie: if a corrected average is made of, for example, Hull moving average, than the crosses are of corrected average and Hull moving average) and in that mode it can be (based on usual inspection and test) used as trend detection indicator (on longer time frames especial;y) That is easiest to see if one turns the visibility of "basic average" on with AverageVisible parameter. So in the end, this indicator is able of producing corrected averages of

0 - simple moving average

1 - exponential moving average

2 - smoothed moving average

3 - linear weighet moving average

4 - parabolic weighted moving average

5 - volume weighted moving average

6 - Hull moving average

7 - triangular moving average

8 - sine weighted moving average

9 - linear regression (lsma)

10 - non lag moving average

11 - zero lag moving average

I used these since all these can be used without any additional parameter added to indicator (to keep the usage as simple as it can be). Default average used as a "basic average" in this one is zero lag moving average, but as I mentioned, the original was on simple moving average. Here are some example that can be produced with the indicator

PS: this indicator has one unusual price : price 7 is (High+Low+Open+Close)/4 (it does not exist as a price type in metatrader, but decided to use it in this indicator) It seems as a good choice in some cases

Files:
corr_1.gif  27 kb
corr_2.gif  28 kb
corr_3.gif  24 kb
 

EDITED: forget this request: solved

Hello, the attached indicator only prints an arrow after the candle closes; can someone rewrite the indicator so that it prints the arrows during candle?

 

mladen,

I am getting false hits on the trend and then of course on the arrows?? The arrows are on the 5 min setting.

See attached:

The hama1 at 5:19 shows trend -1 then hama2 at 5:20 shows 1 even though the readings support -1, HAMA3 just shows the 5min hama with the problem?? Causing havack with my EA, also the EA works with the chart period but I can't get it to work with a different period such as 1 m chart with a 5min HAMA in the EA.

Sorry if I'm not clear.

Thanks

Ray

 

Thank you Mladen

mladen:
ValeoFX

It is a "measure" or a "criteria" for "stepping". You actually have 2 ways of "choosing" ATR - first it is ATR (average true range - the stress is on average) and if you use period 1 for average true range it becomes a true range (no averaging done) and then a minimal and maximal ATR or TR is cheeked for in the last WindowSize data (the window size limitation is used in order to prevent "infinite length" checking as well as implicit repainting - to remind that it does not repaint any more nor does it deform due to "infinite length" search). Value found that way is then used for further calculations (no linear values used in stochastic calculation, but already "stepped" values)

Hope this clarifies what is ATR used for in step stochastic

regards

Mladen

===================

Many thanks, Mladen. Much appreciated.

 

Problem loading..

mrtools:
Adaptive T3 Heiken Ashi mtf and alerts and Adaptive T3 Vhf. Thanks Mladen for the help. On the picture its h4 heiken on h1 chart and about the vhf check out where the highest peaks are , and in case someone not aware Vhf is not a directional indicator, when it is going up market is trending.

======

MrTools I cannot get the HeikenAshi to load onto a chart. Any idea why not?

Thanks for responding.

 

mrtools

Is there any chance you could add a "trend buffer" to the Heikin ashi ??

Thanks

Ray

mrtools:
Adaptive T3 Heiken Ashi mtf and alerts and Adaptive T3 Vhf. Thanks Mladen for the help. On the picture its h4 heiken on h1 chart and about the vhf check out where the highest peaks are , and in case someone not aware Vhf is not a directional indicator, when it is going up market is trending.
 

Ray

Arrows are shown where hama value without step filtering changes trend, so, if the step value is set to > 0, it will occasionally show arrows on places where it visually does not appear. If you want to avoid that, change the code that goes like this :
trend = trend;

if (ExtMapBuffer3<ExtMapBuffer4) trend = 1;

if (ExtMapBuffer3>ExtMapBuffer4) trend = -1;

//

//

//

//

//

if (Step>0)

{

if( MathAbs(ExtMapBuffer1-ExtMapBuffer1) < Step*pointModifier*Point ) ExtMapBuffer1=ExtMapBuffer1;

if( MathAbs(ExtMapBuffer2-ExtMapBuffer2) < Step*pointModifier*Point ) ExtMapBuffer2=ExtMapBuffer2;

if( MathAbs(ExtMapBuffer3-ExtMapBuffer3) < Step*pointModifier*Point ) ExtMapBuffer3=ExtMapBuffer3;

if( MathAbs(ExtMapBuffer4-ExtMapBuffer4) < Step*pointModifier*Point ) ExtMapBuffer4=ExtMapBuffer4;

}

[/PHP]

and change it to this (move the first 3 lines of the above code to the and of that code block

[PHP]

//

//

//

//

//

if (Step>0)

{

if( MathAbs(ExtMapBuffer1-ExtMapBuffer1) < Step*pointModifier*Point ) ExtMapBuffer1=ExtMapBuffer1;

if( MathAbs(ExtMapBuffer2-ExtMapBuffer2) < Step*pointModifier*Point ) ExtMapBuffer2=ExtMapBuffer2;

if( MathAbs(ExtMapBuffer3-ExtMapBuffer3) < Step*pointModifier*Point ) ExtMapBuffer3=ExtMapBuffer3;

if( MathAbs(ExtMapBuffer4-ExtMapBuffer4) < Step*pointModifier*Point ) ExtMapBuffer4=ExtMapBuffer4;

}

trend = trend;

if (ExtMapBuffer3<ExtMapBuffer4) trend = 1;

if (ExtMapBuffer3>ExtMapBuffer4) trend = -1;

Then it will show where visually the arrows should appear to even if step filtering is applied (as I said, otherwise it shows arrows where "real" unfiltered values change trend).

Also for accuracy of visual checking, when using mtf turn the interpolation off (interpolating is "smoothing" values and thus it is changing the original mtf values - the question is though where the arrows should appear - at the beginning of the mtf bar or at the end. Otherwise classical mtf and interpolated mtf have exactly the same number of correct values : 1 ( one ). Except that the "classical" shows all as the same (which was not true) and interpolated shows the last bar belonging to higher time frame with exact value and the rest is smoothed in combination with previous mtf bar)

regards

Mladen

traderduke:
mladen,

I am getting false hits on the trend and then of course on the arrows?? The arrows are on the 5 min setting.

See attached:

The hama1 at 5:19 shows trend -1 then hama2 at 5:20 shows 1 even though the readings support -1, HAMA3 just shows the 5min hama with the problem?? Causing havack with my EA, also the EA works with the chart period but I can't get it to work with a different period such as 1 m chart with a 5min HAMA in the EA.

Sorry if I'm not clear.

Thanks

Ray
 

Mladen

Thanks for the explainlation and fix. Any input to my second problem, Time frame other then current not working in EA. I'm using the "TimeFrame" as you told me before but Its not seeing it.??

Again Thanks

Ray

mladen:
Ray Arrows are shown where hama value without step filtering changes trend, so, if the step value is set to > 0, it will occasionally show arrows on places where it visually does not appear. If you want to avoid that, change the code that goes like this :
trend = trend;

if (ExtMapBuffer3<ExtMapBuffer4) trend = 1;

if (ExtMapBuffer3>ExtMapBuffer4) trend = -1;

//

//

//

//

//

if (Step>0)

{

if( MathAbs(ExtMapBuffer1-ExtMapBuffer1) < Step*pointModifier*Point ) ExtMapBuffer1=ExtMapBuffer1;

if( MathAbs(ExtMapBuffer2-ExtMapBuffer2) < Step*pointModifier*Point ) ExtMapBuffer2=ExtMapBuffer2;

if( MathAbs(ExtMapBuffer3-ExtMapBuffer3) < Step*pointModifier*Point ) ExtMapBuffer3=ExtMapBuffer3;

if( MathAbs(ExtMapBuffer4-ExtMapBuffer4) < Step*pointModifier*Point ) ExtMapBuffer4=ExtMapBuffer4;

}

[/PHP]

and change it to this (move the first 3 lines of the above code to the and of that code block

[PHP]

//

//

//

//

//

if (Step>0)

{

if( MathAbs(ExtMapBuffer1-ExtMapBuffer1) < Step*pointModifier*Point ) ExtMapBuffer1=ExtMapBuffer1;

if( MathAbs(ExtMapBuffer2-ExtMapBuffer2) < Step*pointModifier*Point ) ExtMapBuffer2=ExtMapBuffer2;

if( MathAbs(ExtMapBuffer3-ExtMapBuffer3) < Step*pointModifier*Point ) ExtMapBuffer3=ExtMapBuffer3;

if( MathAbs(ExtMapBuffer4-ExtMapBuffer4) < Step*pointModifier*Point ) ExtMapBuffer4=ExtMapBuffer4;

}

trend = trend;

if (ExtMapBuffer3<ExtMapBuffer4) trend = 1;

if (ExtMapBuffer3>ExtMapBuffer4) trend = -1;

Then it will show where visually the arrows should appear to even if step filtering is applied (as I said, otherwise it shows arrows where "real" unfiltered values change trend). Also for accuracy of visual checking, when using mtf turn interpolation off (interpolating is "smoothing" values and thus it is changing the original mtf values - the question is though where the arrows should appear - at the beginning of the mtf bar or at the end. Otherwise classical mtf and interpolated mtf have exactly the same number of correct values : 1. Except that the correct shows all as the same (which was not true) and mtf shows the last bar belonging to higher time frame correctly and the rest is smoothed in combination with previous mtf bar)

regards

Mladen
Reason: