-
Notifications
You must be signed in to change notification settings - Fork 3
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
About Fitness computation and storage #3
Labels
Comments
MGO has been entirely redesigned, I think this issue is not valid any-more. Is it? |
I don't know. Remark about elitism() function is cleary obsolete, but we need to check how the elitism is computed for the canonical algorithms NSGA1/2/MOGA. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's not really clear in MGO, there is no declared step for fitness computation.
The step is embeded in elitism() function call during evolution, perhaps there is a better way to create a real function assignFitness() somewhere in the program.
The fitness step need to create a real value attached to each individual, because in many algorithms there are multiple real value fitness computed for each individual. For example, in MOGA or NSGA1 there is no elitism, and selection mechanism operate on full population.
Some examples :
It seems we can cumulate multiple fitness for one individual, so we need a clear way to operate and cumulate this fitness.
The text was updated successfully, but these errors were encountered: