The BAT Method - The EA | Page 2 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

My Bat from team aphid trades 82 replies

The Bat...a strategy by Team Aphid 775 replies

bo7a method... method for GBP/JPY 205 replies

BAT system for 15 min chart 28 replies

The BAT mathematical formula for lines? 0 replies

Attachments: The BAT Method - The EA
Exit Attachments

The BAT Method - The EA

  • #21
  • Feb 2, 2007 6:32am Feb 2, 2007 6:32am
I have this EA on my platform with smiley face and it isn't making trades. At least it's not trading on the EUR/USD and the GBP/USD this am. As I'm typing, trade has just kicked in on the USD/JPY. Don't know why it wouldn't be working on the other pairs.
  • #22
  • Feb 2, 2007 7:05am Feb 2, 2007 7:05am
EA probably not taking trades where price doesn't actually touch Bat line. If price goes by(around) the line=no trade. Can EA be changed to include these trades? I'm pretty sure TeamAphid are taking these trades.Thank you
  • #23
  • Feb 4, 2007 9:40am Feb 4, 2007 9:40am
Another good EA, I can hardly wait to test V2.
  • #24
  • Feb 4, 2007 10:05am Feb 4, 2007 10:05am
is it just me, or i cant see the EA makign any SEll orders either
  • #25
  • Feb 4, 2007 10:14am Feb 4, 2007 10:14am
http://i19.tinypic.com/2evdcwm.jpg

look @ that sell that it missed out on.

i hope this is fixed in v2
  • #26
  • Feb 5, 2007 3:20am Feb 5, 2007 3:20am
There have been concerns with missed entries of v1. I take them serious, and thus - unfortunatly - cannot publish the v2 before the basic problems in v1 are fixed. Have some patience and bear with me. At the same time thanks for pointing these problems out to me.

I try to go through that as systematic as possible.

The parameters:

5 and 4 as forseen in the original method.

The entry method:

The formula for a long is: "Ask>=Upper && High[1]<=Upper" (where Upper is the actual position of the BAT ATR line)
The formula for a short is: "Bid<=Lower && Low[1]>=Lower" (where Lower is
the actual position of the BAT ATR line)

To explain the meaning of the formula on the example of a long entry. The EA calculates first the position of the BAT ATR line and checks if the actual Ask is greater then or equal to the BAT ATR line and at the same time the High of the previous candle is smaller then or equal to the BAT ATR line. In my humble opinion I should get all prices touching or passing the line and it should be therefore conform with the method. But please feel free to comment.

So why don't we get (seemingly) all trades?

Possibility 1: The systems tries to trade, but it cannot (wrong trade parameters etc.) => This means: If you see that a trade was not taken please check the expert and the journal tab and post eventual error messages.

Possibility 2: My function which replaces the actual external Indicator makes mistakes. I backtested the two functions tickwise against each other and compared (automatically) the results; all was ok. It would astonish me, if it would calculate wrong, but it is still possible. To give you independence of that issue, you will have in future versions of the EA a parameter (Use_BATATR_Indicator) which allows you to switch between my function and the original Indicator.

OPEN ISSUES: The Fibo retracement gets sometimes redrawn after the signal takes place. This has no impact on the actual trades, but it looks ugly. I will try to fix that soon too.
  • #27
  • Feb 5, 2007 3:26am Feb 5, 2007 3:26am
As promised the version 1.1.

The major change. Introduction of the variable Use_BATATR_Indicator. If you put it to true, it will use the original external BAT ATR Indicator.

Besides that you have the values UseAlert and UseMail, which allow you to switch Alerts and Mails according to signals on and off.

The parameters debug does not have any function yet.

The variable Lots is double (now?!?!). Please check, it should now allow 0.01 Lot etc.

Moneymanagement will be introduced in the next mini release.
Attached File(s)
File Type: zip BAT_EA_V_1.1.zip   23 KB | 842 downloads
  • #28
  • Feb 5, 2007 9:27am Feb 5, 2007 9:27am
thanks a lot.

I still get very promising results testing your EA on a demo account? What about you guys?
  • #29
  • Feb 6, 2007 4:41am Feb 6, 2007 4:41am
Quoting fukinagashi
As promised the version 1.1.
Thanks for sharing the EA. I have tried backtesting this on 1hr GBPUSD through 2006 to compare to the results in the main thread. However, I am getting a neutral result / small loss.

