-
-
Notifications
You must be signed in to change notification settings - Fork 208
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
ConvexSolver didn't found correct solution #559
Comments
Yes, the expected behaviour here would be to get the same (very similar) solution in both cases. (And if there's some problem, don't report the solution as optimal.) Problem seems to be with the accuracy of the iterative Lagrange multiplier solver. This is configurable to help with situations like this. Try changing it with:
or use the extended precision solver:
With that the reported solution is: { 6.222222222222222, -6.0000000000000005E-31, -6.0000000000000005E-31, -6.0000000000000005E-31, 21.77777777777778 } Not the same as either of the solutions you got before. Regardless of the solver's behaviour here you really should avoid generating models with parameters like |
Short term I won't do anything about this. (Don't know what to do.) The issue can be handled by tweaking the iterative solver precision (as described above) but changing the defaults cause other tests to fail. It is (always) recommended to use I'm keeping this test case and hope to solve the issue sometime. |
Hi, Regarding parameters like Thank you one more time for your time and help. |
Hi, I recently run to this issue with Convex solver so I would like to report it.
The next code will demonstrate the problem:
As can be seen from the code the small change in input vector (C) for objective function is causing issue in the Convex solver. It will not converge to correct solution:
Result OK: OPTIMAL -2918.222222273241 @ { 6.22222222387408, 3.2222233327795915, 3.2222222238740756, 3.2222222238740756, 21.777777776125927 }
Result NOK: OPTIMAL -2712.5 @ { -0.0, -0.0, -0.0, -0.0, 25.0 }
The second result is obviously not optimal.
Version used for test: 53.3.0
The text was updated successfully, but these errors were encountered: