Please accept my apologies. I have made a mistake.
buf1 is fast (3 for example)
buf2 is slow (5 for example)
Hi Marcelo, note that using such small period (3 or 5), and the moving average method as an input parameter, are you sure your setup is not inverted sometimes? (SMA for fast and EMA for slow, for instance)
Hi Marcelo, note that using such small period (3 or 5), and the moving average method as an input parameter, are you sure your setup is not inverted sometimes? (SMA for fast and EMA for slow, for instance)
Hummm ... to be honest I don't like this solution to filter slow/fast periods and I think this is your root problem, since you are changing periods and handles ...
Hummm ... to be honest I don't like this solution to filter slow/fast periods and I think this is your root problem, since you are changing periods and handles ...
I suggest you filter some method combinations too, for instance if the fast MA method is MODE_SMA and slow MA method is MODE_EMA, to avoid new inversions of logic when periods are very near values:
I suggest you filter some method combinations too, for instance if the fast MA method is MODE_SMA and slow MA method is MODE_EMA, to avoid new inversions of logic when periods are very near values:
Can someone please help me
on this ? (figurelli it just happened ... is this what you were explaining?)
Picture 1 shows my EA MA
configuration.
Fast MA is 3 Smoothed and
Slow MA is 4 Exponential.
Probably because of the
TYPE, Slow MA (4) crossed from bottom to top starting a SELL position (picture
MMA2) instead of BUY position. As you see, the MA4 is below MA3.
How can I avoid this? Does
it have any kind of specification about MA with closer values and its type?
Please accept my apologies. I have made a mistake.
buf1 is fast (3 for example)
buf2 is slow (5 for example)
Hi Marcelo, note that using such small period (3 or 5), and the moving average method as an input parameter, are you sure your setup is not inverted sometimes? (SMA for fast and EMA for slow, for instance)
Hi Marcelo, note that using such small period (3 or 5), and the moving average method as an input parameter, are you sure your setup is not inverted sometimes? (SMA for fast and EMA for slow, for instance)
I do not think so ... check
I do not think so ... check
Hummm ... to be honest I don't like this solution to filter slow/fast periods and I think this is your root problem, since you are changing periods and handles ...
Hummm ... to be honest I don't like this solution to filter slow/fast periods and I think this is your root problem, since you are changing periods and handles ...
I do not think so ... check
I suggest you this approach :
I suggest you this approach :
Here is ... Thank you
Alain approach is nice.
I suggest you filter some method combinations too, for instance if the fast MA method is MODE_SMA and slow MA method is MODE_EMA, to avoid new inversions of logic when periods are very near values:
Alain approach is nice.
I suggest you filter some method combinations too, for instance if the fast MA method is MODE_SMA and slow MA method is MODE_EMA, to avoid new inversions of logic when periods are very near values:
Here is ... Thank you
Hi !
Can someone please help me on this ? (figurelli it just happened ... is this what you were explaining?)
Picture 1 shows my EA MA configuration.
Fast MA is 3 Smoothed and Slow MA is 4 Exponential.
Probably because of the TYPE, Slow MA (4) crossed from bottom to top starting a SELL position (picture MMA2) instead of BUY position. As you see, the MA4 is below MA3.
How can I avoid this? Does it have any kind of specification about MA with closer values and its type?
Regards,
Marcelo