Quote:
Originally Posted by MrPip
The EA I posted was for testing purposes to see what works best. I had hoped that members of this thread would post either back test or forward test of what is working for them. In taht way the EA could be improved and indicators that did not help could be removed.
The default settings work OK but there needs to be a better exit strategy, either with trailing stop or indicator(s). Exiting on the firstr arrow and line does not work because often there is a change of direction from ZigZag with no arrow.
I have seen trades up 200-300 pips close at a loss because of this.
I also found that QQE added as an additional filter caused less loss trades but sometimes later entries.
Is anyone willing to test the EA or am I wasting my time here?
Robert
|
Robert,
I do not think that you wasted your time with writing Bouncing EAs. I thought the best one is BouncingPipEA_MPower_v41 so I started to test it a couple of weeks ago. The EA works well but we need to find good settings.
My test period is not that long one yet, this is why I did not post my results earlier.
Attached please find my statement showing three weeks results.
Pairs tested: AUDJPY, EURCAD, EURJPY, EURUSD, GBPCHF, GBPJPY, GBPUSD, NZDJPY
Broker: NorthFinance
TimeFrame: H1
Settings: as attached
I closed several orders manually or locked the profits manually when I thought a significant retracement would come. I did so because I also experienced profitable orders closed with loss. I used TrailingStopMethod=1 so far, perhaps using method 3 or 4 would be better.
I started the test with such many pairs to try to define the best performing ones. As the statement shows GBPUSD is the best performance so far.
I am not sure but I can imagine that the H4 timeframe fits better to the EA, e.g. the QQE followed almost perfectly the big movement in GBPCHF (to 2.35 from 2.42) on H4 but it was scattered on H1.
So there are lots of open questions to clarify that need lots of tests and experiments: best pairs, exit method, timeframe, just to name a few.
Regards,
Chrisstoff