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
Implementation thoughts: the above call would probably instantiate a AugmentedLagrangian instance and call set_coefficients. The instance call takes a g-value list and returns a penalties list. The penalties sum is meant to be added to the objective value similar to penalty boundary handling. update can be called with the best solution afterwards.
See also ConstrainedFitnessAL which uses an AugmentedLagrangian instance and cma.fmin_con2 which uses the former.
Next steps:
outline/implement a AugmentedLagrangian ask-and-tell use case scenario similar to the one with ConstrainedFitnessAL found in this notebook trying to be less opaque than in these docs
evaluate the advantages/disadvantages to incorporate this functionality directly into tell.
The text was updated successfully, but these errors were encountered:
This looks like it could be easily implemented as an F-penalization within tell which creates an AugmentedLagrangian instance (only) when constraints are passed.
Should we allow using
tell
like (based on a suggestion by @brockho)Implementation thoughts: the above call would probably instantiate a
AugmentedLagrangian
instance and callset_coefficients
. The instance call takes ag
-value list and returns a penalties list. The penalties sum is meant to be added to the objective value similar to penalty boundary handling.update
can be called with the best solution afterwards.See also
ConstrainedFitnessAL
which uses anAugmentedLagrangian
instance andcma.fmin_con2
which uses the former.Next steps:
AugmentedLagrangian
ask-and-tell use case scenario similar to the one withConstrainedFitnessAL
found in this notebook trying to be less opaque than in these docstell
.The text was updated successfully, but these errors were encountered: