[BUG] Wrong termination status for LPs with zero constraints
Open
@chris-maes is already working on this.
Since Jun 18, 2025.
bug
- Dominant language
- Cuda
- Stars
- 1k
- Forks
- 233
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 95
Description
Describe the bug
For the following problem without any constraint, the status should either be unbounded or dual infeasible, but cuOpt returns optimal
Steps/Code to reproduce bug
echo "NAME
> ROWS
> N OBJ
> COLUMNS
> x1 OBJ 1
> x2 OBJ 1
> x3 OBJ 1
> x4 OBJ 1
> x5 OBJ 1
> RHS
> RANGES
> BOUNDS
> FR bounds x1
> FR bounds x2
> FR bounds x3
> FR bounds x4
> FR bounds x5
> ENDATA" >test_dual_infeasible.mps
cuopt_cli test_dual_infeasible
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.