Fix bugs on empty problem and pre_process assignment#18
Merged
rapids-bot[bot] merged 8 commits intoNVIDIA:branch-25.05from May 20, 2025
Merged
Fix bugs on empty problem and pre_process assignment#18rapids-bot[bot] merged 8 commits intoNVIDIA:branch-25.05from
rapids-bot[bot] merged 8 commits intoNVIDIA:branch-25.05from
Conversation
akifcorduk
added
bug
Collaborator
|
@akifcorduk Does this also cover @hlinsen bug fix? |
Contributor
Author
|
Yes, it should cover that. But i think @hlinsen should also review. Maybe there is some conflicts. |
hlinsen
approved these changes
May 19, 2025
Contributor
hlinsen
left a comment
hlinsen
left a comment
There was a problem hiding this comment.
lgtm. One small coding style comment.
rg20
reviewed
May 20, 2025
Contributor
Author
|
/merge |
jieyibi
pushed a commit
to yining043/cuopt
that referenced
this pull request
Mar 26, 2026
There was a bug in pre_process_assignment function. During initial solve() we are doing preprocess and then trivial_presolve. That means, the free var replacements are added first then the variable eliminations are done. For that reason the user solution preprocessing should follow the same order. The bug of set_solution is called multiple times in the tests if fixed: we should to pop the back solution after solution is being set, otherwise it will always be set. The bug of he assignment resize is fixed: it should be called before the gather, if not the resize will enlarge it and it will have junk values, causing mismatch in objective costs and sometimes infeasible solutions. This also changes a slight issue where we assign 2x for y and x for z when x is positive, for large initial values this might cause numerical issues, that's why we now assign x for y and 0 for z. This PR also fixes the bug of empty solutions not being handled correctly after a presolve (previously we handled it only for trivial presolve). Authors: - Akif ÇÖRDÜK (https://github.com/akifcorduk) Approvers: - Hugo Linsenmaier (https://github.com/hlinsen) URL: NVIDIA#18
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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 bug in pre_process_assignment function. During initial solve() we are doing preprocess and then trivial_presolve. That means, the free var replacements are added first then the variable eliminations are done. For that reason the user solution preprocessing should follow the same order.
The bug of set_solution is called multiple times in the tests if fixed: we should to pop the back solution after solution is being set, otherwise it will always be set.
The bug of he assignment resize is fixed: it should be called before the gather, if not the resize will enlarge it and it will have junk values, causing mismatch in objective costs and sometimes infeasible solutions.
This also changes a slight issue where we assign 2x for y and x for z when x is positive, for large initial values this might cause numerical issues, that's why we now assign x for y and 0 for z.
This PR also fixes the bug of empty solutions not being handled correctly after a presolve (previously we handled it only for trivial presolve).