-
Notifications
You must be signed in to change notification settings - Fork 23
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
stop_criterion requires knowledge of optima #64
Comments
The thing is even that criterion requires knowledge of the optimizee fitness scale. To really have an optimizee independent solution, we probably will need to find a solution to the fitness scaling issue. |
I thought we already had the solution, with bounding_func also taking care of scaling after being appropriately renamed. I think @dsalaj is working on this. |
but bounding_func only has access to the parameters of an individual, what is responsible for scaling the fitness (apart from the scaling parameter which is again optimizee dependent)? |
True, the fitness is not being scaled. But knowing the scale of the fitness is much much more likely than knowing the actual optima. Since, in many cases, the user defines the fitness. |
Which is not known in most cases. It should be defined as the delta change in fitness where the optimization is stopped.
The text was updated successfully, but these errors were encountered: