Merged
Conversation
…d scaling; also scaling any dual bound in HighsInfo
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## latest #3186 +/- ##
=======================================
Coverage 73.18% 73.19%
=======================================
Files 432 432
Lines 105464 105499 +35
Branches 16987 16991 +4
=======================================
+ Hits 77184 77216 +32
- Misses 28004 28007 +3
Partials 276 276 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Opt-Mucca
approved these changes
Jul 29, 2026
Opt-Mucca
left a comment
Collaborator
There was a problem hiding this comment.
This must have been a pain to track down. Looks good to me!
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
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.
When user cost and bound scaling is applied, both scale the objective value. As observed in #3178, unless any offset is also scaled, this can lead to changes in the gap in the MIP solver, and a different optimal solution.
This closes #3178