Stochastic Direction Confirmation

[mw417]

Hey there folks,

I just got into fxdreema and I gotta say it's a great and powerful tool.
Having said that, I'm still new to the usage and the question I'm about to ask might be covered here some where but at least I wasn't able to find an answer.

I'm trying to have a condition set up where if it detects that the K and D period lines are both pointed upwards it will trigger a buy.
I tried using the 'Indicator Rise' function but I don't think it's simulating my idea right.
How would I go about arranging which blocks to get the condition set up?

Much thanks for everything

[SydneyFox]

How do you determine that it's "pointed upwards"? i.e. what is the definition you are using to determine pointing upwards?

Is it say higher values for each of the past 3 days? Or higher value today than x days ago?

I'm no expert at this but might be able to help with a basic idea if you can give a bit more information.

[mw417]

@sydneyfox

Firstly, thanks for stopping by and taking the time to help out Sydney.

My logic is that when %K value of 3 periods ago,
(i.e. so three one hour candles on H1, three one day candles on D, etc.)
and the %D value of 3 periods ago, is higher than the current %K and %D value,
then it will be determined as it being 'pointed downward'.
Vice versa,
if the %K and %D value of 3 periods ago is lower than the current %K and %D value,
then it will be determined as it being 'pointed upward'.
The explanation might seem confusing so here's another way:

Let,
K0 = current %K value
K3 = %K value of 3 period ago

D0 = current % D value
D3 = %D value of 3 period ago

If
K3 > K0 and
D3 > D0, then it is upwards.
If
K3 > K0 and
D3 < D0, then it is upwards.

If
K3 < K0 and
D3 > D0, then it is downwards.
If
K3 < K0 and
D3 < D0, then it is downwards.

I hope I was able to deliver the right type and the amount of information you needed.
Let me know if you need any other details.
And again, thanks for helping out.

[SydneyFox]

Something like this perhaps? https://fxdreema.com/shared/687P7ImN

[mw417]

@sydneyfox

Oh this is brilliant. This is definitely along the lines of the functions I'm trying to create.
So I understand Signal line to be the %D line and since I want to be comparing previous %D values to the current %D values at one point,
I changed the Right Operand's mode to Signal line of block 2 and block 5.
Now there was another condition that I wanted to apply, which was basically taken care of because the condition blocks offered the yellow node which triggers "When the opposite comparison is valid."

So the logic essentially being this:

And with your guiding help I have come up with the following:

For future reference,
how do I go about uploading indicator files back to fxdreema?
how do I go about sharing a fxdreema project link on forum posts?

Always much appreciation being sent your way.

[SydneyFox]

With what you've written above I don't think you need the condition blocks for the Signal Line. On the left hand side of your diagram you have:

1. If %Kp < %Kc passes then
2. If %Dp < %Dc passes then Buy Now or if %Dp < %Dc does not pass then Buy Now.

i.e. it doesn't matter if %Dp < %Dc passes or not. As long as %Kp < %Kc passes then it will get to Buy Now.

I think you need to re-look at your logic.

I've only once used an indicator that wasn't available in fxDreema. I used this link to figure out what I needed to do https://fxdreema.com/tutorial/builder/indicators.

To share a project click on Projects -> Create a Shared Copy (web link). This will bring up a pop up box and you click on Get a Link. This gives a link that you might just be able to copy and paste into your message? What I do is click on this link which opens up your project in a new tab. I then copy this link from the browser and paste into my message. I might be doing one step more than is needed.

[mw417]

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:

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!