メインコンテンツへスキップ

Complementary Slackness: Issues with Big-M

回答済み

コメント

2件のコメント

  • Riley Clement
    • Gurobi Staff

    Hi Zhisheng,

    You can use addGenConstrIndicator to avoid choosing a Big M value, but I don't expect this would resolve your problem.

    Your best bet is to try and tune the solver.  I would first try with different combinations of MIPFocus and Presolve and if you want to dive deeper then the following video may help: Introduction to Performance Tuning.

    - Riley

    0
  • Zhisheng Xiong
    • First Comment
    • Gurobi-versary
    • First Question

    Hi Riley,

    Thanks for your valuable information. I have checked the code examples and video, and now have some ideas in mind. I will try running my optimization again. 

    Since the solution of the KKT system is used to generate cuts in a decomposition algorithm, if the solution quality is poor, the cuts will be weak—or worse, the whole algorithm may converge prematurely.

    0

サインインしてコメントを残してください。