The indicator is for experimental purpose only, it must not be used as a decisional tool but only as a visual one (like , etc). The information this indicator display is uncertain and subject to drastic changes over time. If you have further question feel free to pm me.
Most of the filters you will find are causal, this mean that they depend on present and past input values, this explain the lag they produce. Non causal filters however will use future input values. A well know way to get a zero-phase filter is by using the forward backward method, but this is not possible in pinescript as i recall. So we have to use some kind of function that will display future values, this is possible using the security function in version 2 or the one in version 3 using barmerge.lookahead_on.
The Use Of A Repainting Indicator
Its always better to filter data in order to have a clearer view of what is happening, this can be useful when doing some forecasting or doing less formal kind of analysis. However since it repaint you cant use it as a signal provider or use signals of other indicators using this filter as source.
For example if you want to forecast a smooth indicator, the forecast of this indicator under normal circumstances could still have lag associated with it, so you would have to react before your forecast, this wont happen if you apply this filter as your indicator source.
We smooth with a the price provided by the security function twice, length control the smoothing level. Since security depend on the time frame you are in you must select your time frame in the indicator parameter selection window.
Filtering using 45 minutes time frame close price in a 5 minutes chart, we fix this by selecting our time frame.
Consider the fact that the input of the indicator is just periodic price, so sometimes the lag can sometimes be less or more than 0 and the estimation not centered.
The indicator can work on time frames up to 1h, after that the filter have some lag, i tried fixing this and i ended up having data errors.
Applying our filter as source for the oscillator.
It is possible to have a kind of zero-phase filters, but it would be better if pinescript could support backward indexing thus making us able to do forward backward filtering.
Since noise can affect our analysis, applying smoothing without having to use offset in plot can be considered useful.
« Je prendrai l’essor et je m’envolerai vers la mer.
« Je connaîtrai le goût des brises du large. J’entendrai les grands cris de la tempête.
All the same, thank you for leading the vanguard in Pine. I hope the new version allows you to realise some of the ideas you have.
pine_ema(_tf, _src, _length) =>
// alpha = 2 / (_length + 1)
// sum = 0.0
// sum := alpha * _src + (1 - alpha) * nz(sum)
_alpha = 2 / (_length + 1)
_sum = 0.0
for _at_time = _length to 0
_tf_src = valuewhen((change(time(_tf)) != 0), _src, _at_time)
_previous_sum = nz(_sum, 0.0)
_sum := _alpha * _tf_src + (1 - _alpha) * _previous_sum
but i digress out of context now :p