New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collect evolution parameters into own data class #566
Comments
jenetics
added a commit
that referenced
this issue
Aug 21, 2019
jenetics
added a commit
that referenced
this issue
Aug 22, 2019
Mark 'Engine.builder()' method as deprecated.
jenetics
added a commit
that referenced
this issue
Aug 22, 2019
jenetics
added a commit
that referenced
this issue
Aug 22, 2019
jenetics
added a commit
that referenced
this issue
Aug 22, 2019
jenetics
added a commit
that referenced
this issue
Aug 22, 2019
jenetics
added a commit
that referenced
this issue
Aug 22, 2019
jenetics
added a commit
that referenced
this issue
Jan 26, 2020
jenetics
added a commit
that referenced
this issue
Jan 26, 2020
jenetics
added a commit
that referenced
this issue
Jan 29, 2020
jenetics
added a commit
that referenced
this issue
Feb 3, 2020
jenetics
added a commit
that referenced
this issue
Feb 3, 2020
jenetics
added a commit
that referenced
this issue
Feb 3, 2020
…aram #566: Add 'EvolutionParams' class
Merged into r5.2.0 branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The parameters which control the evolution process, like selectors or alterers, are mixed with other
Engine
parameters, when building a new evolutionEngine
. To make it easier to create new engines with a modified fitness function, but with the same parameters, it would be nice to have a data class, which collects this parameters:EvolutionParameter
.It's a sub-task of #302.
The text was updated successfully, but these errors were encountered: