Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SCIP optimizer status likely ser incorrectly. #285

Open
jd-lara opened this issue Mar 10, 2024 · 4 comments
Open

SCIP optimizer status likely ser incorrectly. #285

jd-lara opened this issue Mar 10, 2024 · 4 comments

Comments

@jd-lara
Copy link

jd-lara commented Mar 10, 2024

JuMP can't retrieve the result of a successful optimize! call giving the result below. It might be a case that the status is set incorrectly in the MOI wrapper.

image
@jd-lara
Copy link
Author

jd-lara commented Mar 10, 2024

The problem goes away if direct_mode isn't used. So far I tried to reproduce in a small problem and didn't happen.

@matbesancon
Copy link
Member

are you sture this is SCIP-related? It seems like a JuMP error no?

@matbesancon
Copy link
Member

cc @odow

@odow
Copy link
Contributor

odow commented Apr 21, 2024

We need a reproducible example, or the output of JuMP.solution_summary(model).

We only throw this error if the termination status is MOI.OPTIMIZE_NOT_CALLED:
https://github.com/jump-dev/JuMP.jl/blob/509ab616192bc90891c329010e2205f414c8cf94/src/optimizer_interface.jl#L716-L719

SCIP maps SCIP_STATUS_UNKNOWN to MOI.OPTIMIZE_NOT_CALLED:

SCIP_STATUS_UNKNOWN => MOI.OPTIMIZE_NOT_CALLED,

So perhaps the fix probably needs to happen in SCIP.jl. I don't know why the status would be unknown; it looks like the solver found a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants