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

Terminating optimization when leaving root node posts a different bestbound than the one in log.

ユーザーの入力を待っています。

コメント

2件のコメント

  • Nicolas Zerega
    • Gurobi-versary
    • Curious
    • Conversationalist

    I solved it by just setting the parameter NodeLimit to 1

    But I still have the question as to why gurobi explores +2 nodes even when I tell it to stop when the NODCNT != 0

    0
  • Jaromił Najman
    • Gurobi Staff Gurobi Staff

    Hi Nicolas,

    Could you also try setting the Threads parameter to 1 instead of NodeLimit. It is possible that additional threads were able to start exploring the tree and improved the lower bound already.

    Best regards, 
    Jaromił

    0

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