Skip to content
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.

Sign up for GitHub

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

Jump to bottom

EvaluatedCandidate & PopulationData classes must not be final #30

Open
virl opened this issue Feb 1, 2017 · 0 comments
Open

EvaluatedCandidate & PopulationData classes must not be final #30

virl opened this issue Feb 1, 2017 · 0 comments

Comments

@virl
Copy link

virl commented Feb 1, 2017 •
edited

EvaluatedCandidate class must not be final, because when implementing custom EvolutionEngine, users often want to associate additional data with each EvaluatedCandidate.

For example, if each candidate's fitness is compound fitness from several simulations, user may want (for reporting / logging purposes) store all fitness components in EvaluatedCandidate's custom inherited class.

Currently finality of EvaluatedCandidate & PopulationData classes prevents users from properly implementing custom EvolutionEngine.
@virl virl changed the title EvaluatedCandidate class must not be final EvaluatedCandidate & PopulationData classes must not be final Feb 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@virl