-
Notifications
You must be signed in to change notification settings - Fork 9
Allow subproblem failures in DominguezRios #121
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
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Q: in what situations can this model not be OPTIMAL? And if it isn't, what should we do with the box?
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.
the other option is
The tolerance issue with HiGHS means that we discard some points, so we find 36 solutions instead of 43:
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.
The paper says

but this is true in theory but not always numerically.
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 think the model should always be feasible (in theory) as long as the feasible set of the original problem is nonempty. The result is used to figure out the location of the nondominated point (whether it is in the box that we are currently looking into to find nondominated points). So it can be infeasible at the very beginning and can return an empty nondominated set.
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.
If the whole problem is infeasible, then we'll catch that in the ideal point computation.
Problem still remains: what if the problem is feasible but our solver fails for some boxes. Perhaps the right behavior is to just skip some? If we error completely, we ignore the fact that this is a nice anytime algorithm with a bunch of good solutions already.
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.
Yes, that is true.
Maybe the fact that we are not applying the reduction rule of the algorithm and deleting the only problematic box is fine. Should we mention somewhere that this is an anytime algorithm and best suited for use with
SolutionLimitorTimeLimit? If someone wants to get all the nondominated solutions, they should use something else. That is actually one of the things I want to explain in the talk.