Jump to content

Pip Accumulator EA


Recommended Posts

  • Replies 319
  • Created
  • Last Reply

Top Posters In This Topic

Soundfx..its not only for you to come up with the solutions which other experts can attend to as well.

 

repeated request to fix the trailing feature to Musketeer,Capella & Co....

 

am not an expert for sure... just trying to help with my little skills...

Perhaps it is better if Soundfx make the changes, it will spare confusion about everyone's intervention in the code...

About TS, I think the invalid ticket (thus no TS) is because of not knowing the ticket number.

Link to comment
Share on other sites

scorpion,

 

 

 

I assume you're using the MT4 backtester for this.

 

Have you checked to ensure that backtesting accurately reflects live trading? I suspect that there will be discrepancies because of the MTF nature of the probability calculation, so that's the first thing to do. Run the EA in live for 3-5 days and note all the trades. Then run the EA in backtest and compare - that way we can be confident (or not) in backtesting this system in general.

 

 

 

Yes, I suspected that we may need to tweak some of the other options as they were untested when I originally posted the EA. I wanted to include them to provide a framework for anyone who wanted to use them, then all they had to do is fix the bugs rather than code everything from scratch.

 

As for optimisation in general - I don't personally think it's a good thing as it's effectively the worse form of curve-fitting. I've created many EA's in the past and optimised them to give fantastic results on one pair/time period only to find that when I run tests going back into earlier years or use different pairs the EA's collapsed in a spectacular heap blowing accounts.

 

I think that the way forward with this EA is to learn from watching the indicators and create new rules to restrict our trades to high probability ones only.

 

In addition to Chandu's method in the manual thread, German's observations shouldn't go unnoticed either - as these could be all the EA needs.

 

The EA logic would need to be upgraded to include the determination of probabilities in all relevant timeframes which is in the latest II_PipAccumulator. Then we just wait for the MTF probabilities to line up at around 35 or -35 and place trades with stop/target 20 as a first test.

 

2 high probability trades like this per day at 80% accuracy and 1:1 risk:reward will give on average at least 100 pips per week.

 

 

Hi, Soundfx

 

Very nice job! Congratulation! I see the increasingly better results!

I am not skilled at the robots so only unfortunately I am an exterior observer and a fan

Have a nice day!

Link to comment
Share on other sites

The problem remains the management of closing.

 

 

Ticket Open Time Type Size Item Price S / L T / P Close Time Price Commission Taxes Swap Profit

131118765 2011.08.31 12:00 sell 0.10 gbpusd 1.62880 1.62374 1.61680 2011.09.01 04:33 1.62374 0.00 0.00 -1.11 50.60

131217540 2011.08.31 21:06 buy 0.20 usdcad 0.97903 0.97553 0.98403 2011.09.01 09:36 0.97553 0.00 0.00 -2.20 -71.76

131289109 2011.09.01 09:36 sell 0.20 usdcad 0.97555 0.97905 0.97055 2011.09.01 11:12 0.97905 0.00 0.00 0.00 -71.50

131223419 2011.08.31 21:50 sell 0.20 eurusd 1.43705 1.42770 1.42605 2011.09.01 12:15 1.42770 0.00 0.00 -3.12 187.00

131311540 2011.09.01 11:12 buy 0.20 usdcad 0.97902 0.97552 0.98402 2011.09.01 15:43 0.97552 0.00 0.00 0.00 -71.76

131260181 2011.09.01 04:33 sell 0.10 gbpusd 1.62342 1.61809 1.61142 2011.09.01 21:09 1.61809 0.00 0.00 0.00 53.30

131355394 2011.09.01 15:13 sell 0.20 eurusd 1.42852 1.42687 1.41652 2011.09.01 22:06 1.42687 0.00 0.00 0.00 33.00

131421862 2011.09.01 21:09 sell 0.10 gbpusd 1.61791 1.61736 1.60591 2011.09.01 22:15 1.61736 0.00 0.00 0.00 5.50

131359346 2011.09.01 15:43 sell 0.20 usdcad 0.97554 0.97904 0.97054 2011.09.02 15:30 0.97904 0.00 0.00 0.18 -71.50

131541561 2011.09.02 15:45 buy 0.20 usdcad 0.97881 0.97531 0.98381 2011.09.02 16:36 0.98381 0.00 0.00 0.00 101.65

131555437 2011.09.02 16:36 buy 0.20 usdcad 0.98405 0.98055 0.98905 2011.09.02 17:56 0.98055 0.00 0.00 0.00 -71.39

131573097 2011.09.02 17:56 buy 0.20 usdcad 0.98049 0.97699 0.98549 2011.09.02 23:43 0.98549 0.00 0.00 0.00 101.47

131432650 2011.09.01 23:25 buy 0.20 eurusd 1.42738 1.41738 1.43938 2011.09.05 00:00 1.41615 0.00 0.00 -0.06 -224.60

131615206 2011.09.05 00:58 buy 0.20 usdcad 0.98656 0.98933 0.99156 2011.09.05 16:55 0.99156 0.00 0.00 0.00 100.85

131659936 2011.09.05 09:00 sell 0.20 eurusd 1.41477 1.40837 1.40277 2011.09.05 17:31 1.40837 0.00 0.00 0.00 128.00

131428878 2011.09.01 22:25 sell 0.10 gbpusd 1.61759 1.60948 1.60559 2011.09.05 17:43 1.60948 0.00 0.00 -0.68 81.10

0.00 0.00 -6.99 259.96

Closed P/L: 252.97

Open Trades:

Ticket Open Time Type Size Item Price S / L T / P Price Commission Taxes Swap Profit

131741839 2011.09.05 16:55 buy 0.20 usdcad 0.99170 0.98820 0.99670 0.98975 0.00 0.00 -0.71 -39.40

131749648 2011.09.05 17:32 sell 0.20 eurusd 1.40858 1.41858 1.39658 1.40968 0.00 0.00 -0.96 -22.00

131751542 2011.09.05 17:43 sell 0.10 gbpusd 1.60939 1.61939 1.59739 1.61175 0.00 0.00 -0.34 -23.60

Link to comment
Share on other sites

Hello Sounfx or musketeer

I want to try several time frames, with the same symbol, I looked and I can not change the magic number, this can obviously lead to conflict,

the question is: Musketeer make a change, and it appears a label, a comment with the TF, used,

so if you use different TF with the same pair, this sequence of numbers ""II_PIPA_EA721194*05*@1.59332[sl] "" + *TF 05/15/60 is used by the EA as a magic number?

Link to comment
Share on other sites

Hi, soundfx

 

Thanks for your efforts and sharing the EA. I've attached the EA on my demo account at broker time around 19.30 and although I had arranged the EA trading times as 5-19, the EA took the trade. Could you please check if the trading times code is functioning properly...

 

Regards,

Link to comment
Share on other sites

I attached the latest version for forward testing on german DAX on M1. And after some minutes a new arrow has been placed. a buy arrow. and what has the EA done? It sold???? Is it a bug???

 

edit: The Buy-Arrow was painted @11:51. And the EA sold @11:54 !? (Enter Determination is standard: ArrowProb)

Edited by ProfNuke
Link to comment
Share on other sites

blueocean,

 

I've been experimenting with various settings without too much success so far. Watching the arrows I'm noticing that the signals are just as bad as any other conventional indicator where we get chopped to bits in ranging periods. However probability alone is something different and that can be traded successfully. Perhaps the probability levels need adjusting to filter out bad signals a bit more - for example entering long at prob > 30 and short at prob < 30 looks as though it could work very nicely and using a trailing stop to let the trades run.

 

ProfNuke - I'm not sure what happened there and because the probability is calculated in real-time and I've only got the EURUSD chart up, I can't see exactly the same signal. In fact the arrow signals were so poor today that you'd have probably been better off selling buy arrows and buying sell arrows lol. I'm thinking of removing arrows altogether from the EA and just working on probabilities as I think that's the way forward.

Link to comment
Share on other sites

kesk,

 

Please read my earlier comments!!!!!

 

This is not yet a profitable EA which you can just plug in and expect to make a fortune from.

 

Optimising will do little good - rather than messing around backtesting and optimising we need to be thinking like traders rather than ****py EA programmers lol. The default settings are not meant to be the best settings possible - they are a starting point.

 

What we need to be doing is studying the indicators in different market conditions and monitoring how the EA could pick up on the best signals and then we can code them.

 

This is an EA development project which is on-going.

Link to comment
Share on other sites

Here's another observation...

 

Setting trailing stops to the last swing high/low could work very nicely. The whole point of trailing stops is that we're following the trend and if swing highs/lows are broken then it's a good sign that the trend is no longer intact.

 

Normally trailing stops with fixed values need to be set at quite a distance e.g. 20-30 pips to prevent us being taken out of big trending moves on relatively minor retracements. However when the trend comes to end, if this happens to be sooner rather than later, we end up giving back those 20-30 pips to the market before our trade is closed. As a general rule in a proper trending market, swing stops should minimise the amount of pips we have to give back to the market.

Link to comment
Share on other sites

Guys - check out how mangiare is trading this system manually.

 

As I mentioned earlier, the way forward is forgetting about the arrows (which are no better than any other arrows coming from conventional indicators). Instead concentrate on the probabilities perhaps with other confirming methods or indicators.

 

This EA needs to be the best approximation possible of a very good manual trading system. This is surprisingly more difficult than it seems as I've lost count of the number of EA's I've seen based on good manual trading systems which fail to come up with the goods.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.




×
×
  • Create New...