The BAT Method - The EA (The BAT Method - The EA) - MT4/MT5 Resources
Please find attached the BAT method for my first EA version.
This is a canonical version. No, this has nothing to do with war. This means that it follows the actual rules slavishly and offers nothing to play with. It will be used for both background testing and front-end testing.
As you can see, I'm only releasing it in compiled form. Don't worry, I will try to sell the spec EA suddenly. The methods used are the intellectual property of TeamAlphid and I already have a job that supports my family. The main reason I do this is that I've had some annoying experiences (people messing with my code and releasing it, people selling my EA without my approval, people complaining about my EA being sold by others without my approval but not bringing in the promised big money, etc.).
Since there aren't many features, there isn't much explanation. You can change the lot size and slippage. That's it. When you backtest, especially if you want to compare the results to those discussed in the main thread, make sure you have Alpari data and 90% model quality.
I should mention that the EA does not depend on the BAT indicator. I put it into a function that mimics the indicator to speed up backtesting (factor ~ 10) and reduce system load when actually running the EA (pre-test).
There is one issue that everyone who wants to use this EA should know. For EA, the mediocre expression "recently or significantly low (high)" is fraught with problems. The trained human eye is better at spotting this low/high than a robot. Now, as a DeMark fan, this should be done via fractals. After some backtesting, I found that the best way is to look for the nearest second level fractal (I tried first to third level and the maximum of 1-3 fractals, but the above seems to be the best). However, there may be times when you disagree with EA.
This is a canonical version. No, this has nothing to do with war. This means that it follows the actual rules slavishly and offers nothing to play with. It will be used for both background testing and front-end testing.
As you can see, I'm only releasing it in compiled form. Don't worry, I will try to sell the spec EA suddenly. The methods used are the intellectual property of TeamAlphid and I already have a job that supports my family. The main reason I do this is that I've had some annoying experiences (people messing with my code and releasing it, people selling my EA without my approval, people complaining about my EA being sold by others without my approval but not bringing in the promised big money, etc.).
Since there aren't many features, there isn't much explanation. You can change the lot size and slippage. That's it. When you backtest, especially if you want to compare the results to those discussed in the main thread, make sure you have Alpari data and 90% model quality.
I should mention that the EA does not depend on the BAT indicator. I put it into a function that mimics the indicator to speed up backtesting (factor ~ 10) and reduce system load when actually running the EA (pre-test).
There is one issue that everyone who wants to use this EA should know. For EA, the mediocre expression "recently or significantly low (high)" is fraught with problems. The trained human eye is better at spotting this low/high than a robot. Now, as a DeMark fan, this should be done via fractals. After some backtesting, I found that the best way is to look for the nearest second level fractal (I tried first to third level and the maximum of 1-3 fractals, but the above seems to be the best). However, there may be times when you disagree with EA.
Attachment to original post (1)
📦 Summary of post attachments (13)
Below are all the files (13) shared in the reply.
💡 Featured Recommendations
✍️ Latest by the author
- •
- •
- •
- •
- •
- •
📌 Popular topics
- •
- •
- •
- •
- •
- •
- •
- •
🔗 You May Be Interested In
- •
- •
- •
- •
- •
- •