Skip to content
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

Benders doesn't work correctly for all problems #59

Closed
RalfGollmer opened this issue May 21, 2020 · 5 comments
Closed

Benders doesn't work correctly for all problems #59

RalfGollmer opened this issue May 21, 2020 · 5 comments

Comments

@RalfGollmer
Copy link

Test on the NEOS-Server with dcap233_200 gives wrong optimal objective value with Benders.
Using SCIP
SCIP Status : problem is solved [optimal solution found]
Solving Time (sec) : 1.77
Solving Nodes : 1 (total of 2 nodes in 2 runs)
Primal Bound : +8.82615182183168e+02 (4 solutions)
Dual Bound : +8.82615182183168e+02
Gap : 0.00 %

while dual decomposition gives the correct result
86 +1.833403e+03 +1.835343e+03 +1.833403e+03 0.00 0.11 6777.5
D 87 +1.833403e+03 +1.835343e+03 +1.833403e+03 0.00 0.11 6796.7
Tr STOP with gap tolerance +4.914982e-05 (0.00%).
Status: 3000
Primal Bound: 1835.34
Dual Bound : 1833.4

So if Benders is not applicable for the dcap test problem, the code should detect that and issue a corresponding message instead of pretending to have solved the problem.

See Neos jobs
#8227684
#8226078
#8228073

@kibaekkim
Copy link
Collaborator

The Benders algorithm implemented in the solver is not able to address integer variables in the second stage. Hence, DSP would relaxes the second-stage integrality. I realized that this must confuse users. Thank for reporting!

I will also add the code to display the corresponding message when the Benders is used.

@RalfGollmer
Copy link
Author

RalfGollmer commented May 21, 2020 via email

@kibaekkim
Copy link
Collaborator

OK, then this must be reopened. Thanks for the report again!

@kibaekkim kibaekkim reopened this May 22, 2020
@kibaekkim kibaekkim added the bug label May 22, 2020
@RalfGollmer
Copy link
Author

RalfGollmer commented May 22, 2020 via email

@kibaekkim
Copy link
Collaborator

No worries. I will add a code to print out the warning message in the code.
Thank you!

@kibaekkim kibaekkim removed the bug label May 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants