I just wanted to be explicit as there are times in the stochastic oscillator where either the %K or %D value hits the top or bottom and starts flattens out.
In which case the data being put out would satisfy %Kp = %Kc or %Dp = %Dc,
and if it satisfy this, I don't want any order being triggered.
You mentioned in point #2 you explained the condition with 'passes' or 'does not pass', but I think it goes deeper than that.
If you look at the block explanation:
alt text
It states that the yellow node is active when the 'opposite comparison is valid.'
Which means if the %Dp < %Dc is not satisfied,
then what passes next is %Dp > %Dc,
not simply that %Dp < %Dc does not pass.
For example while looking to get a buy order (after %Kp < %Kc is satisfied),
I explicitly need buy orders triggering when %Dp < %Dc and as well as %Dp > %Dc is satisfied.
But what da hell do I know, I just started using this 😛
I will look over my logic tree to weed out the redundancy for sure.
Any future post I'll utilize the tips you've given me, I think it's a better way of sharing ideas.
And I'll be sure to check out the tutorial you sent my way,
I think it'll be absolutely beneficial!