Re: "The conflict graph is either empty or too big"

I was told that it is quite normal for a MILP problem.

But the lines haven't change for quite a while :

+258023: mip =     not found yet >=  5.819440044e+004        (242; 34)
+260157: mip =     not found yet >=  5.819440044e+004        (242; 34)
+262192: mip =     not found yet >=  5.819440044e+004        (242; 34)
+264262: mip =     not found yet >=  5.819440044e+004        (242; 34)
+266054: mip =     not found yet >=  5.819440044e+004        (242; 34)
+267696: mip =     not found yet >=  5.819440044e+004        (242; 34)
+269282: mip =     not found yet >=  5.819440044e+004        (242; 34)
+269824: mip =     not found yet >=  5.819440044e+004        (243; 34)

For 15-30 minutes, only the inside of the parenthesis has changed...

Since I'm running on Gusek, I don't know which solver is used neither how to change it :-/

If anybody can help ? Should I wait more or stop it and change some parameters ?

Thanks a lot.

B.

spiritfire wrote:

Hi,

I'm running a simulation and it's taking quite a while...

I'm running on Gusek, which is the only way I found to use GLPK (couldn't figure out how to install on win)


The program seems to found a solution :

OPTIMAL SOLUTION FOUND
Integer optimization begins...
Gomory's cuts enabled
MIR cuts enabled
Cover cuts enabled
Clique cuts enabled
Creating the conflict graph...
The conflict graph is either empty or too big


But then it goes on searching for quite a while :simul.mod

Time used: 1294.0 secs.  Memory used: 55.1 Mb.
+176120: mip =     not found yet >=  5.813433080e+004        (195; 6)
+176321: mip =     not found yet >=  5.813433080e+004        (196; 6)

I have no clue if it's close to the solution, if it's taking too long or if I should wait or ... ?

Does anybody know if it is normal ?

my code is attached.

Thank you.