Skip to content

internal statuses leak through #77

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

Closed
mlubin opened this issue Aug 16, 2016 · 3 comments
Closed

internal statuses leak through #77

mlubin opened this issue Aug 16, 2016 · 3 comments

Comments

@mlubin
Copy link
Member

mlubin commented Aug 16, 2016

CPLEX.jl sometimes returns :CPXMIP_TIME_LIM_INFEAS when it should be :UserLimit

@mlubin
Copy link
Member Author

mlubin commented Aug 24, 2016

Closed by #78

@mlubin mlubin closed this as completed Aug 24, 2016
@IssamT
Copy link
Contributor

IssamT commented Nov 14, 2016

shouldn't this :CPXMIP_NODE_LIM_INFEAS be also considered as :UserLimit ?

@IssamT
Copy link
Contributor

IssamT commented Nov 14, 2016

Looking at the documentation of MathProgBase

If status does not indicate error or infeasiblity, the other members have the following values:

objval – optimal objective value
sol – primal solution vector
attrs – a dictionary that may contain other relevant attributes such as:
objbound – Best known lower bound on the objective value

it seems that both

:CPXMIP_TIME_LIM_INFEAS
:CPXMIP_NODE_LIM_INFEAS

should be translated into :Unfeasible and not :UserLimit

But then the user does not know if the problem is really unfeasible ...

Maybe we should split the the status :UserLimit to somthing like :UserLimitFeas and :UserLimitUnfeas

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

No branches or pull requests

2 participants