Skip to main content

Different solutions between Gurobi 7.5.2 and 8.1.1

Answered

Comments

3 comments

  • Official comment
    Simranjit Kaur
    Gurobi Staff 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 why not try our AI Gurobot?.
  • Oscar Dowson
    Gurobi-versary
    First Question
    First Comment

    To follow up, it appears to be an integer feasibility tolerance issue. It seems that v8.1.1 has a tighter tolerance by default, and the "better" solution found by v7.5.2 is actually integer infeasible with a tighter tolerance.

    0
  • Daniel Espinoza

    Hi Oscar,

     

    Indeed, it seems that it is a tolerance issue, if you tighten primal tolerances in v752 you get the same value as in v811.

    Now, it seems that you are modeling some implication constraints (I see lots of 1e6 * binary in the constraints and very large right hand sides). If accuracy is an issue for you, you might want to try changing the numeric focus, or using implication constraints and let gurobi do the reformulation as a MIP....

    Hope this helps,

    Daniel

    0

Post is closed for comments.