I have used Alpari 1m data converted to 5m,15m, & 1hr, every tick to get 90% modelling quality. I get 50% profitable trades, but the average loss is slightly bigger than the average gain.

Any idea what I'm doing wrong?
  • #30
  • Feb 6, 2007 5:54am Feb 6, 2007 5:54am
Again an update. That is actually quite important. I found the real reason why the EA didn't take all trades. It is actually quite obvious once you are aware of it. So again thanks to the testers mentioning that.

As a little recompensation the v1.2 has a few nice new features:

We start with Moneymanagement (RiskPercent). This value can receive any value between 0 and 100 and will take care of your Moneymanagement. If it is 0, it will use the value which is in the variable Lot. If it is for example 3 it will risk 3% of you equity per trade etc. Please be aware that you broker might have the free choice of Lots restricted. A little warning: The Function I use here is clever. If the minimum Lotsize you could open, is 1 Lot, it will open 1 Lot, even if you have only an account equity of 1000 $ and a RiskPercent of 3. It all depends on MinLot, MaxLot and LotStep. If you are not sure about these run this script: http://codebase.mql4.com/972. The function should as well able to deal with Mini, Micro and other ForexAccounts if you Broker sends the right MarketInfos to your instance of MT.

The Parameter MultipleFibos will influence if the system keeps only one Fibo (the actual) with MultipleFibos=false or if you want to leave all Fibos once drawn on the charts MultipleFibos=true. This feature is only optical and has no influence on the trading.

The parameter debug is now very chatative. Leave it off until you really need it (= I ask you for it)

After I have found now the real reason for the bug, I personally will run my EA with Use_BATATR_Indicator=false which means that the system will use again my optimized function in place of the external indicator. The results should/must/will be the same.

ATRPeriod and Factor are the same parameters as used in the original method. They can be changed, but I only made them external so everyone can really be sure that I use these very, original values.

Trade1VolumeFactor, Trade2VolumeFactor and Trade3VolumeFactor are the factors for the lotsize you use for trades 1 (Entry 100%), 2 (61.8%) and 3 (38.2%). The very original method foresaw to enter with 1 Lot, then to enter a retrace to 61.8% with 1 Lot and then a retrace to 38.2% with 2 Lots. Here you have the chance to parameterize that.

It would be kind if you guys would check this version again and come back with me, if you think the EA does not react as it should (canonical ).
Attached File(s)
File Type: zip BAT EA V 1.2.zip   25 KB | 898 downloads
  • #31
  • Feb 6, 2007 8:36am Feb 6, 2007 8:36am
Quoting fukinagashi
Again an update. That is actually quite important. I found the real reason why the EA didn't take all trades. It is actually quite obvious once you are aware of it.
Fukinagashi,

I think the reason that the results are different is that your EA has a TP at 161% on the first trade. I believe TeamAphid have no TP, they just trail the stop at the BAT line.
  • #32
  • Feb 6, 2007 8:57am Feb 6, 2007 8:57am
Nice work fuckinagashi, it is getting the SElls right now
  • #33
  • Feb 6, 2007 9:37am Feb 6, 2007 9:37am
Quoting charlies
Fukinagashi,

I think the reason that the results are different is that your EA has a TP at 161% on the first trade. I believe TeamAphid have no TP, they just trail the stop at the BAT line.
yes, if price hits the 161% and than should retrace back to an entry fib level, no further position should be taken. No TP at 161%. (Based on TA guideline)

However, on manual backtesting I found it profitable more consistantly if I don't care about the 61.8% and 32.8% retracement entries, but focus my whole position on the break of the bat line and take partial profit on this 161% fib extension, and then trail the stop at BAT line. There several possibilities of stop losses and profit taking, I experimented with a second tp level, but these are just minor adjustments.

It would be awesome if this Indicator could be set to define stop losses and TP levels, as a non programmer I don't know how difficult this would be.
But for backtesting different strategies it would be of much help.
I've been manually backtesting so much and it is so tedious, just to backtest a slightly different idea I have to do it all again.... a modifyable EA would be great...

Thanks Fukinagashi for this cool EA
  • #34
  • Feb 6, 2007 12:18pm Feb 6, 2007 12:18pm
Quoting charlies
Fukinagashi,

I think the reason that the results are different is that your EA has a TP at 161% on the first trade. I believe TeamAphid have no TP, they just trail the stop at the BAT line.
Quoting islandtrader
yes, if price hits the 161% and than should retrace back to an entry fib level, no further position should be taken. No TP at 161%. (Based on TA guideline)

Ahhhhhhhhhhhhhhhhhhhhh! A fine canonical EA programmer am I . I completly misunderstood that part. And I had constantly that in my had, that it is a shame to finish trade 1 at 161.8% TP .

Ok, I propose you guys cease the testing of the V1.2. For some technical reasons, this is a bit more then just removing the TP. So stay tune for the V1.3.

I am quite happy though. All this corrections done before the V2.0 will greatly improve the overall quality of the EA for this great method. So again, thank you for you positive input!
  • #35
  • Feb 6, 2007 12:26pm Feb 6, 2007 12:26pm
Quoting islandtrader
However, on manual backtesting I found it profitable more consistantly if I don't care about the 61.8% and 32.8% retracement entries, but focus my whole position on the break of the bat line and take partial profit on this 161% fib extension, and then trail the stop at BAT line. There several possibilities of stop losses and profit taking, I experimented with a second tp level, but these are just minor adjustments.
I know and I do agree ... in a trending market.

In a ranging market you should rather fade the retracements. Since you cannot really foresee what the market means to do tomorrow, the team alphid does the right thing by entering at certain levels of retracement.

Quoting islandtrader
It would be awesome if this Indicator could be set to define stop losses and TP levels, as a non programmer I don't know how difficult this would be.
But for backtesting different strategies it would be of much help.
I've been manually backtesting so much and it is so tedious, just to backtest a slightly different idea I have to do it all again.... a modifyable EA would be great...
And that is what the whole version 2 is about. I am not sure if I made that clear. The break of the BAT ATR line will remain the backbone of the EA, but how to trade that, that I will leave up to you. If you want to open 9 trades at 100% (the break of the line) and close them all at different TP levels => fine. You want to trace any imaginable level of retracement => fine.

I even consider allowing a future version (V3?) to trade against the signal if wanted. We'll see how things work out, but by all means I need your support.

Quoting islandtrader
Thanks Fukinagashi for this cool EA
Oh, you are welcome!
  • #36
  • Feb 6, 2007 12:54pm Feb 6, 2007 12:54pm
Just a question, I have had v1 and v1.1 running now for the week and it has not opened any positions.

I have it on a 1hr tf chart, the little simily is working any idea's.

Glenn
  • #37
  • Feb 6, 2007 5:00pm Feb 6, 2007 5:00pm
Quoting glenn5t
Just a question, I have had v1 and v1.1 running now for the week and it has not opened any positions.

I have it on a 1hr tf chart, the little simily is working any idea's.

Glenn
Hi Glenn,

1. Any error messages in expert / journal tab?
2. Does the system run 24/24?
3. Please try further tests at least with the v1.2. It does probably not yet exploit the full potential (see my post above), but it will trade when it is supposed to.
  • #38
  • Feb 6, 2007 5:20pm Feb 6, 2007 5:20pm
I have similar issue with another EA but not this one. What I had to do is keep the source in the same directory as the executable.
  • #39
  • Feb 6, 2007 5:44pm Feb 6, 2007 5:44pm
Hi fukinagashi and everybody,
Have a look at the EUR/AUD trade which triggered today February 6th at 22:30 gmt. The EA bought at 1.6723, see green arrow... price didn't move up there, if the spread widened it would have been a 30 pip spread.
IBFX said it's unlikely that the spread widened this much, even though exactly at 22:30 gmt there was the AUD interest statement. As price on the charts didn't show any sign of volatility I don't think the entry was due to spread widening either.
Did this happen to anybody else too, or similar things before?
Maybe it was a bad tick, I mean even if there's a bug in the EA the broker wouldn't be able to fill the requested price... does anybody have an idea what happened here?

ps. just demo, no drama, but I wouldn't like it to happen on the live account
Attached Image
  • #40
  • Feb 6, 2007 6:01pm Feb 6, 2007 6:01pm
fukinagashi,
now the EA bought another lot at the entry level, the middle red arrow...
Just thought you might be interested for your new version 1.3 in case there is still some bug lurking in a corner....
I'm looking forward to 1.3 ...
1 trader viewing now