Nanningbob 10.2 auto-trading EA

[cuzgeorge]

Here you have it. I changed all the places using Point to use factor instead. Will see in the coming week how it goes.

I also fixed the function LookForD1TrendTrade to check if it is okay to stack trades if a trade already exists just like it is done in LookForD1H4TrendTrade. I added this...



Will see if I get some BB trades in the coming week. Looking forward to see how the BB trades perform.

Kind Regards,

Alex

Nice Alex, and welcome to the Steves spot on the web.

I have also not had any BB positions from my versions here. I have had good progress with this EA including Jemook's uber version this past week.
I've set up the newer version from Steve using Shelley, Bob and Jemook's ideas and looking forward to their new one on Monday.

I welcomed Steves 2b version and was shocked that none of us had picked up the '.04' error in the code from previous versions. I attempted, but failed, to find the BB problem you mentioned and and it all makes sense when i read your post. This problem was mentioned before but it does'nt appear to have been addressed yet. Will wait to see what Steve does with the info. Please keep us posted with the new week on the progress of your factor and point issue.

My progress has been very good on this EA, i am running them concurrently with Bobs 5.1, 5.3 and 5.5 EA's and noticing that i prefer Steves 2b version more.
The 5's have much higher DD but most of the time they do close in profit. the swing is just freaking me out and i have closed many charts (oroginally 26 pairs on Steve's EA) to avoid ridiculous and unrealistic DD. The idea is to test for real account usage and i doubt i will ever deposit 100k in my real account. i wish i could.
i'm using 6 charts on main pairs for the 5's and 11 charts for 2b, all on main pairs and not the minor crosses. 1 each for silver and gold, and 6 for US stocks like facebook and intel etc etc.
all doing well.
Still messing around with the settings though as they do vary and cause a clash with MPTM for hedging, although i try to avoid hedging as much as possible. it really complicates everything for me and its hard to keep track of whats going on. too early to send stats and figures as its best to close all positions before assuming a winner in the EA.
hope this info helps and thanks again for valuable insight ,
regards
cuz

[al3xx]

Good job Alex

please, share mq4 file, so we can do backtest to verify if BB trade is ok

Yes, thanks Alex. That is great bloop-spotting.

If you could upload the mq4 it will save me making the edits manually.

Thanks Steve. Here it is.

On that first attachment, I put the wrong extension when saving. It is actually the .mq4 with the readable code and you could just change the extension. This time everything is good though. My apologies for that mixup.

I made some other changes as below.

Still on the BB trades, this doesn't look right...

Code: Select all

//Look for a range trade if the ltf trend is ranging i.e. < 0.4 and > -0.4.
         if (LtfTrend == ranging)
         {
            if (UseBollingerBands) LookForBbRangeTrade(OP_BUY);
         }//if (LtfTrend == ranging)

LtfTrend is never set to ranging at any point. The same applies when looking to sell. I changed it to check with LtfSlopeTrend that will be set when reading ind values like so.

Code: Select all

//Look for a range trade if the ltf trend is ranging i.e. < 0.4 and > -0.4.
         if (LtfSlopeTrend == ranging)
         {
            if (UseBollingerBands) LookForBbRangeTrade(OP_BUY);
         }//if (LtfSlopeTrend == ranging)

I have added a feature I need that verifies a cross over. What this does is to avoid situations when you load the EA on the chart and it picks a cross that happened 50 or more pips ago as a valid entry. I don't want this... I want to catch the cross at the moment it happens. So we check the distance between price and the crossed line and if it is more than a set number of pips it is not valid.

The extern you need to set is MaxPipsCrossed. I have it set to 10. Set to zero to disable this check.

EDIT:

I forgot to mention that I got a different weekly open histogram 2x1 ind back at FF forums in Nanningbob's thread for this system. It is called "10.2 WOH 2x1 5.22" and is different from the "10.2 WeeklyOpenHistogram 2x1 4.29" used in the original Steve's EA. If you download and load this EA you may get error messages in your logs that it couldn't find 10.2 WOH 2x1 5.22 indicator.

You just need to get this version of the WOH and you will be ok. Alternatively, change "10.2 WOH 2x1 5.22" to "10.2 WeeklyOpenHistogram 2x1 4.29" (that is in the original I think) and recompile the EA. I am attaching the 10.2 WOH 2x1 5.22 here too.

Alex

[SteveHopwood]

EDIT:

I forgot to mention that I got a different weekly open histogram 2x1 ind back at FF forums in Nanningbob's thread for this system. It is called "10.2 WOH 2x1 5.22" and is different from the "10.2 WeeklyOpenHistogram 2x1 4.29" used in the original Steve's EA. If you download and load this EA you may get error messages in your logs that it couldn't find 10.2 WOH 2x1 5.22 indicator.

You just need to get this version of the WOH and you will be ok. Alternatively, change "10.2 WOH 2x1 5.22" to "10.2 WeeklyOpenHistogram 2x1 4.29" (that is in the original I think) and recompile the EA. I am attaching the 10.2 WOH 2x1 5.22 here too.

Alex

Thanks Alex. In that case I will have to make the alterations manually as I do not use the Woh indi's; the code that calculates the returns from Woh is in-house and I do not want time-consuming calls to custom indis when these can be avoided.

[al3xx]

Thanks Alex. In that case I will have to make the alterations manually as I do not use the Woh indi's; the code that calculates the returns from Woh is in-house and I do not want time-consuming calls to custom indis when these can be avoided.

Hi Steve, unless I am mistaken, I thought the call was already there. I was reffering to the function GetWoh that calls the custom WOH ind. I just changed the name of the ind.

[phil_trade]

Steve

I made a control with different historical data with your D1 Slope calculate module embedded in EA :

ex. of calculation D1 slope for AUDUSD at the same point :

with 1 month history : D1 slope = 0.653
with 2 months history : D1 slope = 0.503
with 3 months history : D1 slope = 0.470
with 12 months history : D1 slope = 0.470

So, I suggest to add a control in all EA with iBars for each Symbol like
if iBars( symbol(), 1440 ) < 100 then bla bla
if iBars( symbol(), 240 ) < 100 then bla bla
etc

Phil

[SteveHopwood]

Thanks Alex. In that case I will have to make the alterations manually as I do not use the Woh indi's; the code that calculates the returns from Woh is in-house and I do not want time-consuming calls to custom indis when these can be avoided.

Hi Steve, unless I am mistaken, I thought the call was already there. I was reffering to the function GetWoh that calls the custom WOH ind. I just changed the name of the ind.

doh. Yup. My signature says it all.

So, version 2c is in post 1. The only difference between this and the version Alex was kind enough to post is that I changed the name of the Woh back to the one that everyone else is using, to avoid confusion. Alex knows enough to make the change back for himself if I post a later update.

This is a brilliant contribution, Alex, and I am most grateful. Thanks.

[SteveHopwood]

Steve

I made a control with different historical data with your D1 Slope calculate module embedded in EA :

ex. of calculation D1 slope for AUDUSD at the same point :

with 1 month history : D1 slope = 0.653
with 2 months history : D1 slope = 0.503
with 3 months history : D1 slope = 0.470
with 12 months history : D1 slope = 0.470

So, I suggest to add a control in all EA with iBars for each Symbol like
if iBars( symbol(), 1440 ) < 100 then bla bla
if iBars( symbol(), 240 ) < 100 then bla bla
etc

Phil

This caused me to do a rapid update to 2c. I have added iBars(NULL, PERIOD_D1); to init(). Does this do the job?

[phil_trade]

Steve

I made a control with different historical data with your D1 Slope calculate module embedded in EA :

ex. of calculation D1 slope for AUDUSD at the same point :

with 1 month history : D1 slope = 0.653
with 2 months history : D1 slope = 0.503
with 3 months history : D1 slope = 0.470
with 12 months history : D1 slope = 0.470

So, I suggest to add a control in all EA with iBars for each Symbol like
if iBars( symbol(), 1440 ) < 100 then bla bla
if iBars( symbol(), 240 ) < 100 then bla bla
etc

Phil

This caused me to do a rapid update to 2c. I have added iBars(NULL, PERIOD_D1); to init(). Does this do the job?

I dont' think so.
I don't believe that iBars force Empty4 to load anything but only return the number of bar in the chart.
Better to inform user that there is not enough bar in your DisplayUserFeedBack() with test like
if iBars( symbol(), 1440 ) < 100 then NotEnoughDay = true
if iBars( symbol(), 240 ) < 100 then NotEnoughH4 = true

[SteveHopwood]

I dont' think so.
I don't believe that iBars force Empty4 to load anything but only return the number of bar in the chart.
Better to inform user that there is not enough bar in your DisplayUserFeedBack() with test like
if iBars( symbol(), 1440 ) < 100 then NotEnoughDay = true
if iBars( symbol(), 240 ) < 100 then NotEnoughH4 = true

Thanks Phil. I do not remember where I got the idea that the code would work - somewhere here but no idea where.

No probs about adding the filter, but do you happen to have any idea how to force a download of the history? I assume not, or you would have posted it, but no harm in asking.

Cheers

[phil_trade]

I dont' think so.
I don't believe that iBars force Empty4 to load anything but only return the number of bar in the chart.
Better to inform user that there is not enough bar in your DisplayUserFeedBack() with test like
if iBars( symbol(), 1440 ) < 100 then NotEnoughDay = true
if iBars( symbol(), 240 ) < 100 then NotEnoughH4 = true

Thanks Phil. I do not remember where I got the idea that the code would work - somewhere here but no idea where.

No probs about adding the filter, but do you happen to have any idea how to force a download of the history? I assume not, or you would have posted it, but no harm in asking.

Cheers

No code to force but my finger to push down the left arrow to force each graph to download
I also import M1 data from FT to Empty4 and run convert script to generate all TFs