Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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 : TA Science Projects & Experimental Indicators -- Ignore unavailable to you. Want to Upgrade?

To: HeyRainier who wrote (107)	4/5/1998 11:07:00 PM
From: ftth	Respond to of 237

Hi Rainier, I'm not entirely sure metastock can be used to implement the entire process--it may require more coding capabilities that it has. The basic operation could use nested IF statements, but the hysteresis would seem to need multi-element storage, i.e. arrays. Hysteresis, you ask? You made the comment << The problem with the MA switching according to certain thresholds is the MA's could switch almost daily if the volatility was right on the switch boundary>> And yes, that would be a problem, which is why I said: <<... although the downside thresholds should probably be lower than the upside thresholds (hysteresis, as it's called) so that if it happens to sit right at a threshold for a few days, it doesn't flail back and forth between 2 MA settings.>> It must not have been worded very clearly, but we're thinking along the same lines. We would need a variable to keep track of when each threshold has been tripped, and then change the threshold to the "downside" threshold. Would need to do this for each threshold, and maintain the value of the variable across calculations. Although that's pretty basic for a real programming language, I'm not sure M/S can do this. Will let you know if I find out. dh