Open veskur opened 3 years ago
Could you try to run with a higher level of logging, e.g. Output.Console.LogLevel=1
or Output.Console.LogLevel=0
(if you want to save it to a file, as it seems you do, use Output.File.LogLevel
instead). Also add Output.Console.DualSolver.Show=true
to get the output of Cbc in the log file.
And then attach the log file to this issue or send it to me at andreas.lundell@abo.fi? Also if you would be willing to share the problem file, it would make finding the error easier...
Could you also try to only use one thread with Cbc, i.e, --threads=1
, and see if that helps?
The cause of the issue may be Cbc (c.f. https://github.com/coin-or/SHOT/issues/85), which has some stability issues I have not been able to pinpoint... However, that does not explain the missing time-limit, which seems like a bug in either Cbc or SHOT to me.
Thank you for your fast feedback. I added our debug flags and tried the suggested solution but sadly with no success. Attached you find the output files, the first three with core dumps at different times during the computation and the last is one randomly successful run. I will also send you the problem file to the given address.
We are using SHOT for a MIQCQP on Linux (Debian). Sometimes, but not always, SHOT crashes with
Segmentation fault (core dumped)
when using the time limit flagTermination.TimeLimit
(see below). Nevertheless, running SHOT again with exactly the same configuration may or may not succeed. One the other hand, after removing theTermination.TimeLimit
, SHOT has run perfectly fine for now. Interestingly, the time limit is apparently not considered, meaning that a limit of e.g. 2 seconds has long been exceeded when SHOT crashes.Call:
SHOT 160139061642117510802438150482602.osil Model.BoundTightening.FeasibilityBased.TimeLimit=0 Termination.TimeLimit=2 Dual.MIP.Solver=2 --osrl 160121502130516382784313271567890.osrl --log shot.log