Discussion of article "The checks a trading robot must pass before publication in the Market" - page 7

[Konstantin Seredkin]

Guys, what to do in a similar situation

Robot for FORTS market

Trading from densities in the stack, under a certain density put limit and further maintenance, but in the tester stack does not work, how in such a situation to pass the test for publication, I tried, I corrected the errors, but it can not pass the test + tries to test on the forex market, for which the robot is not designed at all because the robot works on the flipper prices of the stack, all calculations and event model is tied to the events in the stack.

[Rashid Umarov]

Explain the situation to the Market moderators in the comments.

[Andrej Hermann]

Good afternoon.

Check_OrderLevels.mq4 script has a Take Profit check error.

//--- check if there are changes in Takeprofit level
      bool TakeProfitChanged=(MathAbs(OrderTakeProfit()-sl)>tp)

[Rashid Umarov]

Andrej Hermann:

Good afternoon.

Check_OrderLevels.mq4 script has a Take Profit check error.

Thank you, corrected

[Aleh Sasonka]

QUESTION on automatic testing.

Previously, in my trading robots I had input parameter checks written in the OnInit function. And automatic testing did not "swear" at it.

Now the testing shows an initialisation error:

Why can't I stop the execution of a programme with incorrect parameters?

[Mohammad Hashemi]

Good day,

I already trying to upload my EA but when I browse and click in upload; I saw the message " File compiled for Profiling " Could you please let me know what should I do?

Thanks

[Alexandr Gavrilin]

When testing automatically, I get this error. How can I reproduce it in a regular tester, as I don't have such problems there. And the second question, how to fix it?

test on EURUSD,H1 (hedging)
 2016.04.29 20:20:01   failed instant sell 2.00 EURUSD at 1.14491, close #20  buy 2.00 EURUSD 1.14426 [Modification failed due to order or position being close to market]
 2016.04.29 20:20:02   failed instant sell 2.00 EURUSD at 1.14490, close #20  buy 2.00 EURUSD 1.14426 [Modification failed due to order or position being close to market]
 2016.04.29 20:20:02   failed instant sell 2.00 EURUSD at 1.14491, close #20  buy 2.00 EURUSD 1.14426 [Modification failed due to order or position being close to market]

[Ramiz Mavludov]

Alexandr Gavrilin:

When testing automatically, I get this error. How can I reproduce it in a regular tester, as I don't have such problems there. And the second question, how can I fix it?

The modification failed because the order or position was close to the market.

Probably missed the freeze level stopl level check.... I haven't encountered it, but that's probably the reason.

[Alexandr Sokolov]

I have a multicurrency indicator and the names of symbols are specified in the input parameters. In my terminal it works (it finds symbols), but when testing for publication it cannot find symbols that are specified by the standard in the input parameters

What can I do in this situation?

Here is the code that is responsible for checking for the presence of input characters in the initialisation

//--- Checking for correctness of entered characters -----------------
   bool s1 = false, s2 = false, s3 = false;
   for(int s = 0; s < SymbolsTotal(true); s++)
     {
      if(SymbolName(s,true) == symbol1) {s1 = true;};
      if(SymbolName(s,true) == symbol2) {s2 = true;};
      if(SymbolName(s,true) == symbol3) {s3 = true;};
     };
   s3 = (s3 == false && visualize == qs2 ? true : s3);
   if(s1 == false) {Print("Symbol ",symbol1," not found (Symbol #1)"); return(INIT_FAILED);};
   if(s2 == false) {Print("Symbol ",symbol2," not found (Symbol #2)"); return(INIT_FAILED);};
   if(s3 == false) {Print("Symbol ",symbol3," not found (Symbol #3)"); return(INIT_FAILED);};

[Vladimir Karputov]

Also for the tester there is a mention in the help: for the tester it is necessary to force symbol selection in OnInit. That is, first SymbolSelect by three symbols and only then test.

Multicurrency testing