TickScalper EA - page 73
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Good. Happy trading :)
Could not resist to make a small change though - this version automatically adjusts the color to the chart color so the user does not have to adjust the color of the part that is supposed to hide the histogram (otherwise it does it only on black charts). So this one looks a bit nicer :). Also this version has a timer (a real timer, when it is required to use seconds as an interval, not when ticks are counted), so, in that case, it will work even when no new ticks are generated
PS: that change of the code is included too
PPS: due to real time usage, the result will probably be different (especially for small time intervals, when the indicator does not depend on ticks coming in but generates its own data even when there are no ticks)
Ok, I will try the new version.
BTW, I find it is very hard to review ticks data in MT4, consider exporting it to socket, so make life easier.
Ok, I will try the new version.
BTW, I find it is very hard to review ticks data in MT4, consider exporting it to socket, so make life easier.
Try using the tick data indicator (from here https://www.mql5.com/en/forum/185296 for example)
Yes, it's a option.
thanks
PS: https://www.mql5.com/en/articles/1361"
WORKING WITH SOCKETS IN MQL, OR HOW TO BECOME A SIGNAL PROVIDER"
will be a good start.
Hi mladen,
I'm trying to understand the idea of TickScalper_v3.44.mq4. And get confused by the code:
double TickSmoother(int mode,int tf,int price,int fast,int slow,int mamode,int numt,int nums,int maxb,int bar)
{
......................
double lim=0.95*iClose(NULL,0,0);
bool ok = tClose > lim && fastMA > lim && slowMA > lim && tClose1 > lim && fastMA1 > lim && slowMA1 > lim;
bool ok1 = confMA1 > lim && confMA2 > lim;
if(ok) ok=true;
if(ok1) ok1=true; I see you change the code in 3.5 :)
......................
if(mode==1 && ok) { ...................... }
else if(mode==2 && ok) { ...................... }
else if(mode==3 && ok && ok1) { ...................... }
else if(mode==4 && ok && ok1) { ...................... }
else if(mode==5 && ok && ok1) { ...................... }
else if(mode==6 && ok && ok1) { ...................... }
else if(mode==7) { ...................... }
else if(mode==enum_Enum_TS_Mode_Averages_Macd && ok && ok1) { ...................... }
else if(mode==9 && ok && ok1) { ...................... }
else if(mode==0) result=0;
return(result);
}
By calling "TickSmoother" we may get some signal of tick data indicator.
double lim = 0.95 * iClose(NULL,0,0);
bool ok = tClose > lim && fastMA > lim && slowMA > lim && tClose1 > lim && fastMA1 > lim && slowMA1 > lim;
bool ok1 = confMA1 > lim && confMA2 > lim;
ok and ok1 act as filter( except mode 1,2,7), make it only return none 0 value when all the variables is above 95% of iClose[0]
Am I right?
If so how about the value higher than 105% of iClose[0] ?
PS: 95% means tick data is "kind of flat" for some time?
Hi mladen,
I'm trying to understand the idea of TickScalper_v3.44.mq4. And get confused by the code:
double TickSmoother(int mode,int tf,int price,int fast,int slow,int mamode,int numt,int nums,int maxb,int bar)
{
......................
double lim=0.95*iClose(NULL,0,0);
bool ok = tClose > lim && fastMA > lim && slowMA > lim && tClose1 > lim && fastMA1 > lim && slowMA1 > lim;
bool ok1 = confMA1 > lim && confMA2 > lim;
if(ok) ok=true;
if(ok1) ok1=true; I see you change the code in 3.5 :)
......................
if(mode==1 && ok) { ...................... }
else if(mode==2 && ok) { ...................... }
else if(mode==3 && ok && ok1) { ...................... }
else if(mode==4 && ok && ok1) { ...................... }
else if(mode==5 && ok && ok1) { ...................... }
else if(mode==6 && ok && ok1) { ...................... }
else if(mode==7) { ...................... }
else if(mode==enum_Enum_TS_Mode_Averages_Macd && ok && ok1) { ...................... }
else if(mode==9 && ok && ok1) { ...................... }
else if(mode==0) result=0;
return(result);
}
By calling "TickSmoother" we may get some signal of tick data indicator.
double lim = 0.95 * iClose(NULL,0,0);
bool ok = tClose > lim && fastMA > lim && slowMA > lim && tClose1 > lim && fastMA1 > lim && slowMA1 > lim;
bool ok1 = confMA1 > lim && confMA2 > lim;
ok and ok1 act as filter( except mode 1,2,7), make it only return none 0 value when all the variables is above 95% of iClose[0]
Am I right?
If so how about the value higher than 105% of iClose[0] ?
PS: 95% means tick data is "kind of flat" for some time?
I did not change that code
In any case that line of code is doing nothing - all is done in the
bool ok1 = confMA1 > lim && confMA2 > lim;line (two lines before the line you marked), and the line that you marked has no effect on anything executed after it - exactly the same as the line proceeding it - it is there the same as if it never was written there (check the logic of it and you shall agree after that with me). So, no need to think about it
As of the logic : if you check I am not the creator of that EA. It was one of the EAs that were attempting to work on the "wings" of SNB interventions in EUR/CHF, probably the logic was adjusted to that, but quite frankly I don't know exactly. Never discussed those issues with igorad
PS: what tick data indicator you are referring too?
????
what is "not under orders"?