-
Notifications
You must be signed in to change notification settings - Fork 81
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
Generating a simple problem that reliably triggers hits :UserLimit #342
Comments
You could do something like: Gurobi.jl/test/MOI/MOI_callbacks.jl Lines 27 to 53 in 183a1c5
but set a time limit of 0 seconds or a solution limit of 1 or something. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm on Julia 1.4 but using an older version of the JuMP and Gurobi packages (I'm planning to upgrade soon, but one of my other packages constrains me to using JuMP v0.18.6.):
When solving an MILP via JuMP using the
GurobiSolver
, I've found thatgetobjbound
appears to ignore any constant term (perhaps related to this issue) if the objective is aJuMP.AffExpr
when my solve hits a:UserLimit
. I haven't been able to confirm whether this is an issue if a) my solve does not hit a:UserLimit
or b) forgetobjectivevalue
. (I can get around this issue by adding an additional variable constrained to be equal to the objective and optimizing over the variable instead.)I wanted to add a test (although I'm still not sure which package that test should go into) to ensure that this is no longer the case, but I haven't been able to reproduce this with a simple example as I can't figure out how to reliably trigger
:UserLimit
with a small problem. Does anyone have a suggestion for a problem that is simple to understand but for which I can get the:UserLimit
status?The text was updated successfully, but these errors were encountered: