swami stochastic needs some additional explanation ...

The stochastic used in it is not a built in stochastic. It is a kind of a 2 times EMA smoothed stochastic. Smoothing periods are fixed (first EMA 3 smoothing is applied to numerator and denominator of stochastic calculation and then the stochastic itself is smoothed by a 9 period EMA). So, it is rather far from the built in stochastic indicator

In order to implement different types of averaging I will need to solve a problem of processor usage first. That (along with big number of objects it creates) is the biggest problem. Swami indicator with default settings behaves like 42 separate indicators (42 different stochastics is calculated in order to show those values) With some different types of smoothing it would add significant CPU usage. If I find some acceptable solution I will most certainly post it here since I too think that the composite stochastic it is constructing is remarkably robust (was even surprised f that - Ehlers version does not have that composite value at all, and I was surprised that they overlooked the possible usage of it since it seemed as a logical idea).

Posted via email from newdigital world