Skip to main content

Issues with outlev and logfile in Gurobi version 10.0.1

Answered

Comments

2 comments

  • Official comment
    Simranjit Kaur
    • Gurobi Staff
    This post is more than two 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.
  • Robert Fourer
    • Gurobi-versary
    • Collaborator

    The problem with outlev=1 not showing any log output was caused by a glitch in the build of Gurobi 10.0.1 for AMPL. It is fixed in the most recent build (dated 20230330).

    The problem with a MIP start being tried, when no starting values were provided by the user, appears to be a bug in the new AMPL-solver interface starting with Gurobi 10.0. The AMPL interface to Gurobi 9.5.2 used our older interface, which did not have this problem. For the case where you are not specifying any MIP start, a workaround is to add mipstart=0 to your gurobi_options string.

    0

Post is closed for comments.