Slopey Slope

[hilavoku]

Hi Zyp,

can you give me the info about one or two of the taken sell trades? Did you delete the .ex4 file or recompiled the indi?!

thx
Guido

PS: I added the EA to AUDCAD and it immediately trys to take a BUY order. Which fails with error 130...


2012.08.20 21:52:03 Slopey Slope_repaired AUDCAD,H1: Alert: AUDCAD Slopey Slope_repaired OP_BUY order send failed with error(130): invalid stops


(A backtest shows that the EA takes long and short positions.)

sincerely
Guido

[SteveHopwood]

Thanks for the feedback Zyp. I just changed some lines in the 'ReadIndicatorValues' function. Even when Steve's version seems to work at the moment it calculates the wrong values as i stated above. This doesn't also mean that my version is 100% right :-|

Just so you know, Guido, the values calculated are those of the 10.2 TMA slope v.1.4B 4.30 indi and are correct on my charts.

The EA is doing as I want it to, for now. What I want it to do may change.

[hilavoku]

Thanks for the feedback Zyp. I just changed some lines in the 'ReadIndicatorValues' function. Even when Steve's version seems to work at the moment it calculates the wrong values as i stated above. This doesn't also mean that my version is 100% right :-|

Just so you know, Guido, the values calculated are those of the 10.2 TMA slope v.1.4B 4.30 indi and are correct on my charts.

The EA is doing as I want it to, for now. What I want it to do may change.

Hope the best

The TMA value calculation itself is correct thats for shure but the time the values are updated isn't. As i stated above, the lower timeframe previous tma value is only updated every higher timeframe...

Code: Select all

if (OldBarTime != iTime(NULL, HtfTimeFrame, 0) )
      {
         PrevLtfSlopeVal = GetSlope(Symbol(), LtfTimeFrame, 2);
      }//if (OldBarTime != iTime(NULL, HtfTimeFrame, 0)

That is not correct 'PrevLtfSlopeVal' should updated every 'LtfTimeFrame'. When the 'LtfSlopeVal' changes then also 'PrevLtfSlopeAngle' must change like i posted here: http://www.stevehopwoodforex.com/phpBB3 ... 5&start=26

Would be nice if someone else can look at the function 'ReadIndicatorValues' and give his thoughts to us. I also spent a lot of time into this before i post something where i say that a calculation is wrong. Especially when its from you Steve!


see you
Guido

[Zypip]

Hi Zyp,

can you give me the info about one or two of the taken sell trades? Did you delete the .ex4 file or recompiled the indi?!

thx
Guido

PS: I added the EA to AUDCAD and it immediately trys to take a BUY order. Which fails with error 130...


2012.08.20 21:52:03 Slopey Slope_repaired AUDCAD,H1: Alert: AUDCAD Slopey Slope_repaired OP_BUY order send failed with error(130): invalid stops


(A backtest shows that the EA takes long and short positions.)

sincerely
Guido

Hi Guido,

Sorry for being bother. Did not recompile the EA as I thought Empty4 should do that when the restart during initialisation, which I did. I thought it was not an issue at my end on the basis that Steve's version was opening correctly short/long trades according to whether the H4 slope was rising or decreasing. Also, I did not upgrade yet to the 432 build but will do soon.

At the mo I have the slopeyslope EA running on about 18 pairs and Baluda's basket management EA running on another pair so that I would take profit whenever the total profit reaches X pips.

Anyway, I does seem to take longs and shorts on your machine so it is probably something I have to sort out at my end.

Cheers,

Zyp

[hilavoku]

Thx for the info Zyp.

Hope the EA serves you well and will take some longs for you. Read my thoughts about a threshold. I think it would be an usefull addition.

sunny greetings from germany
Guido

[SteveHopwood]

Thanks for the feedback Zyp. I just changed some lines in the 'ReadIndicatorValues' function. Even when Steve's version seems to work at the moment it calculates the wrong values as i stated above. This doesn't also mean that my version is 100% right :-|

Just so you know, Guido, the values calculated are those of the 10.2 TMA slope v.1.4B 4.30 indi and are correct on my charts.

The EA is doing as I want it to, for now. What I want it to do may change.

Hope the best

The TMA value calculation itself is correct thats for shure but the time the values are updated isn't. As i stated above, the lower timeframe previous tma value is only updated every higher timeframe...

Code: Select all

if (OldBarTime != iTime(NULL, HtfTimeFrame, 0) )
      {
         PrevLtfSlopeVal = GetSlope(Symbol(), LtfTimeFrame, 2);
      }//if (OldBarTime != iTime(NULL, HtfTimeFrame, 0)

That is not correct 'PrevLtfSlopeVal' should updated every 'LtfTimeFrame'. When the 'LtfSlopeVal' changes then also 'PrevLtfSlopeAngle' must change like i posted here: http://www.stevehopwoodforex.com/phpBB3 ... 5&start=26

Would be nice if someone else can look at the function 'ReadIndicatorValues' and give his thoughts to us. I also spent a lot of time into this before i post something where i say that a calculation is wrong. Especially when its from you Steve!


see you
Guido

Thanks again, Guido. I misunderstood what you were saying. I had not noticed the lower time frame problem because I have not used the ltf yet.

Version 1b is in post 1, with the time thingy corrected. I noticed a couple of other oddities whilst doing this, and fixed those as well.

[hilavoku]

Hi Steve,

good to hear that i'am not nuts and my brain is still functional although it's very hot here in germany...

[SteveHopwood]

Version 1c is in post one, in preparation for next week.

I am finding that SS will open trades that become profitable when they are taken after a turnaround. Eventually, there is a further turnaround and the profit disappears.

I want to use mptm to close the whole position a la basket trading, at x% profit, so I have to tell SS not to immediately enter fresh trades.

So, as an example of what I have done, imagine SS detects a rising angle that might trigger a buy, so:

• - the angle at the close of the previous candle must be > that of 2 candles ago.
  - I have added the condition that the angle of 3 candles ago must be > that of two candles ago, indiating that the angle first fell, then rose again. If not, the chart feedback will show the angle as, "Rising, but not tradable."

[glabbeek]

Hi Steve,

How do you plan to filter out ranging markets? I would expect that your last addition to the EA might cause a lot of whipsaws.

[SteveHopwood]

Hi Steve,

How do you plan to filter out ranging markets? I would expect that your last addition to the EA might cause a lot of whipsaws.

How?