Elite indicators :) - page 1348

New comment
 
greif:

Hi,

I am trying to use stepma averages indicator in EA (using iCustom) but strange error happen: 

2016.09.25 22:55:18.024 2015.01.15 00:02  Stepma averages 4_4 mtf EURUSD,M5: invalid EX4 file (8)

2016.09.25 22:55:17.997 2015.01.15 00:02  Stepma averages 4_4 mtf EURUSD,M5: global initialization failed

2016.09.25 22:55:17.997 2015.01.15 00:02  Stepma averages 4_4 mtf EURUSD,M5: invalid EX4 file (8)

2016.09.25 22:55:17.970 2015.01.15 00:02  Stepma averages 4_4 mtf EURUSD,M5: global initialization failed

2016.09.25 22:55:17.970 2015.01.15 00:02  Stepma averages 4_4 mtf EURUSD,M5: invalid EX4 file (8)

2016.09.25 22:55:17.944 2015.01.15 00:02  Stepma averages 4_4 mtf EURUSD,M5: global initialization failed

 

Testing in tester, MT4 build is 1010. Indicator works at graph without any problems (2016.09.25 23:13:47.686 Custom indicator stepma averages 4_4 mtf EURUSD,H1: loaded successfully).

Could you help me please? What is the problem?

Post your iCustom() call please so that it can be checked?

PS: that ex4 file was built using build 1012 - you should let the upgrade for the terminal take place and then all will work OK

 
greif:

Hi,

I am trying to use stepma averages indicator in EA (using iCustom) but strange error happen: 

2016.09.25 22:55:18.024 2015.01.15 00:02  Stepma averages 4_4 mtf EURUSD,M5: invalid EX4 file (8)

2016.09.25 22:55:17.997 2015.01.15 00:02  Stepma averages 4_4 mtf EURUSD,M5: global initialization failed

2016.09.25 22:55:17.997 2015.01.15 00:02  Stepma averages 4_4 mtf EURUSD,M5: invalid EX4 file (8)

2016.09.25 22:55:17.970 2015.01.15 00:02  Stepma averages 4_4 mtf EURUSD,M5: global initialization failed

2016.09.25 22:55:17.970 2015.01.15 00:02  Stepma averages 4_4 mtf EURUSD,M5: invalid EX4 file (8)

2016.09.25 22:55:17.944 2015.01.15 00:02  Stepma averages 4_4 mtf EURUSD,M5: global initialization failed

 

Testing in tester, MT4 build is 1010. Indicator works at graph without any problems (2016.09.25 23:13:47.686 Custom indicator stepma averages 4_4 mtf EURUSD,H1: loaded successfully).

Could you help me please? What is the problem?

PPS: used the following code to test

void start ()
{
   double result = iCustom(NULL,0,"Stepma averages 4_4 mtf",0,0);
   Comment(result);
   return;
}

and all works just fine

 

Hello mladen,

 

would it be possible to make a histo version of this indicator?

 

Thx.

D. 

 
Desatar:

Hello mladen,

 

would it be possible to make a histo version of this indicator?

 

Thx.

D. 

I think,correct name should be like this "Regularized ema + alerts 1.2"

for to avoid and mislead spreading wrong name,though it is working.

 
mladen:

PPS: used the following code to test

and all works just fine

Thanks, I have found mistake in params of iCustom, indi not released and it probaly caused fill of ram and crash .... 
 

Upgraded corrected average (with the newest set of averages and the newest set of prices). Also, some additions made :different way of coloring - using coloring on slope for this indicator instead of average crosses - as it is in the Andreas Uhl's original - seems to be filtering out quite a few false signals.

Balance between some (not much, compared to crosses) additional lag and eliminating the false signals has to be found, but all in all, the indicator is not bad


Files:
Corrected average 2.5.ex4  131 kb
 
mladen:

Upgraded corrected average (with the newest set of averages and the newest set of prices). Also, some additions made :different way of coloring - using coloring on slope for this indicator instead of average crosses - as it is in the Andreas Uhl's original - seems to be filtering out quite a few false signals.

Balance between some (not much, compared to crosses) additional lag and eliminating the false signals has to be found, but all in all, the indicator is not bad


Dearest MLADEN

Thanks for additional averages and prices along with extra features.

do you means the original line is thin one but we have to consider thick line that formed with possible less lag but removing some tiny false signal on purpose "as a result" .

regards

 
mntiwana:

Dearest MLADEN

Thanks for additional averages and prices along with extra features.

do you means the original line is thin one but we have to consider thick line that formed with possible less lag but removing some tiny false signal on purpose "as a result" .

regards

mntiwana

No. The original corrected average was always the thick line. But the color of that line was determined by the cross of the underlying average (thin line) and the corrected average (the thick line) - I decided to add an option to have a color of the corrected average on slope, not just on those crosses

 
mladen:

mntiwana

No. The original corrected average was always the thick line. But the color of that line was determined by the cross of the underlying average (thin line) and the corrected average (the thick line) - I decided to add an option to have a color of the corrected average on slope, not just on those crosses

Dearest MLADEN

Thanks for early response,understand exact ...... so the thin underlying line is of same average but with few faster periods only

if there any difference (code wise) in between corrected averages and your bundle package Averages (37) ..... or the only difference with extra underlying line that help change coloring (as an option) and capable removing few tiny signals along side a bit possible lag.

regards

 
mntiwana:

Dearest MLADEN

Thanks for early response,understand exact ...... so the thin underlying line is of same average but with few faster periods only

if there any difference (code wise) in between corrected averages and your bundle package Averages (37) ..... or the only difference with extra underlying line that help change coloring (as an option) and capable removing few tiny signals along side a bit possible lag.

regards

mntiwana

The thin line is the average (the same as in the averages indicator)

The thick line is the corrected average - that is that same average but "corrected" only if the change of the average exceeds the desired deviations amount (something similar to the "filters" we are using). Try setting the "number of deviations" to 0 and you shall see that you are going to get exactly the same value as the averages since in that case there is no correction that needs to be checked

1...134113421343134413451346134713481349135013511352135313541355...1519
New comment
Reason: