Introduce Candidates and Candidate IDs
Summary
The current EvoAl implementation has an implicit assumption what a candidate is (a properties vector that adheres to a properties specification). It would be great to make this candidate explicit and to give it a unique candidate id that is created on generation.
Component
evoal.core
, evoal.ea
and evoal.pso
Expected Behavior
No changes in external behaviour in the first step.
Use Case
This feature is necessary to calculate inheritance relations and so on.
Contact Person
(Link a person/ people, that can answer questions about this issue, e.g. yourself)
/cc @berber
Edited by Bernhard Johannes Berger