Yep. It's inconvenient without the results table displayed while you're working. But never mind.
Starting genetic optimisation.
First generation passes, second generation begins.
I stop, see the results.
Then I start it again.
Questions:
1. In the results XML file, the Pass column - now displays only one value, not the "generation, number" pairs as it was before. Is it supposed to be like this ?
2. When I start optimization continuation, pairs (0, xxx) appear in the log - i.e. generations seem to start again. Is it supposed to be like that ?
Yep. It's inconvenient without the results table displayed while you're working. But never mind.
Starting genetic optimization.
First generation passes, second generation begins.
I stop, see the results.
Then I start it again.
Questions:
1. In the results XML file, the Pass column - now displays only one value, not the "generation, number" pairs as it was before. Is it supposed to be like this ?
2. When I start optimization continuation, pairs (0, xxx) appear in log - i.e. it looks like generations start again. Is it supposed to be like this ?
The answer is.
Texnolog: Optimisation of a simple MA EA. I interrupted it 2 times and it always optimizes from the beginning.
Why didn't you say from the start that you were running genetics?
The principle of genetic search itself is based on randomness and so it has no point in "continuing what you started". Its job is to run randomly.
And even then the cache is used. It's just that your probability of hitting previously calculated results is very low (you have a search area of 50 million variants). So it looks like starting from the beginning, since the starting point is randomized.
Why didn't you say from the start that you were running genetics?
The principle of genetic search itself is based on randomness and so it has no point in "continuing what you started". Its job is to run randomly.
And even then the cache is used. It's just that your probability of hitting previously calculated results is very low (you have a search area of 50 million variants). So it looks like a start from the beginning, as the starting point is randomised.
That's right.
I have a question about designations - generations should kinda stay ? И
In the latest versions - 1815 and 1816, during optimisation, a screen blink appeared when viewing the"optimisation graph" tab. Windows 7 operating system.
Aliaksandr Yemialyanau: In the latest versions - 1815 and 1816, during optimisation, a screen blink appeared when viewing the"optimisation graph" tab. Windows 7 operating system.
I have a question about the designations - the generations are supposed to stay? И
The generations aren't going anywhere, but their work is a big mystery.
QG 011:57:30.971 Core 1 connected
KF 011:57:30.977 Core 1 authorized (agent build 1816)
DL 011:57:31.040 Core 1 common synchronization completed
IG 011:58:09.237 Tester Best result 3179.39 produced at generation 0. Next generation 1
QH 011:58:15.949 Tester Best result 3202.04 produced at generation 1. Next generation 2
PM 011:58:23.623 Tester Best result 3208.14 produced at generation 2. Next generation 3
HF 011:58:31.384 Tester Best result 3208.14 produced at generation 2. Next generation 4
CJ 011:58:38.068 Tester Best result 3208.14 produced at generation 2. Next generation 5
RO 011:58:44.621 Tester Best result 3289.21 produced at generation 5. Next generation 6
LP 011:58:51.800 Tester Best result 3317.26 produced at generation 6. Next generation 7
CE 011:58:59.147 Tester Best result 3317.26 produced at generation 6. Next generation 8
OI 011:59:07.854 Tester Best result 3317.26 produced at generation 6. Next generation 9
DQ 011:59:13.278 Tester Best result 3317.26 produced at generation 6. Next generation 10
QD 011:59:18.071 Tester Best result 3317.26 produced at generation 6. Next generation 11
EH 011:59:22.291 Tester Best result 3317.26 produced at generation 6. Next generation 12
MO 011:59:25.700 Tester Best result 3339.8 produced at generation 12. Next generation 13
OR 011:59:28.160 Tester Best result 3352.2 produced at generation 13. Next generation 14
FF 011:59:31.179 Tester Best result 3352.2 produced at generation 13. Next generation 15
FM 011:59:32.544 Tester Best result 3352.2 produced at generation 13. Next generation 16
KP 011:59:33.811 Tester Best result 3352.2 produced at generation 13. Next generation 17
QD 011:59:34.378 Tester Best result 3352.2 produced at generation 13. Next generation 18
QK 011:59:36.256 Tester Best result 3352.2 produced at generation 13. Next generation 19
JO 011:59:38.017 Tester Best result 3352.2 produced at generation 13. Next generation 20
QR 011:59:38.811 Tester Best result 3352.2 produced at generation 13. Next generation 21
PI 011:59:39.322 Tester Best result 3352.2 produced at generation 13. Next generation 22
FM 011:59:39.389 Tester Best result 3352.2 produced at generation 13. Next generation 23
EP 011:59:39.394 Tester Best result 3352.2 produced at generation 13. Next generation 24
QG 011:59:39.500 Tester Best result 3352.2 produced at generation 13. Next generation 25
DK 011:59:39.571 Tester Best result 3352.2 produced at generation 13. Next generation 26
MN 011:59:39.575 Tester Best result 3352.2 produced at generation 13. Next generation 27
FR 011:59:39.579 Tester Best result 3352.2 produced at generation 13. Next generation 28
II 011:59:39.933 Tester Best result 3352.2 produced at generation 13. Next generation 29
EL 011:59:40.001 Tester Best result 3352.2 produced at generation 13. Next generation 30
LP 011:59:40.005 Tester Best result 3352.2 produced at generation 13. Next generation 31
OG 011:59:40.009 Tester Best result 3352.2 produced at generation 13. Next generation 32
KI 011:59:40.013 Tester genetic calculation is over
QD 011:59:40.013 Tester result cache used 7038 times
GP 011:59:40.013 Tester genetic optimization finished on pass 8704 (of 651360)
KQ 011:59:40.144 Statistics optimization done in 2 minutes 12 seconds
HG 011:59:40.144 Statistics local 1666 tasks (100%), remote 0 tasks (0%), cloud 0 tasks (0%)
LL 011:59:40.145 Core 1 connection closed
Generations are not going anywhere, the truth is their work is a big mystery.
Why "a big mystery"?
As for the work of the optimizer itself, I don't see any difference. All works well, and understandably, in case of process interruption a new process will be carried out with other data, which is given by randomizer.
I have a question about the designations. I just wanted to use the data of the generations in which this or that result appeared.
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.
In any case the MT5 terminal has nothing to do with it. There's something wrong with the computer.
More likely in the indicators/advisors used.
Yep. It's inconvenient without the results table displayed while you're working. But never mind.
Starting genetic optimisation.
First generation passes, second generation begins.
I stop, see the results.
Then I start it again.
Questions:
1. In the results XML file, the Pass column - now displays only one value, not the "generation, number" pairs as it was before. Is it supposed to be like this ?
2. When I start optimization continuation, pairs (0, xxx) appear in the log - i.e. generations seem to start again. Is it supposed to be like that ?
Yep. It's inconvenient without the results table displayed while you're working. But never mind.
Starting genetic optimization.
First generation passes, second generation begins.
I stop, see the results.
Then I start it again.
Questions:
1. In the results XML file, the Pass column - now displays only one value, not the "generation, number" pairs as it was before. Is it supposed to be like this ?
2. When I start optimization continuation, pairs (0, xxx) appear in log - i.e. it looks like generations start again. Is it supposed to be like this ?
The answer is.
Optimisation of a simple MA EA. I interrupted it 2 times and it always optimizes from the beginning.
Why didn't you say from the start that you were running genetics?
The principle of genetic search itself is based on randomness and so it has no point in "continuing what you started". Its job is to run randomly.
And even then the cache is used. It's just that your probability of hitting previously calculated results is very low (you have a search area of 50 million variants). So it looks like starting from the beginning, since the starting point is randomized.
Updated the terminal to version 1816.
Changed Sleep(60000) to Sleep(5000) in running EA. Compiled on new version of compiler.
I tried to open it on the chart and got EX5 loading failed.
Everything compiled on the old compiler seems to work.
What i have to do with it ? What do I do ?
I was told this
Why didn't you say from the start that you were running genetics?
The principle of genetic search itself is based on randomness and so it has no point in "continuing what you started". Its job is to run randomly.
And even then the cache is used. It's just that your probability of hitting previously calculated results is very low (you have a search area of 50 million variants). So it looks like a start from the beginning, as the starting point is randomised.
That's right.
I have a question about designations - generations should kinda stay ? И
In the latest versions - 1815 and 1816, during optimisation, a screen blink appeared when viewing the"optimisation graph" tab. Windows 7 operating system.
That's right.
I have a question about the designations - the generations are supposed to stay? И
The generations aren't going anywhere, but their work is a big mystery.
Updated the terminal to version 1816.
Changed Sleep(60000) to Sleep(5000) in running EA. Compiled on new version of compiler.
I tried to open it on the chart and got EX5 loading failed.
Everything compiled on the old compiler seems to work.
What i have to do with it ? What do I do ?
Generations are not going anywhere, the truth is their work is a big mystery.
Why "a big mystery"?
As for the work of the optimizer itself, I don't see any difference. All works well, and understandably, in case of process interruption a new process will be carried out with other data, which is given by randomizer.
I have a question about the designations. I just wanted to use the data of the generations in which this or that result appeared.