setObjective() not updating when called on GRBModel object
AnsweredHi, I am having trouble with the setObjective() and getObjective() functions in Gurobi. Specifically, getObjective() does not seem to return the correct model objective after updating via setObjective() For example, in the code below,
mod = gp.Model("model")
x = mod.addVar(lb = 0, ub = 5, vtype = GRB.CONTINUOUS, name = "x")
y = mod.addVar(lb = 0, ub = 5, vtype = GRB.CONTINUOUS, name = "y")
z = mod.addVar(lb = 0, ub = 5, vtype = GRB.CONTINUOUS, name = "z")
obj = mod.setObjective(x+y, GRB.MAXIMIZE)
print(mod.getObjective())
the program returns "0" as the model objective. It does actually optimize and solve the model correctly, but I am trying to write a program in which I need to call mod.getObjective() as part of the argument of the setObjective() function, so this is causing issues. I am trying to negate the current objective, but when I retrieve the new objective with getObjective(), it returns the original objective still.
Additionally, if I split up setting the objective into two lines (the expression on the first, and then setting GRB.MAXIMIZE on the second), the program behaves as a minimization problem. Maybe this is just syntax that I'm not aware of.
Any help would very much be appreciated in figuring out this issue! Thanks!
-
Official comment
-
Gurobi Staff
This post is more than two years old. Some information may not be up to date. For current information, please check the Gurobi Documentation or Knowledge Base. If you need more help, please create a new post in the community forum, or try Gurobot, our chatbot interface offering instant, expert-level support. -
-
-
You have to call the update method first before querying any model objects.
obj = mod.setObjective(x+y, GRB.MAXIMIZE)
mod.update()
print(mod.getObjective())This is due to the lazy update mechanism.
0 -
-
Thank you for your prompt response!
0 -
Post is closed for comments.
Comments
3 comments