Actually to get out of the way I put a condition in OnInit() that closes the EA and gives way to the next pass.
which gives me an error in the journal:
This solution improves the time in the test, by preventing to evaluate with those values, but it DOES NOT IMPROVE THE TOTAL EVALUATION, since the passes that closes the EA are counted with result 0.
you can return INIT_PARAMETERS_INCORRECT if the timeframes are not the way you want them
you can return INIT_PARAMETERS_INCORRECT if the timeframes are not the way you want them
both order
if timeframeIND1 >= timeframeIND2){ return ( INIT_SUCCEEDED ); }
who does not give any comment in the newspaper, and
if timeframeIND1>= timeframeIND2){ return ( INIT_PARAMETERS_INCORRECT ); }
which is given in the newspaper:
2025.03 .10 12 : 59 : 28.515 Core 1 genetic pass ( 0 , 2 ) tested with error "incorrect input parameters" in 0 : 00 : 00.004
In both cases, results with 0 operations still appear (as with ExpertRemove() ).
I really want to eliminate that situation and improve the efficiency of genetic optimization by changing those "0 operations" to evaluations.
both order
who does not give any comment in the newspaper, and
which is given in the newspaper:
In both cases, results with 0 operations still appear (as with ExpertRemove() ).
I really want to eliminate that situation and improve the efficiency of genetic optimization by changing those "0 operations" to evaluations.
I see , maybe you can go the custom criterion type of test and return INT_MIN for those cases as a score.
Actually to get out of the way I put a condition in OnInit() that closes the EA and gives way to the next pass.
which gives me an error in the journal:
This solution improves the time in the test, by preventing to evaluate with those values, but it DOES NOT IMPROVE THE TOTAL EVALUATION, since the passes that closes the EA are counted with result 0.
Is there any possibility to condition the value of variable 2 in function of variable 1 in the genetic test?
Yes, this is a known drawback of the optimization process how it's implemented in MT5.
You can find a workaround in the algotrading book.

- www.mql5.com
Yes, this is a known drawback of the optimization process how it's implemented in MT5.
You can find a workaround in the algotrading book .
Just what I need, thanks.

- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Actually to get out of the way I put a condition in OnInit() that closes the EA and gives way to the next pass.
which gives me an error in the journal:
This solution improves the time in the test, by preventing to evaluate with those values, but it DOES NOT IMPROVE THE TOTAL EVALUATION, since the passes that closes the EA are counted with result 0.