SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Strategies & Market Trends : Technical Analysis - Beginners -- Ignore unavailable to you. Want to Upgrade?


To: Monty Lenard who wrote (11044)1/28/2001 7:43:44 PM
From: MechanicalMethod  Read Replies (1) | Respond to of 12039
 
adaptive average pseudo code, incomplete.

Var: len(0), adaptAvg(0), cSlope(0), avgSlope(0);

if c > c[1] then cSlope = 1; {+slope}
if c < c[1] then cSlope = -1; {-slope}

AdaptAvg = average(c,len);{old val of len}
if adaptAvg > adaptAvg[1] then avgSlope = 1; {+slope}
if adaptAvg < adaptAvg[1] then avgSlope = -1; {-slope}

if len > 3 and len < 21 then begin
if cSlope > 0 and avgSlope < 0 then len = len - 1; {speedup avg}
if cSlope < 0 and avgSlope > 0 then len = len + 1; {slows avg}
end; {price and avg diverging}

adaptAvg= average(c,len); {updated val of len}

plot1(average(c,8),”avg8”);{for comparison}
plot2(adaptAvg,”adaptAvg”);

~~~~~~~~~~~~~~~~
A separate indicator formatted as histogram tracks the value of len as it adjusts.

plot1(len,"len"); {this shows len stuck at 21 bug}
~~~~~~~~~~~~~~~~~~~
unresolved: store adaptAvg for each bar in array then average array values using each new adaptive length. Currently instead of averaging values that result from multiple parameters it changes parameter but doesn’t store result. Recalculations use new len on entire price series {bug}.

Theory: there are good reasons to speedup an avg besides correcting divergence between avg and price. One that comes to mind is only adapt when an additional condition is met such as price and avg must be crossed [convoluted] before slope divergence triggers a parameter adjustment. I’m not clear on that at the moment but have worked it and it’s straightforward, just slips my mind at the moment.

Decent beginning although it goes to len 21 and stays there I think without further adapting {a bug}. My intent is to use this with other than simple avg’s. First I need to get the values from each bar into an array so each new bar calculates on price but only adds the most recent value to the array which is my price proxie.

Mechanical Method



To: Monty Lenard who wrote (11044)1/28/2001 8:24:55 PM
From: TechTrader42  Read Replies (1) | Respond to of 12039
 
"Anyway, I think you should post that scan Brooke. It may be a good one after this bear is over."

I don't think the scan would be at all useful, Monty, except perhaps as a lesson in how not to trade.

One of the members of the group did some back-testing on it, and found that the section of it dealing with float turnover had no bearing on future performance. That was half the scan, and it was found to be useless, at least in those tests.

That leaves ATR, which was used in the scan to find stocks with relatively high volatility. This was at the height of the market, shortly before the crash. ATR was combined with high trade rate in QCharts to find volatile stocks, and the results were probably very interesting. ("Brother, can you spare a dime?")

Apparently, some of the group members are seeking professional help (in a manner of speaking), with a group called TCI (www.tcicorp.net). It's a company that offers investment education and trading systems. PTATR didn't do it for them, it seems.