We've got a new EA under development. When I run it in the Strategy Tester (using tick data courtesy of Birt's excellent "Tick Data Suite") from Jan 1, 2012 - April 1, 2013, it doesn't make it very far. Here is the Tester log:
13:57:01 BadaBing EURUSD,M1: loaded successfully 13:58:00 BadaBing inputs: MagicNumber=20130325; ExpYear=0; ExpMonth=0; ExpDay=0; Password=1285321; RiskPercent=5; FixedLotSize=1; MarginPercent=20; Leverage=50; PercentK=5; PercentD=3; Slowing=3; PriceField=1; OBZ=90; OSZ=10; ClosePercent=33; MinRange=10; FixedSL=0; SLbarPercent=100; FixedTP=0; TPmultiplier=1; ProfitPips=0; TrailPips=0; Ratio1_XBars2_None0=0; Ratio=1; XBars=3; 13:58:00 2012.01.02 21:00 BadaBing EURUSD,H1: open #1 buy 38.46 EURUSD at 1.29320 ok 13:58:00 2012.01.02 21:00 BadaBing EURUSD,H1: modify #1 buy 38.46 EURUSD at 1.29320 sl: 1.29190 tp: 1.29450 ok 13:58:00 2012.01.02 21:49 Tester: stop loss #1 at 1.29190 (1.29187 / 1.29195) 13:58:00 2012.01.03 09:00 BadaBing EURUSD,H1: open #2 sell 47.50 EURUSD at 1.29769 ok 13:58:00 2012.01.03 09:00 BadaBing EURUSD,H1: modify #2 sell 47.50 EURUSD at 1.29769 sl: 1.29869 tp: 1.29669 ok 13:58:00 2012.01.03 09:00 BadaBing: stopped because of Stop Out 13:58:00 2012.01.03 09:00 Tester: order #2 is closed
Notice that the previous trade hit the stoploss and the Tester says "stop loss #1 at 1.29190 ..."; but that is *not* what it says for the second trade. What does "stopped because of Stop Out" mean? Note it started with a $100,000 starting balance and ended with a -$1,146.35 net loss. I've never seen this error message before.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
We've got a new EA under development. When I run it in the Strategy Tester (using tick data courtesy of Birt's excellent "Tick Data Suite") from Jan 1, 2012 - April 1, 2013, it doesn't make it very far. Here is the Tester log:
13:57:01 BadaBing EURUSD,M1: loaded successfully
13:58:00 BadaBing inputs: MagicNumber=20130325; ExpYear=0; ExpMonth=0; ExpDay=0; Password=1285321; RiskPercent=5; FixedLotSize=1; MarginPercent=20; Leverage=50; PercentK=5; PercentD=3; Slowing=3; PriceField=1; OBZ=90; OSZ=10; ClosePercent=33; MinRange=10; FixedSL=0; SLbarPercent=100; FixedTP=0; TPmultiplier=1; ProfitPips=0; TrailPips=0; Ratio1_XBars2_None0=0; Ratio=1; XBars=3;
13:58:00 2012.01.02 21:00 BadaBing EURUSD,H1: open #1 buy 38.46 EURUSD at 1.29320 ok
13:58:00 2012.01.02 21:00 BadaBing EURUSD,H1: modify #1 buy 38.46 EURUSD at 1.29320 sl: 1.29190 tp: 1.29450 ok
13:58:00 2012.01.02 21:49 Tester: stop loss #1 at 1.29190 (1.29187 / 1.29195)
13:58:00 2012.01.03 09:00 BadaBing EURUSD,H1: open #2 sell 47.50 EURUSD at 1.29769 ok
13:58:00 2012.01.03 09:00 BadaBing EURUSD,H1: modify #2 sell 47.50 EURUSD at 1.29769 sl: 1.29869 tp: 1.29669 ok
13:58:00 2012.01.03 09:00 BadaBing: stopped because of Stop Out
13:58:00 2012.01.03 09:00 Tester: order #2 is closed
Notice that the previous trade hit the stoploss and the Tester says "stop loss #1 at 1.29190 ..."; but that is *not* what it says for the second trade. What does "stopped because of Stop Out" mean? Note it started with a $100,000 starting balance and ended with a -$1,146.35 net loss. I've never seen this error message before.
Thank you,
Jelks