[Gurobi] error code 10001: NodefileStart set to 0.1 but the Nodefile was not generated

751 views
Skip to first unread message

Bird

unread,
May 13, 2010, 10:32:00 PM5/13/10
to Gurobi Optimization
Hi,

I ran a MIP problem with 20024 Rows, 16080 Columns and 48826
NonZeros. It was terminated with error code 10001.

Part of the output is

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
142657 93968 1.1258e+07 46 1849 1.1281e+07 1.1249e+07 0.28% 45.2
13693s
142859 94164 1.1273e+07 147 1266 1.1281e+07 1.1249e+07 0.28% 45.1
13702s
143035 94319 1.1278e+07 248 1068 1.1281e+07 1.1249e+07 0.28% 45.1
13708s
143114 94385 1.1257e+07 40 2126 1.1281e+07 1.1249e+07 0.28% 45.1
13710s
143118 94389 1.1260e+07 42 2077 1.1281e+07 1.1249e+07 0.28% 45.1
13716s
143126 94397 1.1262e+07 46 1858 1.1281e+07 1.1249e+07 0.28% 45.1
13722s
143141 94413 1.1267e+07 54 1685 1.1281e+07 1.1249e+07 0.28% 45.1
13738s

Cutting planes:
Gomory: 295
Implied bound: 1397
Clique: 1
MIR: 462
Flow cover: 26746
Zero half: 80

Explored 143263 nodes (6535399 simplex iterations) in 13741.60 seconds
Thread count was 2 (of 2 available processors)

Solve interrupted (error code 10001)
Best objective 1.1280847020e+07, best bound 1.1248789213e+07, gap
0.2842%
ERROR: Out of memory
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

My options settings in the gurobi.env files are:
NodefileDir .
ResultFile solution.sol
Threads 2

I added "NodefileStart 0.1" to the gurobi.env file, but the
Nodefile was not generated when the consumed memory exceeded 0.1GB.

By the way I ran Gurobi from command line ">gurobi_cl data.lp" on a
Windows machine with Dual Core 3.0GHz and 3.00 GB memory.

Could you please give me some suggestion on how to avoid the out of
memory issue?

Thank you!


Greg Glockner

unread,
May 14, 2010, 3:39:39 PM5/14/10
to gur...@googlegroups.com
You should try a few things:

1) Ensure that your gurobi.env file is in the working directory

2) If the parameters are set correctly, you will see something like the following in the output:

Set parameter NodefileStart to value 0.1

3) Try setting the parameters via the command line as explained in the last section of:

http://www.gurobi.com/doc/30/quickstart/node3.html

4) Try setting NodefileStart to an even smaller value such as 0.01

Bird

unread,
May 20, 2010, 11:21:59 AM5/20/10
to Gurobi Optimization
Greg, thank you for your reply!

It saved the node files to disk after I changed parameter
NodefileStart to value 0.05.
Reply all
Reply to author
Forward
0 new messages