gurobi.log file

[Gabe]

I have the python API installed for Gurobi 4.5.1 and everything is
working great. I do, however, get a little annoyed by the gurobi.log
file that gets created everywhere I run my applications. Is it
possible to setup a default location where this file will be written
each time. I'm using linux, so maybe somewhere like /tmp/ ?

[Greg Glockner]

The log is controlled via the LogFile parameter.

If you want to permanently set the location of the LogFile parameter, you could either modify the gurobi.env file, or modify gurobi.sh to set LogFile upon initialization via the global setParam() function.

[Greg Glockner]

Sorry, I rechecked the software. My previous suggestions will set the logfile to a different location. However, they will not prevent Gurobi from writing an initial logfile (gurobi.log) in the current working directory. Guess the best thing is to call the following Python code:

setParam('LogFile', '/path/to/your/logfile/gurobi.log')
import os
os.unlink('gurobi.log')

If you're using the interactive shell, you could automate this by adding it to gurobi.py.

[Gabe]

Thank you

[Greg Glockner]

> Is not being able to prevent an initial log file from being written deemed a bug or a feature? I would hope the former.

It's only an issue for the Python API. See previous posts in this thread for a workaround.

[brandon willard]

I'm seeing the same thing with gurobi_cl.

On Monday, November 5, 2012 4:34:19 PM UTC-6, Hamish Waterer wrote:

> Is not being able to prevent an initial log file from being written deemed a bug or a feature? I would hope the former.

It's only an issue for the Python API.  See previous posts in this thread for a workaround.

So it's a bug. :)

[Greg Glockner]

This is a known issue with the interactive versions. Except for Python, it is not an issue for the APIs.