You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The optimization is done in ~ 2000 function evaluations with a tolfun stopping criterion.
If we then do
es.optimize(lambdax: cma.ff.sphere(x-1))
The step-size of es increases for 1000 more function evaluations before decreasing for another 2000 function evaluations and we hit a tolstagnation criterion.
The idea was to avoid this adaptive phase that costs 1000 function evaluations when activating a kernel that we did not turn off on purpose (mainly for budget allocation) during the optimization of a changing fitness.
Activity
nikohansen commentedon Oct 27, 2021
Another question: why don't we activate the kernel unconditionally?
nikohansen commentedon Oct 27, 2021
Tentative code:
cheikhToure commentedon Oct 28, 2021
Yes it was meant to read
!=.cheikhToure commentedon Oct 28, 2021
The tentative code was meant to activate a kernel that we inactivated beforehand, mainly for budget allocation.
When we do:
The optimization is done in ~ 2000 function evaluations with a
tolfunstopping criterion.If we then do
The step-size of
esincreases for 1000 more function evaluations before decreasing for another 2000 function evaluations and we hit atolstagnationcriterion.The idea was to avoid this adaptive phase that costs 1000 function evaluations when activating a kernel that we did not turn off on purpose (mainly for budget allocation) during the optimization of a changing fitness.
nikohansen commentedon Oct 29, 2021
Maybe we want a method that checks for deactivation status, like
which would allow to write
to activate the kernel only when it was inactivated before.