We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
compute_conflict!
With the previous version of Gurobi.jl, I could run this kind of code:
using JuMP, Gurobi m = Model(Gurobi.Optimizer) @variable(m, x) compute_conflict!(m) MOI.compute_conflict!(backend(m))
With the latest rewrite, I'm getting errors like these:
julia> MOI.compute_conflict!(backend(m)) ERROR: MethodError: no method matching compute_conflict!(::MathOptInterface.Utilities.CachingOptimizer{MathOptInterface.AbstractOptimizer,MathOptInterface.Utilities.UniversalFallback{MathOptInterface.Utilities.Model{Float64}}}) Closest candidates are: compute_conflict!(::Gurobi.Optimizer) at C:\Users\Thibaut\.julia\packages\Gurobi\ntZ45\src\MOI_wrapper.jl:3146 Stacktrace: [1] top-level scope at REPL[20]:1
I now have to use something like MOI.compute_conflict!(backend(m).optimizer.model).
MOI.compute_conflict!(backend(m).optimizer.model)
The text was updated successfully, but these errors were encountered:
You must have been using a direct_model:
direct_model
using JuMP, Gurobi m = direct_model(Gurobi.Optimizer()) @variable(m, x) MOI.compute_conflict!(backend(m))
For the caching optimizer to work, we need to add some methods to MOI.
Sorry, something went wrong.
Thanks for your quick reply! I'm marking this as solved, then, if it's an MOI issue.
No branches or pull requests
With the previous version of Gurobi.jl, I could run this kind of code:
With the latest rewrite, I'm getting errors like these:
I now have to use something like
MOI.compute_conflict!(backend(m).optimizer.model)
.The text was updated successfully, but these errors were encountered: