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 : Technical Analysis - Beginners -- Ignore unavailable to you. Want to Upgrade?

To: Chris G. who wrote (7305)	12/21/1997 12:57:00 PM
From: Tim Fierro	Read Replies (1) \| Respond to of 12039

But this still doesn't account for getting buy signals when the OBV<40, and it's occurring about 30% of the time. Richard mentioned it might be data errors, so I'm thinking of reloading the data one last time. Have you had similar problems Craig? Chris, here is a way to test... I make a new formula: TEST FORMULA IF(OBV(0) >= OBV(40), 1, 0) TREND(0,0) Basicaly I test ONE formula for a TRUE response. If it is true, it will show a spike to 1. If it is false, it will stay at Zero. The above is for WOW, but you should be able to understand it and convert what is necessary to check in Metastock; I think that is what you said you were using. If you get a spike, then today's OBV is greater than it's 40 day OBV value. See if it spikes when it shouldn't and adjust the formula to what it should be. BTW, I only guessed at the above formula for you to try. In QPLUS you need negative numbers to go back in time. You might also want to see if it just higher that 40 days ago or are you really after IS TODAY GREATER THAN THE 40 DAY AVERAGE? So is OBV < 40 mean is OBV less than 40 shares or does metastock mean OBV is less than 40,000? Recheck using the IF statement to see if what you are trying to build is really being built. Tim

To: Chris G. who wrote (7305)	12/21/1997 9:38:00 PM
From: Craig DeHaan	Read Replies (1) \| Respond to of 12039

Chris, In the formula ----------------------------------------------><----------------------------->< Mov((RSI(14)-LLV(RSI(14),14))/(HHV(RSI(14),14)-(LLV(RSI(14),14)+.000001)),14,E)*100 should be optional, but the .000001 would be added to the entire composite of the moving average data array and not just the LLV part of the denominator. You're probably technically correct here, but it cured the errors for me. I think when I originally pasted from Andy's site MS kept forcing me to remove that pair. Whatever. Another mystery of TA software. As for the OBV() function, I use it without any ill effects as OBV() > Mov(OBV(),40,S). Remember that it is a cumulative type indicator that might be dependant on the amount of data loaded into the exploration. I can't say that I've had to do anything unusual to make it work, but check it out by using Explorer \| Options and forcing more data rather than the minimal amount. I had a problem using the Alert() function a month ago for a similar reason. I'd try this before reloading QP database. Craig