Maybe,

else V = EMPTY_VALUE;

at first second of every candles in every TFs mostly, Open = Close = High = Low with Volume = 0,  So, ‘V’ should be ‘Empty’ first, before the loop change ‘her’ value later.. if  High-Low != 0.0.

Just my noob cent.. lol

MTH

Yes, you are right simplex. So, if  High==Low, it means there is no Volume, right ? So, we just don’t care about this candle …. or we take the previous one ? Any idea ?

What’s the purpose of this ?!?!

The logic is not completed yet, as well as the pre-trading conditions…

How was the initial version?

How often do you clear “long-ago” pending trades?

I really don’t understand this “test”… or its purpose…

G.

Yep, this is obviously true:

IMO, the really interesting question is: how does the else if branch look like? You can exclude division by zero easily by some standard code, but you’ll have to make an individual decision what should be done after the case happened.

s.

Yep, this is abviously true:

IMO, the really interesting question is: how does the else if branch look like? You can exclude division by zero easily by some standard code, but you’ll have to make an individual decision what should be done after the case happened.

s.

Thanks for commission information G

Thanks brother. I just think like this :

MathPow(High – Low, -1)

does it means same as :

 1 / (High – Low)

So, it is actually a division operation … if i am not wrong …    but i could be wrong though …

Adding Commission distort the whole TRAILING process in MT4, since it is not included in the trailing calculation (besides the fact that the logic isn’t finished yet).

To simulate commission you should add it to the spread and multiply it by the lot size.

G.

actualRisk will later be used mainly for user display purposes.

G.

Hi Brother,  zero divide should involving division operation, while in your code example this is multiplication operation, so the result could be zero but not zero divide error.

From my noob perspective, before that line of code you could make sure by ‘if’ condition like;

if ( (High - Low) != 0.0 )

to protect zero result condition

Hope it…[Read more]

Hi Brother,  zero divide should involving division operation, while in your code example this is multiplication operation, so the result could be zero but not zero divide error.

From my noob perspective, before that line of code you could make sure by ‘if’ condition like  ‘if ( (High – Low) != 0.0 )’ to protect zero result condition

Hope it h…[Read more]

Hi all,

I got this line of code from other thread :

double V = ( MathAbs(Open – Close) * MathPow(High – Low, -1) ) * Volume;

Just want to make sure about zero devide. If the result of (High-Low)==0.0, then the equation MathPow(High-Low, -1)  will cause error. Is it right?

@pipatronic :  Thanks for info about Obv Div.   

Hi all,

I got this line of code from other thread :

double V = ( MathAbs(Open – Close) * MathPow(High – Low, -1) ) * Volume;

Just want to make sure about zero devide. If the result of (High-Low)==0.0, then the equation MathPow(High-Low, -1)  will cause error. Is it right?

Welcome mate. I haven’t tested v 1.3 yet (will test it soon), but as you know some other features are not implemented yet in this version . But looking at your result (although it is still getting some loss), yes it is promissing. I am sure after all requirements are fullfill (peak trough, osc, trend, etc), we will see a much better result. Try…[Read more]

Hi @VlanFx:

I’m currently reviewing version 1.3 of the EA. In function CalcLot() you have the following line of code:

actualRisk = (100 * minLot * StopLoss * pipValue) / AccountBalance();

That variable actualRisk is never used thereafter. Is it reserved for some future use?

s.

1) will need big space (using many different file name, although we can delete it later, but that is extra work)

2) ==

3) may be can reduce conflict of read⁄write in number 2)

4) i think should be ok … the master process can be changed⁄replace by slave process after master’s job is finish (a slave becomes a master process if nee…[Read more]

My version 1.0 of Volume Zone Oscillator. It consists of a simple indicator file, and an mqh-library which should be placed in the include folder.

In final and practical EA use, there will only be one line of code required:

varName = iiVZO(symb, tf, vzoPeriod, shift);

For debugging and optimizing the EA, a simple iCustom() call of the indicator…[Read more]

My version 1.0 of Volume Zone Oscillator. It consists of a simple indicator file, and an mqh-library which should be placed in the include folder.

In final and practical EA use, there will only be one line of code required:

varName = iiVZO(symb, tf, vzoPeriod, shift);

For debugging and optimizing the EA, a simple iCustom() call of the indicator…[Read more]