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
Could you explain how the popsize_factor should be used. As far as I understood it just alters the population size, e.g. if I define popsize = 100 and popsize_factor = 0.9 it just calculates new iterations with a population of 90. Why should we not just define it as popsize = 90? I understood that the population size starts with 100, then 90 in the next iteration then 81 and so on?
Thank you for the clarification and the great package!
The text was updated successfully, but these errors were encountered:
importcmacma.CMAOptions('popsize_fac')
{'popsize_factor': '1 # multiplier for popsize, convenience option to increase default popsize'}
In contrast to popsize, popsize_factor defines the population size relative to the popsize value. This can be sometimes convenient, for example when we don't know the default population size or when sweep through different dimensions and want a population size which is twice the default. That is all there is to it.
As far as I understood it just alters the population size, e.g. if I define popsize = 100 and popsize_factor = 0.9 it just calculates new iterations with a population of 90.
Kind-of, yes.
Why should we not just define it as popsize = 90?
There is no good reason, if you do want a popsize of 90.
I understood that the population size starts with 100, then 90 in the next iteration then 81 and so on?
Could you explain how the popsize_factor should be used. As far as I understood it just alters the population size, e.g. if I define popsize = 100 and popsize_factor = 0.9 it just calculates new iterations with a population of 90. Why should we not just define it as popsize = 90? I understood that the population size starts with 100, then 90 in the next iteration then 81 and so on?
Thank you for the clarification and the great package!
The text was updated successfully, but these errors were encountered: