Skip to content

[BUG] Incorrect termination status #458

Description

@Iroy30

Describe the bug
The logs determine the solution is infeasible but status returned is Optimal

cuOpt version: 25.10.0, git hash: e40349f, host arch: x86_64, device archs: 80-real
CPU: AMD EPYC 7642 48-Core Processor, threads (physical/logical): 96/96, RAM: 169.08 GiB
CUDA 12.9, device: NVIDIA A100 80GB PCIe (ID 0), VRAM: 79.33 GiB
CUDA device UUID: 68ffffffdf5cfffffff5-71fffffff9-6aff

Unpresolved problem: 4 constraints, 3 variables, 9 nonzeros
Calling Papilo presolver
Presolve status: reduced the problem
Presolve removed: 4 constraints, 3 variables, 9 nonzeros
Presolved problem: 0 constraints, 0 variables, 0 nonzeros
Papilo presolve time: 0.032460
Best feasible: -3.000000
Post-solve status: Post solved solution violates constraints. This is most likely due to different tolerances.
The solution is not feasible after post solve
Solution objective: -3.000000 , relative_mip_gap 0.000000 solution_bound -3.000000 presolve_time 0.032460 total_solve_time 0.000000 max constraint violation 1.000000 max int violation 0.000000 max var bounds violation 0.000000 nodes 0 simplex_iterations 0
STATUS: 1 , REASON: Optimal

Steps/Code to reproduce bug
Run the following MPS file and inspect solution:

NAME
ROWS
 N  OBJ
 L  R0
 L  R1
 L  R2
 G  R3
COLUMNS
    MARK0001  'MARKER'                 'INTORG'
    C0 R0 1
    C0 R1 1
    C0 R3 1
    C0 OBJ -1
    C1 R0 1
    C1 R2 1
    C1 R3 1
    C1 OBJ -1
    C2 R1 1
    C2 R2 1
    C2 R3 1
    C2 OBJ -1
    MARK0001  'MARKER'                 'INTEND'
RHS
    RHS1      R0 1
    RHS1      R1 1
    RHS1      R2 1
    RHS1      R3 1.5
BOUNDS
 LO BOUND1    C0 0
 UP BOUND1    C0 1
 LO BOUND1    C1 0
 UP BOUND1    C1 1
 LO BOUND1    C2 0
 UP BOUND1    C2 1
ENDATA

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

awaiting responseThis expects a response from maintainer or contributor depending on who requested in last comment.bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions