-
Notifications
You must be signed in to change notification settings - Fork 23
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
SCIP.jl with exact-rational branch #288
Comments
Hi, are you sure SCIP.jl is correctly linked to your SCIP installation? You can test that with:
which points to the path where the SCIP shared library is |
Hi, sorry that is a typo in the documentation. The parameter ist 'exact/enabled'. Will fix this. |
Thank you for your help, it now works with "exact/enabled". However, it seems like Julia initializes the problem creation when SCIP.Optimizer() is called, which prevents me from setting the exact mode. I get the following error:
|
Hmm, that is a bit of an issue. I don´t know what can be done on the Julia side of things. The reason this error is necessary is that reading a problem in inexact mode already might not give you exactly the problem you want to solve (inaccuracies when converting to binary, setting small values to 0, etc.) As a hacky fix, you could just set the parameters default value to true in |
Sounds like a good solution, I will try that, thank you! |
Hello
I am trying to use the exact-rational branch of SCIP with this package. I managed to compile if fine to pass the install dir to SCIP.jl in my ENV[“SCIPOPTDIR”].
As indicated on the Readme of the branch (see https://github.com/scipopt/scip/tree/exact-rational), it is required to set the parameter exact/exact_enabled.
However, when I try to set the parameter with set_attribute(model, "exact/exact_enabled", "TRUE")
I obtain:
I also tried
set_attribute(model, "exact/exact_enabled", true)
andset_attribute(model, "exact/exact_enabled", 1)
with the same outcome. I suspect I need to implement something regarding this parameter within SCIP.jl but am unsure what to change.The text was updated successfully, but these errors were encountered: