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

Stopping criteria for PoolSearchMode

回答済み

コメント

3件のコメント

  • 正式なコメント
    Simranjit Kaur
    • Gurobi Staff
    This post is more than three 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.
  • Mario Ruthmair
    • Gurobi Staff

    Hi Oscar,

    You are basically right, if the gap is below the value set by the MIPGap parameter and the desired number of different solutions is found (PoolSolutions), then the solver should terminate.

    There are, however, some additional subtleties: The solutions have to differ in the values for the integer variables to count as "different", the continuous variables are ignored here. This could be one reason why your solve takes longer.

    Best regards,
    Mario

    0
  • Mario Ruthmair
    • Gurobi Staff

    If you want have more control over the termination, you could use the MIPSOL callback to check and count solutions, and the current MIP gap, and then call abort() to cancel the process.

    0

投稿コメントは受け付けていません。