-
Notifications
You must be signed in to change notification settings - Fork 110
Compute relative gap with respect to user objectives #418
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
Conversation
|
/ok to test |
@rg20, there was an error processing your request: See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/1/ |
|
/ok to test 40f19a2 |
aliceb-nv
left a comment
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.
Thanks for the super quick fix Rajesh!
|
/ok to test 40f19a2 |
|
/ok to test d42c7b8 |
|
/ok to test d5edb2e |
|
/merge |
Description
In branch-and-bound, to stop the search, we are currently computing the relative gap based on the working problem. When the objective offset is very large, the relative gap on the user problem can be very large even when it is small on the working problem. This PR fixes this by always computing the relative gap with respect to the user problem.
Issue
Closes #417
Checklist