-
Notifications
You must be signed in to change notification settings - Fork 87
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
Add new attribute NodeLimit #2552
Conversation
this also makes for a clean deterministic limit if one wants to solve a MIP up to the root node only (e.g. to get a dual bound from a tightened LP and solutions from a bunch of heuristics) |
|
||
## Default values | ||
|
||
The provided limit must be a `Union{Nothing,Int}`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about problems with more than typemax(Int32)
nodes solved on 32-bit machines 😆
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's the same issue for many other attributes no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it's common to explore more than 2_147_483_647
nodes on a 32-bit machine 😄
Co-authored-by: Benoît Legat <[email protected]>
This adds a node limit attribute, which seems to make sense given that there is the corresponding termination status. Most MIP solvers have a limit on the number of nodes in the BNB tree. Note that this is in general different from the number of solved LPs, since each node contains its own solve-and-cut loop (at least for SCIP)