Entry point:

Currently we enter pending trade AFTER bar close.

If so, why enter on the High+xx (for LONG) or Low-xx (for SHORT)?

We can enter a Buy-Stop at the Close+xx (Long) or Sell-Stop at Close-xx (Short).

We can also enter Buy-Limit at the Close-xx or Sell-Limit at Close-xx.

(or even BOTH, as KIAD suggested…)

G.

You decide which version of the Peak&Trough to use.

Once decided, I prefer the iCustom call to external indicator in initial development, and later on, once stabilized, convert it to MQH.

Make the decision among yourself based on actual results – and ignore my preference.

Let’s move on with a conclusion on this.

G.

If you read my posts on the subject: I’m all in favor for MQH file in the FINAL version.

For the timebeeing I prefer iCustom calling of the external indicator, for easy debugging and visualization.

iCustom doesn’t add lines of code, because the indicator is a separate, stand-alone, MQ4 file.

Furthermore, that indicator can be used, monitored,…[Read more]

What I see on chart is a Relative-Currency-Strength, which can benefit the current EA in several ways.

It can be used as a scanner to select which currency-pairs to trade, and in which direction.

It can also be used as a confirmation to the main logic.

Both of the above features are more than welcome to this thread EA.

G.

How does that indicator perform whithin the EA?

G.

I don’t know how many times is needed to request the use of iCustom ….

I already stated that the Peak&Trogh function needs completion before moving on, but instead we get more and more “logic” features and additions.

This is good, and I’m not against it, but lets focus on completing the MAIN logic first !!

G.

I don’t know how many times is needed to request the use of iCustom ….

I already stated the the Peak&Trogh function needs completion before moving on, but instead we get more and more “logic” features and additions.

This is good, and I’m not against it, but lets focus on completing the MAIN logic first !!

G.

We can’t use or evaluate ex4.

Both the “multi instance function” and the CS is more than welcome, if supplied in source code.

The Penguin EA is based on Peaks & Trough areas as main logic, with optional CS and other logic as supporting features.

That main logic is already proven as profitable on all 7 Majors, so we continue to base on that…[Read more]

General functions:

//Auto TakeProfit
if (TP==0.)
{
tp = SL()/Point*TP_Factor;
}
else
{
tp = TP;

}

//Auto StopLoss

if (SL==0.)
{
sl=SL()/Point;
}
else
{
sl = SL;

}

//Auto Lot calculation
if (Lot==0.)
{
Lots = CalcLot(sl);
}
else
{
Lots = Lot;
}

G.

V.1.2 is WORSE than initial version, when compared to ALL 7 Majors with sames params.

Since the initial version is our base-line, we need to check and modify the cause, before adding more features/filters.

The importance of checking the EA on ALL 7 majors is in the fact that it reflects various market conditions, like different volatility, DD,…[Read more]

Thanks  VlanFx !!

Remarks to v1.2:

SwingPeriod – Not needed

Missing functions before main logic:

FFCAL -> avoid trading before and after news (default 30 min.)

Max. Spread -> Don’t trade if Spread >max.

Trading Hours -> trade only from StartHr (int) to EndHr (int)

TradeOnMonday -> allow trading on Monday (true/false)

TradeOnFriday -> a…[Read more]

Thanks  VlanFx !!

Remarks to v1.2:

SwingPeriod – Not needed

Missing functions before main logic:

FFCAL -> avoid trading before and after news (default 30 min.)

Max. Spread -> Don’t trade if Spread >max.

Trading Hours -> trade only from StartHr (int) to EndHr (int)

TradeOnMonday -> allow trading on Monday (true/false)

TradeOnFriday -> a…[Read more]

The above is the main reason why I want to use iCustom with visual indicator instead of MQH lib.

The MQH can come later, when everything is stable.

G.

The above is the main reason why I want to use iCustom with visual indicatorinstead of MQH lib.

The MQH can come later, when everything is stable.

G.

Hi Brother, forgive me for my noob idea..

1. You could use MA for this averaging , and you could use
double MathAbs(
double value // numeric value
);

to make all the calculation in positive value.
for example ;

//for your 1st question
AverageRange{i} = MathAbs ( iMA(Symbol(),NULL,InpAveragePeriod,0,0,PRICE_CLOSE,i)
-…[Read more]

Hi Brother, forgive me for my noob idea..

1. You could use MA for this averaging , and you could use
double MathAbs(
double value // numeric value
);

to make all the calculation in positive value.
for example ;

//for your 1st question
AverageRange = MathAbs ( iMA(Symbol(),NULL,InpAveragePeriod,0,0,PRICE_CLOSE,i)
-…[Read more]

Hi Brother, forgive me for my noob idea..

1. You could use MA for this averaging , and you could use
double MathAbs(
double value // numeric value
);

to make all the calculation in positive value.
for example ;

//for your 1st question
AverageRange = MathAbs ( iMA(Symbol(),NULL,InpAveragePeriod,0,0,PRICE_CLOSE,i)
-…[Read more]

Hi Brother, forgive me for my noob idea..

1. You could use MA for this averaging , and you could use
double MathAbs(
double value // numeric value
);

to make all the calculation in positive value.
for example ;

//for your 1st question
AverageRange = MathAbs ( iMA(Symbol(),NULL,InpAveragePeriod,0,0,PRICE_CLOSE,i)
-…[Read more]

I can understand the “excitement” coming with this Peak&Trough, but please stay focused.

We want the Peak&Trough to be a callable FUNCTION within the EA.

We currently want only one TF – which is H4.

We want the function to use iCustom calls to a viewable indicator, for easy debugging.

MQH, MTF’s, Trend, etc etc…. will come later, after…[Read more]

Good job!!

Just verify that the external buffers/indexes are accessible to the EA and logic is Ok.

Also, verify that the results according to our base-line results on all 7 Majors, with same params.

Make a function, based on that indie,  that returns entry signal to the penguin EA, replacing the current one.

Pls post indie + function…[Read more]