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 : The 56 Point TA; Charts With an Attitude -- Ignore unavailable to you. Want to Upgrade?


To: Doug R who wrote (24894)1/2/1999 7:50:00 PM
From: milesofstyles  Read Replies (1) | Respond to of 79230
 
my data in parity matches that of craig's readings in mswin, again, we are all using qp2 data i am guessing,and for the most part is pretty clean. i don't think there is a calculation difference in parity that i can see. my data shows three higher lows below 20 dating back to early september in both parity and qp2
9-3...10-7...11-23...
this is the formula listed in qp2
%K = 100[ (C - L5) / H5 - L5) ]
i believe the 5s to be an example period...but looks the same to me as the one you have listed for parity.
i have noticed differences in the short sto's and this may have lead to my misintrepretation basis of the sto e vs s and also a recent misintrepation on my part of a study regarding a comparison of the calculation of the simple and exp, which found the exp more favorable.

milesov



To: Doug R who wrote (24894)1/2/1999 8:41:00 PM
From: Craig DeHaan  Read Replies (1) | Respond to of 79230
 
Doug,

If that Parity 'doohickey' (I luvit) stoch formula is actually using
%K = 100[(C - Lxclose)/(Hx - Lx)] its more akin to a low-bias W%R w/ inverted scaling. W%R is:

((HHV(C,NPer)-C)/(HHV(H,NPer)-LLV(L,NPer))) * -100

%K stochastic calcs in most TA sw use C-Lx [C-LLV(L,NPer)] for the numerator vs LxClose [C-LLV(C,NPer)]. Curiously, what should be happening output-wise with your lil' doohickey is lower values at both low and high scale extremes. I'm thinking this JBM inconsistency must mostly be a case of data influenza... or is it just more voodoo?

Now we'll never ween you to MSWIN/QP.

CP