Logging

The Gurobi Optimizer produces a log that allows you to track the progress of the optimization. The Gurobi command-line tool puts the log to both the screen and to a file named gurobi.log by default. The other interfaces just put the log to the screen. Screen output can be controlled using the OutputFlag and the LogToConsole, and file output can be controlled using the LogFile parameter.

The format of the log depends on the algorithm that is invoked.

• Header
• Simplex Logging
• Barrier Logging
• Sifting Logging
• MIP Logging
• Solution Pool and Multi-Scenario Logging
• Multi-Objective Logging
• Distributed MIP Logging
• IIS Logging