Trying to find turning point based on PRICE leads to std. Fractals, which are lagging by at least 2 bars.

Furthermore, the entry will be on the close of the second bar.

Can we do something better than that? or more reliable, eliminating false entries?

G.

Like I said: another SPAM post from him and I’ll notify him to Facebook, LinkedIn, YouTube as Spammer.

G.

Let’s focus on one issue at a time.

Currently the task is creating a highly reliable Peak & Trough functions.

Defining Trend will be the next.

G.

Please DON’T try to make a trading system. We’ll get to it in small steps.

For now we only need a rigid, reliable, minimal lag, minimal false-signal Peak & Trough Functions.

The next step will be the same rigid, reliable, minimal lag, minimal false-signal Trend Function.

G.

Please DON’T try to make a trading system. We’ll get to it in small steps.

For now we only need a rigid, reliable, minimal false-signal Peak & Trough Functions.

The next step will be the same rigid, reliable, minimal false-signal Trend Function.

G.

If you want to use some kind of “smoothing” don’t use MA’s.

You can use some kind of second order Low-Pass filter.

G.

White bars are either “Doji” or engulfed bars, i.e. no significant price movement.

G.

White bars are either “Doji” or engulfed bars, i.e. no significant movement.

G.

There is no true Volume in Forex.

The parameter “Volume” in Data-Window is actualy Tick-Volume – which is the number of times the price is changed during TF.

This number is coming to the broker from Interbank. From testing it’s quite good reference to Futures Volume, like 90% correlation. Not by actual number, but by the relative relation to…[Read more]

Engulfed is already eliminated in the function initial definition:

“…A new high is made (in an uptrend) or a new low (in a downtrend)…”

G.

In your code you defined “Range” as (High-Low). It should be MathAbs(Close-Open). See same question & response by SmallCat.

Also I think it will more beneficial to display results on-chart and not in a separate indicator window, but that’s me…

Didn’t check further than that.

If you want to further extend it to Trend, please make it as a…[Read more]

In your code you defined “Range” as (High-Low). It should be MathAbs(Close-Open). See same question & response by SmallCat.

Didn’t check further than that.

If you want to further extend it to Trend, please make it as a separate function – like defined in the “Trading made really simple” thread.

Thanks for your efforts!

G.

Furthermore, others need basis to improve, add ideas and further enhance. That’s the aim of this “drill” – and it relates to the new topic “Trading made REALLY Simple”.

G.

Furthermore, others need basis to improve, add ideas and further enhance. That’s the aim of this “drill” – and it relates to the new topic” Trading made REALLY Simple”.

G.

This is a Volume-based early warning of exhaustion, when even volume cannot extend the range and even closed BELOW the High or ABOVE the Low.

Higher-High and/or Lower-Low can only be determined AFTER the fact, by watching next bars.

That’s the reason why std. ZZ  & Fractals are lagging by at least 2 bars/candles.

G.

This is a Volume-based early warning of exhaustion, when even volume cannot extend the range and even closed BELOW the High or ABOVE the Low.

Higher-High and/or Lower-Low can only be determined AFTER the fact, by watching next bars.

G.

MQ4 please. I don’t download voodoo charms.

G.

Just to clarify:

Volume greater than previous bar volume

Range less than previous bar range

A new high is made (in an uptrend) or a new low (in a downtrend)

Closes below the high (in uptrend) or below the low (in downtrend)

G.

talha yeasin,

How much do you pay for clicking the link?

From your profile: Talha Yeasin. Not so good: SEO expert | link builder | Effective Keyword

Do you want us to bann you from Facebook & LinkedIn, etc.?

Just another post like this B.S. one – and it will happen.

G.