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.

Sign up for GitHub

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

Jump to bottom

CglTwomir generates invalid cuts #36

Closed
svigerske opened this issue Mar 2, 2019 · 1 comment
Closed

CglTwomir generates invalid cuts #36

svigerske opened this issue Mar 2, 2019 · 1 comment
Labels
bug Something isn't working CglTwomir

Comments

@svigerske
Copy link
Member

Issue created by migration from Trac.

Original creator: ojasparekh

Original creation time: 2010-09-20 23:31:08

Assignee: somebody

Version: release 0.5.1

In determining whether a row is bounded, the DGG_getData function uses a fixed value of DBL_MAX rather than the OsiSolverInterface object's getInfinity() value. This resulted in invalid cuts with OsiCpxSolverInterfacel. This bug may affect other Cgl generators as well.
@svigerske svigerske added bug Something isn't working CglTwomir major labels Mar 2, 2019
@svigerske svigerske removed the major label Mar 11, 2019
This was referenced Mar 11, 2019
Closed
Open
@svigerske
Copy link
Member Author

Good observation. CglTwomir has been fixed up. For others, #44 has been created.

tkralphs pushed a commit that referenced this issue Mar 11, 2019
@svigerske
use solvers infinity instead of (COIN_)DBL_MAX for absent bounds/sides
66dbf20 
- fixes #33
- fix suggested in #36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working CglTwomir
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@svigerske