Bob and Shelley Again

[SteveHopwood]

Here's another one...looks like BASA is taking the re-entry once price crosses above the MA (not necessarily a close)

We need an extra filter to ensure that Close[1] was on the correct side of the fast MA.

Added to V 1f in post 1.

Steve v1f produced 2 trades in the one candle overnight for me.
EURNZD - both re-entry trades, 1st trade taken BUY 1.68751 at 12:00 closed for BE+2, 2nd trade BUY 1.68738 taken at 14:56 still open

1st trade is correct, but not the 2nd trade

eurnzd.gh4_reentry trades_130806.png

Well, if a trade taken on one candle is closed on the same candle then the conditions are correct for a re-entry again because they were correct for the first trade. This means the bot will take a second trade. 4 hours is quite a long time so it is perfectly possible for this to happen.

An EA does what it is coded to do. You want it to do something different, you have to tell me to tell it what is different. EA's are not mind-readers. Nor am I.

[SteveHopwood]

I have some very sickly trades still open and heading rapidly towards SL - live trading but tiny lots and not much money involved.

I am going to leave this running live until the end of the week to see if it can make up some lost ground (and take the hit if not), then knock off for August and just run on demo.

I have an update coming tomorrow with some stacking ideas. I had intended adding Andy's ideas tonight as an option, but some now-deleted local difficulties distracted my attention. More tomorrow if I am in the mood, or Thurs if not.

Have fun.

[forex.rapheal]

Dear all,
Can we add an option to change the fixed TP and SL. Infact I love the idea from Bunker about "strench slope". Can we put them together?
http://www.stevehopwoodforex.com/phpBB3 ... f=44&t=716
Regards,

[fxozgirl]

Here's another one...looks like BASA is taking the re-entry once price crosses above the MA (not necessarily a close)

We need an extra filter to ensure that Close[1] was on the correct side of the fast MA.

Added to V 1f in post 1.

Steve v1f produced 2 trades in the one candle overnight for me.
EURNZD - both re-entry trades, 1st trade taken BUY 1.68751 at 12:00 closed for BE+2, 2nd trade BUY 1.68738 taken at 14:56 still open

1st trade is correct, but not the 2nd trade

eurnzd.gh4_reentry trades_130806.png

Well, if a trade taken on one candle is closed on the same candle then the conditions are correct for a re-entry again because they were correct for the first trade. This means the bot will take a second trade. 4 hours is quite a long time so it is perfectly possible for this to happen.

An EA does what it is coded to do. You want it to do something different, you have to tell me to tell it what is different. EA's are not mind-readers. Nor am I.

Ok, fair call
I thought I had specified that for re-entry trades, but looking back I hadn't...
So, can we have it so it only trades once per candle?
and there has to be a close above/below 60 lwma to validate the set up.

Main entry's all look to be good

[fxozgirl]

Dear all,
Can we add an option to change the fixed TP and SL. Infact I love the idea from Bunker about "strench slope". Can we put them together?
http://www.stevehopwoodforex.com/phpBB3 ... f=44&t=716
Regards,

I have just set up a 2nd demo using mptm to manage SL using 2 x ADR..this may prove to be more suitable than a fixed SL

[fxozgirl]

I have some very sickly trades still open and heading rapidly towards SL - live trading but tiny lots and not much money involved.

I am going to leave this running live until the end of the week to see if it can make up some lost ground (and take the hit if not), then knock off for August and just run on demo.

I have an update coming tomorrow with some stacking ideas. I had intended adding Andy's ideas tonight as an option, but some now-deleted local difficulties distracted my attention. More tomorrow if I am in the mood, or Thurs if not.

Have fun.

Looking forward to your stacking ideas Steve

Here's my current open trades...the account is down a bit, but most of that is caused by incorrect entries. The other thing I've noticed is that most of the trades that did hit SL were virtually at the peak of their drawdown and then reversed back into the direction of the trend...perhaps signifying the stop is too close.

For further testing and comparison I have set up a 2nd demo using 2 x ADR as the SL to see if this works better. I will do a bit more analysis of trades over the weekend.

basaopentrades_130807.png

[SteveHopwood]

V 1g is in post 1.

• added a filter that will stop BASA taking a second trade during the candle in which an earlier trade closed.
• added Andy's moving average stacking function - details in 'Moving Average stacking' in post 1.
• added trade stacking - details in 'Trade stacking.' in post 1

Trade stacking has huge potential - we all had a trade or two that moved a few hundred pips last week, so imagine we had taken extra trades as the market moved for us. How to initiate stack trades is going to be the big discussion point.

[OldTrader]

Ok, fair call
I thought I had specified that for re-entry trades, but looking back I hadn't...
So, can we have it so it only trades once per candle?
and there has to be a close above/below 60 lwma to validate the set up.

Main entry's all look to be good

So now there does need to be close above/below lwma for reentry?

[MrLong]

V 1g is in post 1.

• added a filter that will stop BASA taking a second trade during the candle in which an earlier trade closed.
• added Andy's moving average stacking function - details in 'Moving Average stacking' in post 1.
• added trade stacking - details in 'Trade stacking.' in post 1

Trade stacking has huge potential - we all had a trade or two that moved a few hundred pips last week, so imagine we had taken extra trades as the market moved for us. How to initiate stack trades is going to be the big discussion point.

Hi Steve,

The Ma's I actually use for the stack are the 21 EMA and 55 EMA:

Code: Select all

 if (useMaStack && (!detectMaStack(CurrentPair, PERIOD_H4, 21, 55, 0, MODE_EMA, PRICE_CLOSE, OP_BUY, 0)))

I also use the CSS H1 to try confirm the pullback is over and CSS H1 strength starts heading in my direction with:

Code: Select all

 extern double breakDifferenceThreshold    = 3.5;   // for the break slope .

  if (useCSSH1 && (!cssLongH1 > cssShortH1))
            continue;

 if (useCSSH1 && (!MathAbs(myDiff) > breakDifferenceThreshold))             // got to have broke out  and into my direction
        continue;

Hope this also helps

Andy

[SteveHopwood]

The Ma's I actually use for the stack are the 21 EMA and 55 EMA:

Code: Select all

 if (useMaStack && (!detectMaStack(CurrentPair, PERIOD_H4, 21, 55, 0, MODE_EMA, PRICE_CLOSE, OP_BUY, 0)))

I can add stacking moving average inputs as user choices. Why these particular ones?

I also use the CSS H1 to try confirm the pullback is over and CSS H1 strength starts heading in my direction with:

Code: Select all

 extern double breakDifferenceThreshold    = 3.5;   // for the break slope .

  if (useCSSH1 && (!cssLongH1 > cssShortH1))
            continue;

 if (useCSSH1 && (!MathAbs(myDiff) > breakDifferenceThreshold))             // got to have broke out  and into my direction
        continue;

Hope this also helps

Andy

The second bit does not unless I am right in this: you use Lib.CSS to find the values of cssLongH1 and cssShortH1? And that the two variables are those that you have defined elsewhere in your code?

Actually, now I read it after posting, the makes no sense. Nope, not a clue what you mean.