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.

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

Optimality checking and other additional information #3

Open
matthieu-vergne opened this issue May 28, 2014 · 0 comments
Open

Optimality checking and other additional information #3

matthieu-vergne opened this issue May 28, 2014 · 0 comments

Comments

@matthieu-vergne
Copy link
Owner

For the OptimalityChecker of the OptimizerPool, rather than an ambiguous isOptimal(), we should consider both cases of isLocalOptimum() and isGlobalOptimum(). The returned value should be true if it surely an optimum, false if it is surely not, and null otherwise. By the way, as a local optimum is relative to a mutator, maybe isLocalOptimum() should be delegated to the mutator.

More generally, any information (generator, optimality checker, etc.) could correspond to a generic interface Informator, and each kind of Informator could be provided to the incubator to provide (algorithm-independent but domain-dependent) knowledge which can be exploited in the algorithm. Richer information can be provided by more specialized and combined interfaces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant