Old and defunct Holy Graily Bob

[SteveHopwood]

why does this thing close all other pending trades on other pairs soon as it opens a trade ? and how can we prevent it from closing the other pending trades ?

This fella reported the same thing - don't know if they're doppelgangers ...

Good point. Another account bites the dust.

[jiraiye]

Dear All,

Spotted a slight error in V2t Line 2338.

Code: Select all

   if (TrendWaveBuyTotalTrades + TrendWaveSellTotalTrades >= TrendWaveMaxMultiTrades)

it should be coded the following way:

Code: Select all

   if (TrendWaveBuyTotalTrades + TrendWaveSellTotalTrades >= TrendWaveMaxTradesAllowed)

[traderduke]

Yes, but i would like to know how people are going, i have seen the system have a series of stop out in certain conditions and or if the market it changing direction, I just would like to know if people are experiencing the same as i am.....

Regards
Wiggy

If you trade H4, a lot of the entries this week have been counter to the daily signals.

Absolutely, many pair made some retracement.

I went from over 4.500 floating to just over 2.000 pips yesterday [D1 trading, no TP] with 24 trades open.
Yesterday -700, today +300 closed on this demo.
Some feed-error screwed my test, will continue.

I want to find out how much is given back in retrace before a yellow wave prints on the D1.

Wiggly
I have been trading the HGI trend & rad using the 10.7 stochs on a 4h chart manually & I find the 10.7 keeps me out of trouble/DD 2 out of 4 times. I realize HGB is a monster to code but could the 10.7 option be added for the trade decision?? I tried copying it from other Ea's but to no avail.

What do you think Steve??

regards

Ray

[SteveHopwood]

Dear All,

Spotted a slight error in V2t Line 2338.

Code: Select all

   if (TrendWaveBuyTotalTrades + TrendWaveSellTotalTrades >= TrendWaveMaxMultiTrades)

it should be coded the following way:

Code: Select all

   if (TrendWaveBuyTotalTrades + TrendWaveSellTotalTrades >= TrendWaveMaxTradesAllowed)

Nice spot. Thanks.

I won't put up a fix straight away - it is an insignificant little bloop. I will wait until a few more thingies have waved a flag at us.

[SteveHopwood]

Wiggly
I have been trading the HGI trend & rad using the 10.7 stochs on a 4h chart manually & I find the 10.7 keeps me out of trouble/DD 2 out of 4 times. I realize HGB is a monster to code but could the 10.7 option be added for the trade decision?? I tried copying it from other Ea's but to no avail.

What do you think Steve??

regards

Ray

You will have to remind me how it works first - I have forgotten.

[spgandau]

Hello Steve,
I am still occasionally surprised by the message "Global Profit Target Reached". It is code issue...at least for me.
here is what I have found (1st issue I referred to earlier, 2nd issue is recent)
line 6225 is the function HaveWeHitProfitTarget()
lines 6237 thru 6239 filter out trades to be considered in assessing whether or not the profit target has actually been reached.

line 6239
I replaced it, because it was incorrectly allowing trades from prior weeks be counted as part of "today's" profit assessment.

modified line 6239 now reads.
if (OrderCloseTime() < iTime(Symbol(),PERIOD_D1,0) ) continue; //order was closed before today, ignore it.

I also discovered that in the function HaveWeHitProfitTarget() each EA looks at ALL pairs, ALL trades and determines profit levels and shuts down the EA...which is fine. However, I actually wanted to have the EA determine if the current pair had reached a profit target for today, and ignore all other pairs in that determination. (I use HGBB to determine global profit levels and stop all EA activity)

So, I also inserted the following line, at line 6238:

if (OrderSymbol()!=Symbol() ) continue; //this filters so that only THIS symbol trades are checked.

I have modified my HGB with these two lines. Perhaps, others will find this useful, if they are getting unexpected "Global Profit Targets Reached" messages. Just one idea that might help.

Cheers!

[spgandau]

Hello Steve,
Line 5050 shows:

bool result = ModifyOrder(OrderTicket(), OrderOpenPrice(), OrderStopLoss(), take, OrderExpiration(), clrNONE, __FUNCTION__, slim);

I believe it was intended to read:

bool result = ModifyOrder(OrderTicket(), OrderOpenPrice(), OrderStopLoss(), take, OrderExpiration(), clrNONE, __FUNCTION__, tpim);

Am I correct?

Cheers!

[spgandau]

Hello Steve,
Line 6113 shows:

result = ModifyOrder(OrderTicket(), OrderOpenPrice(), OrderStopLoss(), take, OrderExpiration(), clrNONE, __FUNCTION__, slim);

I believe it was intended to read:

result = ModifyOrder(OrderTicket(), OrderOpenPrice(), OrderStopLoss(), take, OrderExpiration(), clrNONE, __FUNCTION__, tpim);

Am I correct?
(I am not trying to be a bother, but I am chasing the 141 ("too many requests") error code and and discovering this along the way.)

Cheers!

[SteveHopwood]

Hello Steve,
Line 6113 shows:

result = ModifyOrder(OrderTicket(), OrderOpenPrice(), OrderStopLoss(), take, OrderExpiration(), clrNONE, __FUNCTION__, slim);

I believe it was intended to read:

result = ModifyOrder(OrderTicket(), OrderOpenPrice(), OrderStopLoss(), take, OrderExpiration(), clrNONE, __FUNCTION__, tpim);

Am I correct?
(I am not trying to be a bother, but I am chasing the 141 ("too many requests") error code and and discovering this along the way.)

Cheers!

.


Yes you are indeed correct - one of my umpteen copy/paste bloops. Thanks again.

No need to worry about being a bother. These are minor bloops that will have no impact on the majority of users, but accurate code is always better than inaccurate code.

Still not posting fixes guys - no need for now. I will post them in time for trading next week.

[trendinator]

having a look through some of the trades in the forward test i came across lots of TrendWave trades that were closed after a few seconds and then reopened 10 mins later.

CADJPY_TRENDWAVE.JPG