Based on the Auto-Line code, the Efficient Auto Line aim to provide a more controlled adaptivity of the indicator. The first indicator of this sort worked this way : when the absolute difference between the price and the indicator is higher than the previous indicator +/- A pips of amplitude, the indicator will display the closing price, else its anterior value. The second indicator (Auto-Line) was adaptive and used the standard deviation instead of a constant A. This indicator will run both methodology providing both a trend strength indicator (Efficiency Ratio) parameter and two constant parameter.
Parameters
The length parameter will control the period of the efficiency ratio, a high period return lower values of the efficiency ratio. Since its an indicator in a range of (0,1) we use it to make our indicator more adaptive in trending market, this is when we need our two constant parameters, the fast/slow parameter can be any amount of pips where fast < slow, when the price is trending (efficiency ratio close to 1) the indicator will use the fast parameter, if its ranging (efficiency ratio away from 1) the indicator will use the slow parameter, then it will work like the first methodology previously explained. So the fast parameter should be equal to a small movement of pips (0.0001 or 1 pip) and the slow parameter should be equal to a number of pips you wont expect to see in a ranging market. At this point it is good to test for both parameter and see which values work better (a more automatic process is in development).
You’re a treasure and I always appreciate your work and words. Obviously time is tight, but I for one would love if you published an educational idea like the one you done recently exploring “Approximting a Least Square Moving Average in Pine”. Whatever you do, keep it up, you’re amazing
ICEKI
⋅
Wow good work, I will definitely, thanks for shared =D
jaggedsoft
⋅
Keep up the great work
UnknownUnicorn15320316
⋅
pine v5 pleASEE
navyreal7
⋅
Alex, hello, I want to create alerts for this indicator with such a block alertcondition(change(a)>0,title="Long") alertcondition(change(a)<0,title="Exit") But in practice I see a lot of duplicate signals if the notification is "once per bar". what can be done so that the signal is not duplicated? I ask because other indicators with color do not have this undesirable effect
navyreal7
⋅
thanks Alex, you great
spmforextrading
⋅
Nice!
dpanday
⋅
Is it possible to create a strategy for this? Would be great if the signals can be displayed a couple of bars earlier then the change of the line color! :)
alexgrover
⋅
@dpanday, Of course it could be possible to make a strategy using this indicator, but what do you mean by displaying signals earlier than the change of colour ?
dpanday
⋅
@alexgrover, Converting this to a strategy and display the signals based on the change of colour are a couple of bars too late and will result in loss per trade.