Holy Graily Bob 'n Grid

[PeterUK]

I just skipped f

Typo.

Ok, I corrected it myself....Damn, I'm goood

[Bruster400]

Continues to perform! I've had to manually close out my positions because work commitments and the upcoming uk bank holidays mean that I don't want to leave live positions unattended for 5 days. Even so, this is a great result from less than 8 trading days. Admittedly, GBPUSD has delivered the majority of this and when you look at the price action, straight up and then straight back down again can't get better for this trading but the other majors have delivered solid results.

Looking forward to firing it back up next week!

[SteveHopwood]

V 1h is in post 1. This has some essential safety code.

One way to avoid overtrading is to use one of the margin filters - I am using ForexKiwi at 800 but watch the default of 1500. There is a new input in the margin section - DeletePendingOrders.

This input tells HGBnG to delete pending trades when the margin level drops below your minimum, so long as there are not yet any market trades open. The rationale is that the margin level is already below our comfort level and so opening a new position is a bad idea.

There is a second safety feature. Newbies may not know that the platform can lie to you. When an ea sends a trade it appears immediately in your trade tab so you assume that it is an open trade. It is so in that the broker's server has accepted it, but the server has to return a receipt to the platform before it becomes 'visible' to an EA.

This receipt can take time arriving and can lead to an ea being unaware that it has just sent a trade, This sequence of event can and does occur:

• There is a trade trigger.
• The ea yells, "Woooohoooo, party time" and sends a trade.
• Next tick, the trade trigger is still in place. The ea examines the list of trades it can 'see'. If the receipt has arrived, it will see there is already a trade open and not send another.
• If the receipt is delayed, the ea cannot 'see' one, yells, "Woooohoooo, party time" and sends a trade.
• This can happen hundreds of times within seconds. Next time you look at your platform, spread, commission and the teensiest move in the wrong direction have blown your account through a margin call.

Matt Kennel's LibOrderReliable code overcame this for years. The Cretins at Crapperquotes broke it recently - PostTradeAttemptWaitSeconds is designed to overcome this.

Should this fail for any reason, we can end up with grids of hundreds of pending orders within a very short distance of one another. I have added a function to combat this. Should HGBnG discover more than GridSize x 4 pending trades (20 by default) he will assume that something has gone wrong and:

• Take a snapshot of the types of grids open and in what order.
• Delete all the pending orders.
• Replace the deleted grids.

I have not tested all possible combos and with any luck this feature will not be needed. We shall see.

----------------------------------------------------------------------------------

I am putting a stop to two discussion points here, and will delete posts about them:

• Persuading HGBnG to mop up after users have manually deleted market orders. HGBnG is an auto-trader. You want to interfere manually great, but use some brains, consider that there might be unexpected consequences if he is running on the chart, and remove him first.
• Maximum trades allowed by brokers. I don't care. Your broker does not allow you to trade as you wish? Change brokers.

[PeterUK]

Thanks Steve,

Understood, lets go party with v1g onwards

----------------------------------------------------------------------------------

I am putting a stop to two discussion points here, and will delete posts about them:

• Persuading HGBnG to mop up after users have manually deleted market orders. HGBnG is an auto-trader. You want to interfere manually great, but use some brains, consider that there might be unexpected consequences if he is running on the chart, and remove him first.
• Maximum trades allowed by brokers. I don't care. Your broker does not allow you to trade as you wish? Change brokers.

[patmontes]

2 GBPUSD sells had hit TP and I'm not going to interfere manually and see what happens with the open trades since I know we have the tools already to combat most situations
Last week if I did not close the open trades in profit manually, the returns would have been bigger.

.....waiting game for that yellow wavy to close my trades now...

[Peepaws]

Thank you again Steve for all your work and for sharing you're amazing creations with all of us!

I will be running 3 demos: one with normal HGBnG, one with Tnavi's MA, and one with Bobs MA. All basically OOTB, running on the majors and GJ.

This is in preparation to go live and the winner of the 3(or maybe another winner discovered by someone else on the forum) will be going live in a month or so!

Together with all of the other contributors you really have taken the Holy Grail and automated it!


:hi: :hi: :hi: :hi: :hi: :hi: :hi:

I will report weekly on the status of each demo...

[cyberevil]

Check this out, So as most of you know I was running 3 demos on three different systems/locations. All three of them were in a DD situation some in big DD.

All three of them came out of DD successfully! Two of them I manually closed at $50+ profit but this last one I left it to see how high it can go. I'll let this picture do the explaining to you all. This one I left it alone to what it would do...

Untitled.png

[PeterUK]

Hi Cyber,

Nice trading results, would you mind I ask which settings you used? or possibly a setfile may suffice?

Many thanks,

Peter

[cyberevil]

Here you go, I don't think I messed too much with the original set. I'm running it on 2n as you see. I really wanted to test this version fully to my satisfaction. I'm pretty happy with it as of now. Next I'll be upgrading my home demo with GP to the latest version to test it.

set file is attached for those interested but like I said I didn't mess too much with it.

cy.txt

[PeterUK]

Thanks Cyber, much appreciated, using KDiff3 I see what you've done

Here you go, I don't think I messed too much with the original set. I'm running it on 2n as you see. I really wanted to test this version fully to my satisfaction. I'm pretty happy with it as of now. Next I'll be upgrading my home demo with GP to the latest version to test it.

set file is attached for those interested but like I said I didn't mess too much with it.