Old and defunct Holy Graily Bob

Post by **SteveHopwood** » Mon Dec 01, 2014 6:41 pm

Wapen » Mon Dec 01, 2014 6:26 pm wrote:
SteveHopwood » Mon Dec 01, 2014 8:13 pm wrote:Just to let you guys know, I had a quick look at the code and it only disallows new trades if there is already one open. It does not look at closed trades in the history tab.

Live with it for now, and I will add the fixes.

thanks for the feedback, Please just check the "Trailing Stop"

No. Got enough to do. Maybe you hadn't noticed?

Post by **SteveHopwood** » Mon Dec 01, 2014 6:50 pm

V 1c is in post 1, with some quick and dirty fixes for the latest bugs to crawl out of the woodwork.

I have added code to stop HGB sending, for example, a buy when there is a high wavy line that will cause a trade to be closed on the following tick. This will cause HGB sometimes to display a tradable signal which is not in fact traded. I will tidy this up if it becomes necessary.

I have also added code to stop HGB sending a new trade when one has opened and closed during the current candle. This is a blunt instrument fix, as it disallows all trading; I am making the assumption that a closure is not going to be followed immediately by an open in the opposite direction, or by an open inspired by a different trading strategy to that which caused the open in the first place. This could be a false assumption - this stuff is only a little less new to me than it is to you guys.

Coders
You will see how I have cancelled the signal in void ReadIndicatorValues().

The extra function I added is bool HaveTradesAlreadyClosedThisCandle(). This is called from within bool CanWeTrendTrade(int type), bool CanWeRangeTrade(int type) and bool CanWeRadTrade(int type). Please do say if you see any holes in the logic.

Post by **currymonster** » Mon Dec 01, 2014 8:38 pm

Deleted, being a numpty, just tasered myself, cheers

Cal

Post by **SteveHopwood** » Mon Dec 01, 2014 9:58 pm

currymonster » Mon Dec 01, 2014 8:38 pm wrote:Deleted, being a numpty, just tasered myself, cheers

Cal

You do realise that most of what I published today was bug-laden rubbish, don't you?

Post by **currymonster** » Mon Dec 01, 2014 10:00 pm

Au contraire! What I posted over the last hour was bug laden rubbish, caused by my bug laden brain! I have just instructed a family member to slap me about the face using a large herring!

Justice is done

Post by **kwchau** » Tue Dec 02, 2014 12:19 am

I have a different understanding of the nature of the RAD trade which should be a breakout trade. When I reviewed the RAD trades taken so far in the test, they were taken immediately when the RAD signals appeared.

Please ignore this if my understanding is incorrect.

Cheers !

Post by **trader689** » Tue Dec 02, 2014 1:57 am

can anyone tell why holy graily bob v1c on global prime took this audusd as a long trend trade? when its in a downtrend. please see attached picture, any advice appreciated thanks

Post by **rapple** » Tue Dec 02, 2014 2:21 am

trader689 » Tue Dec 02, 2014 11:57 am wrote:can anyone tell why holy graily bob v1c on global prime took this audusd as a long trend trade? when its in a downtrend. please see attached picture, any advice appreciated thanks

Have you updated the indicator (HGI V.14.02)

Cheers Richard

TheWolfInsideUs · Post by **TheWolfInsideUs** » Tue Dec 02, 2014 2:48 am

Have everything set on a VPS. Looking forward to test and contribute to the development of the EA and us as human beings.

Was not sure if this was already discussed/fixed. When loading the template and the EA it opened and closed two USDCAD buys within seconds. Sorry if this is already a known issue.

My sincere respect,

The Wolf

PS: I use from both the EA as the indicators the latest version.

Update: It opened and closed another USDCAD buy within seconds.

usdcad-h4-tradeslide-trading-tech.png

Post by **rapple** » Tue Dec 02, 2014 3:03 am

I also just got multiple 'Range Trade' buy-sells on Green Range Buy arrow on a number of pairs.

Is it because the wavy line is above?

Cheers Richard