Libraries: MultiTester - page 7

New comment
 
Сергей Таболин:

This is an option ))) But if you set, for example, 10 cycles, you will have to press the Stop button 9 times. ))) And one time would be better (want)))).

Well, it has almost nothing to do with the library. As you write an Expert Advisor based on the library, so it will be.

The advisor in KB is only an example of using the library.

 
I wanted to control reconnection. I tried to add Login function to the clicker. In the Navigator/Favourites window "clicking" VK_HOME works, but VK_ENTER does not. Is the login blocked?
 
Edgar:
I wanted to control reconnection. I tried to add Login function to the clicker. In the Navigator/Favourites window "clicking" VK_HOME works, but VK_ENTER does not. Is the login blocked?

To run the Tester on different brokers?

 
fxsaber:

To run the Tester on different brokers?

No, I tell you, for reconnection.

Very often the terminal is connected to the server with ping 300-400 ms, although there are servers with 60-70 ms, and even pressing "Rescan network" does not change anything. The terminal holds on to the server to the last and does not switch.

This is certainly not in the MultiTester stream, but within your clicker code I have learnt from you. It was the best idea for me in a long time.

 
Reconnect works under MT4. Ask for a solution for 5 on the forum. This thread is not read.
 

Can you please see why the optimisation charts are not closed in this multitester variant? If over-optimisation is performed only on currency pairs, they are closed.

#include <fxsaber\MultiTester\MultiTester.mqh>
#property description "Shape-forward optimisation..."
enum shap_per {day,week,month};
input uchar shaping = 1; //Number of test runs
input uchar per_mod = 1; //Test period multiplier
input datetime start_test = D'2019.07.01';
input shap_per period_val = day; //Length of the test period
//+------------------------------------------------------------------+
//||
//+------------------------------------------------------------------+
// This function is responsible for generating the task list.
void SetTesterSettings()
  {
   ENUM_TIMEFRAMES perd_1 = PERIOD_D1;
   datetime open_day = start_test;
   switch(period_val)
     {
      case week:
         perd_1 = PERIOD_W1;
         break;
      case month:
         perd_1 = PERIOD_MN1;
         break;
      default:
         break;
     }//switch
   int p_step = PeriodSeconds(perd_1) * per_mod;
//--Encrease the test start date by one period
   for(uchar p = 0; p < shaping; p++)
     {
      // Search all symbols from the Market Watch.
      for(int i = SymbolsTotal(true) - 1; i >= 0; i--)
        {
         const string Name = SymbolName(i,true);
         Print(Name);
         TesterSettings.Add(NULL,Name,0,open_day,0);
        }//i: Symbols
      open_day -= p_step;
     }//p: Periods
  }//SetTesterSettings()
 
Good Beer:

Can you please see why the optimisation charts are not closed in this multitester variant? If over-optimisation is performed only on currency pairs, they are closed.

I cannot reproduce it.

 
fxsaber:

Can't get a playback.

Maybe the settings are wrong? In Shape-Forward the end date of testing is stable, the start date is pushed back all the time, by the length of the period. Example of settings in order:

3; 1; 9.09.2019; week. Forward - custom 16.09.2019; end of testing period 21.09.19. The start will be inserted from the Expert Advisor. This hemo is due to the lack of possibility to read the start date from the tester window. It turns out 3x by the number of pairs in the market overview the number of optimisation windows.

 
Good Beer:

Maybe the wrong settings?

Make a screenshot of the Tester settings.

 
fxsaber:

Take a screenshot of the Tester settings.

There is a testing process going on, but it should be clear:

multitester settings:

multitester

terminal tester settings

terminal

slow - there is one parameter

1234567891011121314...45
New comment