ACORN-11869: Populate variable values for FEASIBLE status in HiGHS#5
Merged
Conversation
…lver Fix crash when HiGHS returns FEASIBLE status (time limit, node limit, gap tolerance). Now populates variable_value, objective_value, and best_objective_bound for both MPSOLVER_OPTIMAL and MPSOLVER_FEASIBLE, consistent with SCIP solver behavior.
PedramHooshangiAUGAI
requested review from
AlexAshbourneAGMT and
ChiaraPiacentiniAGMT
March 17, 2026 15:02
AlexAshbourneAGMT
approved these changes
Mar 17, 2026
ChiaraPiacentiniAGMT
approved these changes
Mar 17, 2026
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
3 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.
This pull request updates the solver logic in
highs_proto_solver.ccto improve how solution results are handled. The main change is expanding the conditions under which the solver sets the objective value and best objective bound in the response.Solver result handling:
HighsSolvePrototo set theobjective_valueandbest_objective_boundwhen the solver status is eitherMPSOLVER_OPTIMALorMPSOLVER_FEASIBLE, instead of only when it isMPSOLVER_OPTIMAL.…lverFix crash when HiGHS returns FEASIBLE status (time limit, node limit, gap tolerance). Now populates variable_value, objective_value, and best_objective_bound for both MPSOLVER_OPTIMAL and MPSOLVER_FEASIBLE, consistent with SCIP solver behavior.