Added Cut in Callback Not Activated Immediately Even on Single Thread

Ongoing

Mohd. Hafiz Hasan

• July 29, 2020 03:10

Hi,

I'm implementing a callback that adds cuts in C++, and I'm also printing to standard output every time a cut is added. Based on my understanding, if I run the MIP solver on a single thread, then Gurobi should add the cut immediately, but I noticed that is not the case. For instance, in the log shown below, the cut was introduced at the highlighted point:

However, it appears that the cut is not activated until much later in the solver, as the most significant digit of the best bound should jump to 3 if it were activated immediately, but it only goes to 3 some 600 seconds later:

May I know why this is the case, even though I'm running the solver on a single thread? Is there a way to ensure that the cut is activated immediately (as it is a strong one and will significantly save computation time)? 

0

• Official comment

  

  Matthias Miltenberger

  Gurobi Staff

  • August 20, 2020 06:57

  This thread is continued over here.

  Cheers,
  Matthias
• Official comment

  

  Simranjit Kaur

  Gurobi Staff

  • December 06, 2024 00:43

  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 why not try our AI Gurobot?.

Post is closed for comments.