Libraries: MultiTester - page 6

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

I just noticed. Where is this coming from?

The dates that are currently displayed in Tester.

 
fxsaber:

The dates that are currently on display in the Tester.

In fact, I realise that it should be there, but it's not. I'm very interested in getting these dates programmatically.

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

In fact, I realise that it should be there, but it's not. I'm very interested in getting these dates programmatically.

TesterDate is a date not set by MultiTester.

You can start MultiTester. Then interrupt it. Change the dates in Tester. Start MultiTester and it will continue with the dates you changed in Tester. So it makes sense.

 

You can choose advisors.

#include <fxsaber\MultiTester\MTTester.mqh> // https://www.mql5.com/ru/code/26132

void OnStart()
{
  if (MTTESTER::SetExpertName("Examples\\Moving Average\\Moving Average.ex5"))
    Print(MTTESTER::GetExpertName() + " - OK.");
  else
    Print("Failed.");
}
 
Updated all files. Added an example of launching several Expert Advisors. 
#include <fxsaber\MultiTester\MultiTester.mqh> // Multiple runs/optimisations in Tester.

// This function is responsible for generating the task list.
void SetTesterSettings()
{
  static const string ExpertNames[] = {"Examples\\Moving Average\\Moving Average.ex5",
                                       "Examples\\MACD\\MACD Sample.ex5",
                                       "Examples\\Controls\\Controls.ex5",
                                       "Examples\\ChartInChart\\ChartInChart.ex5"};

  const int Size = ArraySize(ExpertNames);

  for (int i = 0; i < Size; i++)
    TesterSettings.Add(ExpertNames[i]);
}


Now, if you need to check/compare different versions of your EAs, you can create a similar source, run multi-optimisation and do other more pleasant things.

As it turned out, such a thing is more good not for searching symbols (although it is also suitable), but for comparative analysis of Expert Advisors.

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

Faced with a power outage.

Thanks for prompting to write this thing.

I had a few hours of shuffles going on 2171 that had a bug with freezing. Saw on the forum that 2174 was out. Just stopped MultiTester, recompiled EAs and started MultiTester. And it continued from the same place where it was stopped. It was unexpectedly convenient.

A good example of why you should put your toolkit in the public domain. You can see from the outside what can be useful.

 

Good day.

I have encountered one small inconvenience.

The thing is that I have added "cycles". The default setting is 6 cycles. You know, it is when optimisation of one character is performed 6 times.

So, the other day I added an additional block of signals to one of my Expert Advisors. Of course, I decided to run optimisation. I set 3 cycles. Everything works, everything is fine. But! I knew that on some symbols the Expert Advisor is almost useless. It does not drain, but there is no return. Now it came to such a symbol, the first cycle has passed and I can see from the results that further optimisation makes no sense.

This is where the question arises - what to do?

Suggestion: it would be great if there was a small panel like this (sorry, not an artist :)

Then I would simply click on the "Skip" button when I see that there is no prospect for a given symbol, this symbol would be removed from the queue, the current optimisation would be stopped and optimisation of the next symbol would start.

Is this possible?

P.S. Right now I just have to wait for two more passes, and the pass lasts over an hour. More than two hours of lost time. Pathetic ))))
 
So just press the Stop button in the Tester when the unwanted character has started.
 
fxsaber:
So just press the Stop button in the Tester when the unwanted character has started.

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)))).

 
★★★★★
12345678910111213...45
New comment