Handle cuOpt UnboundedOrInfeasible termination status (11)#3916
Open
rgsl888prabhu wants to merge 3 commits intoPyomo:mainfrom
Open
Handle cuOpt UnboundedOrInfeasible termination status (11)#3916rgsl888prabhu wants to merge 3 commits intoPyomo:mainfrom
rgsl888prabhu wants to merge 3 commits intoPyomo:mainfrom
Conversation
cuOpt added a new termination status (value 11, UnboundedOrInfeasible) that the PSLP presolver returns when it cannot disambiguate infeasibility from unboundedness. The cuopt_direct plugin's status cascade did not recognize it, falling through to TerminationCondition.error and failing any LP_unbounded test. Adds an elif branch mapping status 11 to TerminationCondition. infeasibleOrUnbounded (with SolverStatus.warning / SolutionStatus.unsure). Also extends the status-code comment block to include status 10 (WorkLimit) and 11 (UnboundedOrInfeasible) for documentation. Tracked in NVIDIA/cuopt#1114. Signed-off-by: Ramakrishna Prabhu <ramakrishnap@nvidia.com>
Member
|
This looks reasonable. Can you add a a test that exercises this result from cuOpt? |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3916 +/- ##
==========================================
- Coverage 89.94% 89.93% -0.01%
==========================================
Files 902 902
Lines 106457 106461 +4
==========================================
- Hits 95748 95745 -3
- Misses 10709 10716 +7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
An unbounded LP with no variable bounds triggers cuOpt's presolver to return UnboundedOrInfeasible (status 11); the test asserts the plugin maps it to TerminationCondition.infeasibleOrUnbounded, SolverStatus.warning, and SolutionStatus.unsure.
blnicho
approved these changes
Apr 17, 2026
Member
|
Note: the test appears to require a specific version of cuOpt: |
Author
Status 11 was introduced in cuOpt v26.04.00 (PR #941, tagged 2026-04-09). The CI runs 25.10.0, so PSLP isn't available and status 11 is never produced |
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
4 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.
Summary
cuOpt added a new termination status (value 11, `UnboundedOrInfeasible`) that its presolver returns when it cannot disambiguate infeasibility from unboundedness. The `cuopt_direct` plugin's status cascade does not recognize it, so it falls through to `TerminationCondition.error` and fails the `LP_unbounded` test variants (`test_cuopt_python`, `test_cuopt_python_nonsymbolic_labels`, `test_cuopt_python_symbolic_labels`).
Adds an `elif status == 11` branch mapping to `TerminationCondition.infeasibleOrUnbounded` (with `SolverStatus.warning` / `SolutionStatus.unsure`). Also extends the status-code comment block to include status 10 (WorkLimit) and 11 (UnboundedOrInfeasible).
Tracked upstream in NVIDIA/cuopt#1114.