-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SHOT exits abruptly on Windows #85
Comments
It is difficult to find the problem without more information... Do you think you could share the .nl file either as an attachment to the issue on Github or by e-mail ([email protected]) if you do not want to make it public? Another thing you could do is to increase the verbosity of the output and upload that. To do this, specify the following parameters
|
This actually happens on Linux as well. But the problem is not with SHOT, but rather it's Cbc (which SHOT uses as a subsolver) that crashes. I tried with a newer version of Cbc (the current master-branch) than the one included in the Windows binaries, but it does not help. I also tried setting some different options for Cbc, but sooner or later Cbc crashed anyway. At this stage I cannot unfortunately put any more effort into finding the exact reason why Cbc crashes, but hopefully this is something that version 3.0 of Cbc will fix whenever it is released. If you have the possibility to use Cplex or Gurobi (both free for academic use), you can use SHOT with those solvers instead. I tested SHOT with CPLEX and that solved your problem. However, there is no precompiled version of SHOT with those solvers so you would need to compile it yourself. |
#159 may be relevant, or maybe not. |
I am using pyomo for a MIQP problem and SHOT just exits abruptly after sometime. I tried using the .nl problem file generated by pyomo directly from SHOT command line but it still exits abruptly. Log is attached. I have been using the same problem with Bonmin solver and it works fine. I am using the SHOT binaries for windows.
SHOT.log
The text was updated successfully, but these errors were encountered: