Holy Graily Bob 'n Dotty 'n SuperSlope

[nwannao]

Hello Steve,

Just noticed that the Baluda.SuperSlope.v.2.0 for EA is showing red for the highest time frame (i.e M1) while the EA is says green.

I tried running the normal Baluda. SuperSlope.v.2.0 and the colors tally.

Though I think the one you posted for the EA seems more accurate, I am not sure if it is a problem as the EA reads a diff color.

[SteveHopwood]

Hello Steve,

Just noticed that the Baluda.SuperSlope.v.2.0 for EA is showing red for the highest time frame (i.e M1) while the EA is says green.

I tried running the normal Baluda. SuperSlope.v.2.0 and the colors tally.

Though I think the one you posted for the EA seems more accurate, I am not sure if it is a problem as the EA reads a diff color.

Forget the version for EA. I removed all the externs so an EA could call it before Thomas subsumed the SS code into the EA code.

So far as the EA is concerned, what the indi shows on the chart is irrelevant. The EA makes its own calculations and displays colours according to them. This will be either red or blue as it takes no notice of ranging periods displayed as white in TJF's original template, which is the one I am using. Note my comment about ranging periods in post 1.

I repeat for the benefit of anybody not taking any notice of anything I write under any circumstances as usual, indi code baffles me. I do not understand it. I have no idea how SS works. What we have in the EA is Thomas' work in bringing the indi code 'in house'.

The indi and the EA are displaying different colours? Sod all I can do about it. The EA works with the information shown in its chart feedback display and could not give a stuff what the indi says.

[nwannao]

Forget the version for EA. I removed all the externs so an EA could call it before Thomas subsumed the SS code into the EA code.

So far as the EA is concerned, what the indi shows on the chart is irrelevant. The EA makes its own calculations and displays colours according to them. This will be either red or blue as it takes no notice of ranging periods displayed as white in TJF's original template, which is the one I am using. Note my comment about ranging periods in post 1.

I repeat for the benefit of anybody not taking any notice of anything I write under any circumstances as usual, indi code baffles me. I do not understand it. I have no idea how SS works. What we have in the EA is Thomas' work in bringing the indi code 'in house'.

The indi and the EA are displaying different colours? Sod all I can do about it. The EA works with the information shown in its chart feedback display and could not give a stuff what the indi says.

Nice one Steve. Thanks for the clarification. Well understood.

[SteveHopwood]

Latest version is in post 1. There is no need to download it if you already have the existing working version.

Explanation at http://www.stevehopwoodforex.com/phpBB3 ... 50#p152650

[dclayw]

Been away for a few months, just catching up on all the threads. There's an awful lot going on.

I'm interested in this EA as for a few months early last year I manually forward tested HGI using HTF original CSS as trend guide. Results looked promising but it's hard work testing that way. This EA should help a lot, particularly now that SS is here.

So I'm hoping this EA maintains some interest. Also keeping tabs on the Flying Buddha version. Looking more at H4 and D1 these days and likely concentrating just on SS. Just setting up VPS and will come back once I have anything useful to add.

[SteveHopwood]

Been away for a few months, just catching up on all the threads. There's an awful lot going on.

There sure is, and all of it exciting. Welcome back.

I have had the latest batch of the DB family running ootb because I am the coder and so tend to release bots the way I would trade them.

I am finding that: DD consistently outstrips banked profits; pairs move into a massively hedged position that does not clear within a timescale that we would regard as reasonable were we trading live.

This could be because my trading methodology is bollocks and that more imaginative traders are finding settings that suit them. I am favouring http://www.stevehopwoodforex.com/phpBB3 ... =87&t=5101 because it is an automation of http://www.stevehopwoodforex.com/phpBB3 ... 101&t=5098. It is not a basket/hedging method and so does not build up the massively complicated positions that the rest of the DB family build.

Also, as you have not been around for a while, make sure you visit http://www.stevehopwoodforex.com/phpBB3 ... =59&t=4795. It ain't free. It ain't cheap. It is awesome.

[dclayw]

Thanks for the welcome back Steve.

I have seen some of those impressive results over at the Flying Buddha thread, comes up with some nice ideas does TJF. I've never grid traded so that style of trading in the FB thread would suit me more.

I did play around a little bit with gridding, hedging and offsetting in HGBnDnSS and it can get fairly complicated. I was running on H1 with 20+ pairs to generate a lot of trades, just so I could see how it worked. Pretty easy to lose track. I came across some situations where trades were being closed for no apparent reason. I saw that kind of behaviour in various threads (might have been whole baskets closing) and I'm not sure if that had been fully resolved yet.

Anyway, think I'll stick with standard bracket type trading for now, maybe with a few unhedged grids thrown in.

[SteveHopwood]

The latest version of the core library is in post 1 of the shell thread at http://www.stevehopwoodforex.com/phpBB3 ... =87&t=5077.

The latest version of this EA is available in post 1.

All these updates do is tidy up the bloops I introduced by adding a new input to HGBnDnSSnFB and the way the inputs are displayed to the user. You do not need them if you are happy with what you already have.

I have also updated the user guide attached to post 1 in the http://www.stevehopwoodforex.com/phpBB3 ... 39#p145239 thread.

[dclayw]

Ok, I have my VPS set up and have started doing a little bit of testing. Using the KISS approach, pretty much along the lines of Bob's "simplest trading system ever", resisting the urge to add bits and pieces to it, just tweaking the SS settings here and there.

I've had this EA running on 20 pairs (+ XAUUSD) for about 4 days on H1 trading TF, no grid, no offsetting, no HGI or Sixths or anything like that, no TP or stops. Just Immediate Market orders and CloseTradesOnColourChange. I'm not even using HTF control just yet. I just want to get a feel for how the EA works. With this setup the EA will just take a trade on the H1 SS colour change and exit that trade when the colour changes back again, it will also enter a trade in the opposite direction at that point so it's a stop and reverse type setup, always in the market.

Surprisingly, after 4 days, if I take out XAUSD and GBPNZD (which has always been the worst pair for me) it's sitting at about breakeven. One more thing, my SS settings are 14,50. I came up with that just eyeballing charts and trying different settings. It gets in a little bit later, one bar usually, but that tends to not make much difference in the whole scheme of things. It does tend to get rid of some of the chop though.

I would likely never trade what I have above, it would be nice if I could. As I said, initially I'm just getting a feel for how the EA works. I want to run this for about a month just to collect some decent data. I'll close all trades on Friday evenings (I'm in Australia). I'll then load that data up into myfxbook and see if I can come up with optimised stop/TP for each pair by analysing MFE/MAE. Then run the EA for a few weeks more with these optimised stop/TPs and see if it can make any pips.

Because of the differences in volatility of each pair it would be best to relate the optimised stop/TPs as a measure of volatility, (ATR). That way there is no need to have different pip stop and TP for each pair (which would require a different preset for each pair). The current EA allows for basket TP as a measure of volatility, it would be nice if all stops (including BE and Trailing) and TP settings could all be input in terms of ATR. I know there would be a bit of coding to do to get that to happen. Actually, I think the basket ATR TP works even if you're not grid trading, but it doesn't look like there are any ATR stops in the EA.

There are many variations to the above but I want to keep it real simple at the start and then hopefully build on that without adding too many bells and whistles, hopefully no bells and whistles. A pipe dream you think......

I'll report back here periodically but there might not be a great deal of activity. I'm just hoping this thread and EA stay alive because I reckon this is one of the best ideas Bob has had, and he's had some good ones.

Much thanks to you Steve, and Tomele and the rest of the crew who have put this family of EAs together. I actually coded an auto trade system 10+ years ago using Amibroker, so I know how much work goes into it, and it's all freely available. My auto system never really got off the ground, because platforms were pretty archaic back then, but mainly because my coding sucked big time.

[dclayw]

Not sure if anyone would be interested in this but when I was playing around with grid trading in the EA I was thinking about what value I should use for TpPercentOfAtrToUse for the basket TP. I had a good idea of what I should use as the TP if I was just taking single trades, but what should that be if I was trading a grid?

Lets say you were taking single trades and had a TP of say 100 pips. If you wanted to grid trade that for extra profits then you could express that 100 pips as a % of ATR. Let's say that came out to 1.5 ATR, (GridAtrMultiplier would be 1.5). So what should TpPercentOfAtrToUse be set to for a GridSize of X (X = number of pendings for the grid). It's pretty easy to calculate this manually but here's a quick way:

If you're also using Immediate Market Orders (a trade right at the very base of the grid) then:

TpPercentOfAtrToUse = (X+1) * Y/2 where:

X = GridSize (number of pendings for the grid)
Y = GridAtrMultiplier

So if your grid was 100 pips = 1.5ATR, and you wanted 4 pendings, then TpPercentOfAtrToUse = (4+1) * 1.5/2 = 3.75

If you're NOT using Immediate Market Orders (no trade at the base of the grid) then:

TpPercentOfAtrToUse = (X-1) * Y/2 = 2.25 using example values above.

Anyway test it out to see if it works for you. Pretty sure the math is right, let me know otherwise.