-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Release fixes for multi-objective optimization #996
Conversation
Может это каким-то высокоуровневым тестом заодно проверить? Например, для пары целевых функций, где одна - число узлов в графе со знаком плюс, а другая - со знаком минус. Тогда оптимизатор должен найти полный набор. |
@@ -57,12 +64,15 @@ class GenerationKeeper(ImprovementWatcher): | |||
NB: relevant only for single-objective optimization. | |||
initial_generation: Optional first generation; | |||
NB: if None then keeper is created in inconsistent state and requires an initial .append(). | |||
similar: a function that tells in the case of multi-objective optimization | |||
tells the Pareto front whether or not two individuals are similar, optional. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Тут очепятка: два раза tells
Добавил интеграционный тест в fcfee61 |
92ef832
to
6d43d48
Compare
These fixes came from experiments with abstract graph optimization (synthtic task) that seems necessary for the release.
Apparently, Multi-Objective optimization was broken.
Also closes #997