Libraries: MultiTester - page 18

 
fxsaber:

It's cheaper that way.

thanks, got it


fxsaber:

But it's not enough.

There are not many options - only encode input parameters so that GA cannot quickly find a local maximum.

ZY: a couple of weeks ago I studied this question, there was even a simple coding algorithm specifically for GA, but I can't find it.

UPD: Gray's coding for GAs is used Wiki about GAs - there is a link to Gray's coding there.

 

A good demonstration of why it's good to do several GAs in a row.

Here are five GAs.

 
fxsaber:

Please clarify.

For some reason I missed this message.

There is often a situation when changing some variable in a certain range does not change the result. Then one of the random values from this range is given as the best result, or there are consecutive values that return the same result. To get at the top the minimum or maximum (depending on the meaning of the variable) value of the variable from this range with the same result, I introduced such a micro penalty. The results in the sorting list remain at the same positions, but they become slightly different, and the GA finds the minimum/maximum value of the variable from the range of identical values at the expense of new passes.

At the same time, by increasing the number of passes, new maxima are often found.

Have I explained, or is the question different?

PS by the way, at the end of genetics generations pass very quickly, so this increase in the number of passes does not slow down optimisation much.

 
Hi all. Can you tell me how to make it not once run optimisation, but for example 10 times. And who I, for example, choose 5 custom pairs. And run multitester. And it only makes one run on each pair. But I want it to make more runs. If anyone has a solution, please tell me.
 
fxsaber:

A good demonstration of why it is useful to do several GAs in a row.

Here are five GAs.

and you can do it 50 times and get a bruteforce :D

 
Maxim Dmitrievsky:

or you can do it 50 times and get a bruteforce :D

Bruteforce is practised, but honest, of course.

 

Sometimes it is convenient to limit the duration of one Optimisation. For example, it should not last longer than an hour.

The easiest way is to add a frame mode with a timer to your Expert Advisor. In the timer, when the time threshold is reached, press the Stop button via MTTester.mqh.

 
2492 - Win terminal forms have changed, it seems. Now the clicker has to be redesigned, looking for new codes...
 
Edgar Akhmadeev:
2492 - Win terminal forms have changed, it seems. Now the clicker has to be redesigned, looking for new codes...

You only need the clicker for Start/Stop, it works.

ZЫ I updated to the version I had long time ago.
 
fxsaber:

You only need the clicker for Start/Stop, it works.

ZY I updated it to a version I had a long time ago.

Actually, I'm not talking about the specific MultiTester programme, but about its clicker base, which I took away. I have the clicker set many fields before optimising, and something has changed there. I'll have to look into it a little later, for now I've rolled back.

Just reporting a change in the terminal, not a problem in this programme.