Move evolution strategy bounds to init #436
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Previously, bounds were passed in to the ES's in the
ask
method. However, we never use dynamic bounds, so it makes more sense to simply pass in the bounds in the init, as is done in the emitters.Also made some other small changes to clean up the ESs (see TODO list below).
While moving the bounds around is a backwards-incompatible change, I do not anticipate this will affect many people since the evolution strategies are mostly internal classes that are called by the emitters.
TODO
lower_bounds
andupper_bounds
toEvolutionStrategyBase.__init__
lower_bounds
andupper_bounds
fromEvolutionStrategyBase.ask()
batch_size=None
toEvolutionStrategyBase.ask()
(currently, all ES's do this but it was not reflected in the base class).EvolutionStrategyBase
threadpool_limits
in sep-CMA-ES, LM-MA-ES, and OpenAI-ES -- threadpool_limits was only intended to help with eigendecompositions, and these classes do not use eigendecompositionsQuestions
Status
CONTRIBUTING.md
yapf
pytest
pylint
HISTORY.md