You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting the number of variables, objectives and constraints should be made with methods instead of state variables.
The reference front is not known for real-world problems and it is used mainly for plotting and for calculating quality indicatores. It does not make sense that it has to be part of a problem.
The directions is used to indicate whether the objective functions are to be minimized or maximized, which is used for generating output results. However, jMetalPy assumes that all the objectives are to be minimized, so this field can bring confusion to users.
The proposal to deal with these issues is to redefine the constructor as follows:
About the reference_front and directions state variables, the suggestion is to remove the first one while the second one should be properly documented.
The text was updated successfully, but these errors were encountered:
Class
Problem
in jMetalPy has the following constructor:Several points can be pointed out here:
directions
is used to indicate whether the objective functions are to be minimized or maximized, which is used for generating output results. However, jMetalPy assumes that all the objectives are to be minimized, so this field can bring confusion to users.The proposal to deal with these issues is to redefine the constructor as follows:
This way, the
FloatProblem
class can be implemented in this way:So the unconstrained benchmark problem
Kursawe
can be defined as:In the case of the constrained problem
Srinivas
, it can defined in this way:About the
reference_front
anddirections
state variables, the suggestion is to remove the first one while the second one should be properly documented.The text was updated successfully, but these errors were encountered: