-
Notifications
You must be signed in to change notification settings - Fork 7
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
Adjusting (where appropriate) for maximization #2
Comments
Any thoughts why when _ScalarObjective has the maximize = True the solve_pareto_front_representation function fails. |
Hi Jed. I will look into this later today. I have my own suspicions why this problem is emerging. |
@JedStephens I was able to reproduce the same results with both snippets of code you shared. The issue was that MOProblem expects its nadir and ideal points to be expressed as if each of the objectives were to be minimized. Also, when computing slices: desdeo-mcdm/desdeo_mcdm/utilities/solvers.py Line 208 in cda1301
It was previously assumed that the values in the ideal point were always less than the values in nadir point. In other words, the assumption of everything being minimized was screwing things up. Also, when defining an
I think this is confusing and we should address this in the future.
|
@gialmisi much appreciated as usual. |
@gialmisi Would you help me get to the right starting point for some of these problems.
When
_ScalarObjective
has themaximize = True
thesolve_pareto_front_representation
function fails.Code to reproduce:
The above process can be restated as a minimization problem. To do this I negate all the output values, change the upper and lower bounds and adjust the nadir and ideal values.
(That's a lot to remember!)
Now the code will run.
Code to reproduce
The text was updated successfully, but these errors were encountered: