Version: 0.6.0

# Constraint Violation (CV) As Objective¶

Another way of dealing with constraints is putting them into one of the objectives instead. Then, the goal is not only to find solutions that satisfy all constraints but also provide some trade-off of how much better performance one can achieve when relaxing the constraint a little bit. This can be helpful information for post-processing. Another advantage of this approach is that it is more robust against diversity loss. However, it is worth noting that this method might spend many function evaluations on infeasible solutions that might not be of interest. Moreover, if not the exact boundary solution is found, where the first objective (cv) is minimized, the best solution might still be slightly infeasible.

[2]:

from pymoo.algorithms.moo.nsga2 import NSGA2
from pymoo.constraints.as_obj import ConstraintsAsObjective
from pymoo.optimize import minimize
from pymoo.problems.single import G1
from pymoo.visualization.scatter import Scatter

problem = G1()

problem = ConstrainedProblem()

algorithm = NSGA2(pop_size=100)

res = minimize(ConstraintsAsObjective(problem),
algorithm,
('n_gen', 300),
seed=1,
verbose=False)

plot = Scatter()
plot.show()


Compiled modules for significant speedup can not be used!
https://pymoo.org/installation.html#installation

To disable this warning:
from pymoo.config import Config
Config.warnings['not_compiled'] = False


[2]:

<pymoo.visualization.scatter.Scatter at 0x127369030>


Finally, the least infeasible solution can then be obtained by:

[3]:

from pymoo.core.evaluator import Evaluator
from pymoo.core.individual import Individual

cv = res.F[:, 0]
least_infeas = cv.argmin()
x = res.X[least_infeas]

sol = Individual(X=x)
Evaluator().eval(problem, sol)

print("Best solution found: \nX = %s\nF = %s\nCV = %s" % (sol.X, sol.F, sol.CV))

Best solution found:
X = [0.51040777 0.48990933]
F = [0.50052725]
CV = [0.]