Tobias Achterberg
-
Gurobi Staff
- 合計アクティビティ 107
- 前回のアクティビティ
- メンバー登録日
- フォロー 0ユーザー
- フォロワー 1ユーザー
- 投票 0
- サブスクリプション 0
コメント
Tobias Achterbergによる最近のアクティビティ-
If you are talking about a trial license, this is restricted to models with at most 2000 columns and 2000 rows.
-
This question is very hard to answer, because just like in MILP, the size is not necessarily the most important factor when it comes to the time needed to solve a model. The more important aspect i...
-
The "NoRelHeuristic" parameter is undocumented. Just set it to 1 in order to activate the heuristic. You cannot predict when new incumbent solutions will be found and how their quality will be. Of ...
-
No, this is not directly possible. In constraint programming, such a constraint is refered to as "element constraint", i.e., you have a decision variable as the index into some array. If your m_j v...
-
Gurobi only supports products of pairs of variables, not triples. To overcome this issue, you need to introduce auxiliary variables and build the more complex expression using those. For example, i...
-
I fear that you have to ask this question in the Pyomo community. Gurobi does not try to call any program that is called "xx". I think this must come from Pyomo.
-
You cannot parallelize the calls to addConstrs(). But maybe you can parallelize the construction of the set of constraints that you add. For example, you could try building 8 different sets of cons...
-
Hi Taylor, column generation really is an art. Typically, you cannot just say "these are too many variables, let's ignore some and price them in later". This approach would be very similar to the ...
-
SOS1 constraints are handled via branching. If you have a solution that would be feasible without the SOS1 constraint but that violates this SOS1 constraint (i.e., both z and s are non-zero), then ...
-
Are you using the "Cuts=3" parameter setting? From the source code, this looks like being the only way of getting cuts before the first call to the user callback function. Regards, Tobias