Tobias Achterberg
Gurobi Staff Total activity 188
 Last activity
 Member since
 Following 0 users
 Followed by 0 users
 Votes 0
 Subscriptions 77
Activity overview
Latest activity by Tobias Achterberg
Tobias Achterberg commented,
You need to add each of your constraints with m.addConstr().

Tobias Achterberg commented,
In your formulation, I think that you always need to use (1  bi) for all the bigM constraints as you have formulated them.

Tobias Achterberg commented,
I think that your bigM constraints are wrong. For example, b1=0 will force I[v][i] <= 120*SOC_avg[v][i] due to the first bigM constraint. This is not what you want. You only want to force constra...

Tobias Achterberg commented,
For example, say you have four different regions based on the relationship of x and y in which you have different objective functions. Then you need four binary variables to indicate in which regio...

Tobias Achterberg commented,
The log file looks okay. It seems pretty difficult to find a feasible solution for your model. What you see in the table is the output of the branchandbound tree search. The algorithm successivel...

Tobias Achterberg commented,
This is actually not a bug. It is due to the large (actually, infinite) domains of your variables and the consequences that this has for the piecewise linear approximation that we use for the log ...

Tobias Achterberg commented,
This looks like a bug. Thanks for reporting! I will investigate and check what is going on. Tobias

Tobias Achterberg commented,
Yes, you can do this manually. But you can also just use the "and" general constraint: addConstr(z == and_(x,y)). Moreover, you can just stick with your quadratic objective function as indicated in...

Tobias Achterberg commented,
In very rare cases it may even help to also use barrier for the local node relaxations. There is of course the very big downside that barrier cannot benefit from the warm start information that you...

Tobias Achterberg commented,
Hi Austin, yes, your observation is correct. The fix in Gurobi 9.5 just means that those solutions are discarded from the solution pool. It does not mean that they are already pruned in the search ...