002097's PwR scalping auto trading robot by Steve Hopwood | Page 9 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

Trying scalping with a 1000 bucks - Scalping is expensive! 39 replies

1M & 5M Scalping System (Scalping Paradise) 21 replies

Random Auto Scalping to Profits 36 replies

PwR EVA 16 replies

MoForce's PwR System 25 replies

Attachments: 002097's PwR scalping auto trading robot by Steve Hopwood
Exit Attachments

002097's PwR scalping auto trading robot by Steve Hopwood

  • #161
  • Sep 7, 2011 5:26am Sep 7, 2011 5:26am
Quoting SteveHopwood
Guys, re some recent questions to me: which bit of 'ootb' is causing some of you problems? None of the words are two syllables long, or have more than three letters in them. Google their meaning if unsure of the individual words.

Touche!
Kinda surprised you don't use those filters...
I don't say
  • #162
  • Edited 7:04am Sep 7, 2011 6:01am | Edited 7:04am
Quoting SteveHopwood
Latest update in post 1.

This one is for the analysts and does nothing with the information:

 

  1. Added code to calculate the mean average pips movement over x candles. The input is LookBackForAverageCandles; the default equates to one day of M5 candles.
  2. Added code to display the next upper/lower round numbers.

So guys, start thinking about what to do with the information, whilst I think about the trailing stop and breakeven stuff.

Running total: EU, 5 mins, ootb except for ecn stuff, 24 hours except when my computer...


Hi Steve,
Thank you for coding this EA i am following this method for some time. I was wondering can we start providing some form of organized stats which settings are the best ?

Can you tell if default settings are the ones which allowed you to produce such great outcomes or you choose one of the extra options ?

Maybe we could create excel sheet and put all the variants there ? ...
  • #163
  • Sep 7, 2011 6:06am Sep 7, 2011 6:06am
Quoting dragosd1
Touche!
Kinda surprised you don't use those filters...
I included them before I looked under the bonnet of PwR.

Like all custom indi's PwR works by sending calls to established indi's and manipulating/using the returned data in different ways.

PwR uses Bulls Power and Bears Power. BullsPower calculates an EMA of x periods of the High of each candle and subtracts this from the current High. If this calculation results in a positive number, then the market is rising above the ema. Bulls Power works in reverse on the Close of each candle.

PwR uses 144 as the period against the regular indi's 13. Then it compares the value of Bulls with that of Bears and comes up with a trading direction based on this comparison.

As we have seen so far, this is pretty powerful; whether the D1 pivot and H4 open price make any difference is something to investigate once we have all the other details in place.

Latest update in post 1 guys:

 

  1. added John's tp as a multiple of the sl; input in the Take Profit section. In backtesting EU to make sure the code is correct, an input of 150 makes no difference, but doubling to 200 sure does. No idea if this is significant. Coders might like to check that the code is correct: for a buy take = NormalizeDouble(price + ( (ConvertedCandleRange * (TpPercentageOfSL / 100)) * Point), Digits);
  2. Added code that will enforce CriminalIsECN when the platform is IBFX. This will need removing when IBFX decide no longer to be ECN, for the benefit of their 'valued clients'. Hehe. As soon as I can afford it, I will not be one of these.

If you neither want or need these features, then you do not need the update.

  • #164
  • Sep 7, 2011 6:16am Sep 7, 2011 6:16am
Opened up Aurora at 0400 GMT. EJ, UJ. and GU got eaten alive in areas of congestion and round numbers (actually S&R)

EU actually broke even at 2 and 2 somehow. Needs solid moves and trends, doesn't she, but that's predictable.

Still, it's a good EA. Most of us couldn't have manually scalped with much profit during this Euro a.m.


Shake
  • #165
  • Sep 7, 2011 6:23am Sep 7, 2011 6:23am
Steve

the reason why the calculation does not work for 150 is because you have TPPercenatgeOfSL as a Integer

it needs to be a double.. (when the result field of an operation is not implicitly specified, it uses the first variable as the definition for the result)

for all using this version just change

extern int TPPercentageOfSL=100;

to

extern double TPPercentageOfSL=100;

Regards, John

Quoting SteveHopwood
Latest update in post 1 guys:

 

  1. added John's tp as a multiple of the sl; input in the Take Profit section. In backtesting EU to make sure the code is correct, an input of 150 makes no difference, but doubling to 200 sure does. No idea if this is significant. Coders might like to check that the code is correct: for a buy take = NormalizeDouble(price + ( (ConvertedCandleRange * (TpPercentageOfSL / 100)) * Point), Digits);


  • #166
  • Sep 7, 2011 6:25am Sep 7, 2011 6:25am
Great work Steve! Currently testing with different TP % of SL combined with breakeven and trailing stop
  • #167
  • Sep 7, 2011 7:06am Sep 7, 2011 7:06am
I am suspecting a bug in EAs. Pwr shows down all good to go but EA says trend is up. Should be already down and trade should be taken ?

Can you explain ?
Attached Image (click to enlarge)
Click to Enlarge Name: Picture 6.png Size: 67 KB
  • #168
  • Edited 8:40am Sep 7, 2011 7:34am | Edited 8:40am
Thanks to Steve and 0002097 and all the other contributors for sharing this.

I have downloaded the latest copy of Aurora and am busy backtesting with tester.

I notice that Aurora takes the closing candle of a trade as the setup for a new trade if signal is valid, setting up a trade on the open of the candle immediately following the closing candle of the previous trade. The way I understand the rules this is incorrect as explained in the second graphic screendump in post #1 of the original thread.

I do not know the significance of this but thought I would mention it here!

Added:

Also, on tester A takes a trade where the expiry candle (the third one) of a failed pending order is used as the signal. This also seems in contradiction of the rules. From post #93 in the original thread, 0002097 responded: "I do wait for 3 candles after the signal candle, if it doesn't get hit I cancel my order and wait for another signal, but I don't take more signals in the waiting period."

Please consider if relevant!
Success is a marathon, not a sprint!
  • #169
  • Sep 7, 2011 7:43am Sep 7, 2011 7:43am
Quoting jmw1970
Steve

the reason why the calculation does not work for 150 is because you have TPPercenatgeOfSL as a Integer

it needs to be a double.. (when the result field of an operation is not implicitly specified, it uses the first variable as the definition for the result)

for all using this version just change

extern int TPPercentageOfSL=100;

to

extern double TPPercentageOfSL=100;

Regards, John
And I bracketed the calculation wrongly to allow accommodation for this. Different brackets would have worked.

Cheers.

Also guys, there is a problem with the ECN stuff. If A sends a market trade to an ECN crim, but the stop loss/tp is too close to the market, the trade is sent but the stops not modified.

I have to go out now, and will sort all this out later.

  • #170
  • Sep 7, 2011 11:03am Sep 7, 2011 11:03am
Latest update in post 1.

 

  1. sorted out the ECN thingy. Possibly.
  2. I realised the bot needs more stop loss and tp calculation to avoid some of the 'invalid stop' errors, so I fixed this. Possibly.
  3. Added a round number filter - might have bugs. Details in post 1.


Running total: EU, M15, ootb
Winners: 23
Losers: 8

  • #171
  • Sep 7, 2011 11:22am Sep 7, 2011 11:22am
Steve can you kindly check to see if you received the PM I sent you this morning?!
Thanks in advance
  • #172
  • Sep 7, 2011 12:47pm Sep 7, 2011 12:47pm
Thanks for the developments, Steve. I just spotted the 15 min. !

Old age is interesting.

Glenn
  • #173
  • Sep 7, 2011 1:06pm Sep 7, 2011 1:06pm
I just wondered if it was a worthwhile excercise to prevent the EA from taking trades around the release of scheduled Red Flag news announcements ? - Has anyone any thoughts on this

Also it seems that we can get chopped up pretty badly in days when there is just whipswap action in the markets - would it be worthwhile considering preventing trades until there was some semblance of a trend in the next higher timescale ?
  • #174
  • Sep 7, 2011 1:08pm Sep 7, 2011 1:08pm
hi steve,

really good results, impressive!

but why do you use this EA on m15, originally the rules were for m5 i think?!


greets

wurst
  • #175
  • Sep 7, 2011 1:51pm Sep 7, 2011 1:51pm
Isn't it a typo in post #170 ? Instead of M15 - M5 ?
  • #176
  • Sep 7, 2011 1:57pm Sep 7, 2011 1:57pm
That was what I assumed as well!

Quoting DerBerliner
Isn't it a typo in post #170 ? Instead of M15 - M5 ?
Success is a marathon, not a sprint!
  • #177
  • Sep 7, 2011 2:17pm Sep 7, 2011 2:17pm
Not so sure if this is a bug, but this trade in EURJPY near the round numbers shouldn't been taken, when UseRoundNumberFilter=true:
Attached Image
  • #178
  • Sep 7, 2011 2:19pm Sep 7, 2011 2:19pm
Hi Steve

An observation. All references that I found refer to the PwR indi being Blue or Red, referring to the histogram bars. These to me are the "mode"s 1 and 2 of the indi as used in mql but I see in Aurora's code that you use mode 3 for Up and 4 for Down which refer to the green and white lines of the indi which seem to lag the blue and red.

Am I missing something?

From the code:

PwrDown = iCustom(NULL, 0, "PwR", 4, 1);
PwrUp = iCustom(NULL, 0, "PwR", 3, 1);





Quoting SteveHopwood

  1. PwR indi:

    1. Blue = rising trend
    2. Red = falling trend

  2. Candle_Range_in_pips: Must be <= 15. > 15 stops the trade.
  3. Send a pending Buy at the previous candle high + spread when the previous candle's:

    1. PwR is blue
    2. high is higher and low is higher than that of two candles ago.

  4. Send a pending Sell at the previous candle low - spread when the previous candle's:

    1. PwR is red
    2. high is lower and low is lower than that of two candles ago.



Regards, Nico
Success is a marathon, not a sprint!
  • #179
  • Sep 7, 2011 2:35pm Sep 7, 2011 2:35pm
Quoting NicoScholtz
That was what I assumed as well!
Yep.

  • #180
  • Sep 7, 2011 2:40pm Sep 7, 2011 2:40pm
Quoting NicoScholtz
Hi Steve

An observation. All references that I found refer to the PwR indi being Blue or Red, referring to the histogram bars. These to me are the "mode"s 1 and 2 of the indi as used in mql but I see in Aurora's code that you use mode 3 for Up and 4 for Down which refer to the green and white lines of the indi which seem to lag the blue and red.

Am I missing something?

From the code:

PwrDown = iCustom(NULL, 0, "PwR", 4, 1);
PwrUp = iCustom(NULL, 0, "PwR", 3, 1);









Regards, Nico
After having a look myself, I believe Steve's code is right, 4 and 3 are the right modes

happy pipping!
0 traders viewing now