You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JuMP.value(node::OptiNode,vref::VariableRef) throws an error:
ERROR: KeyError: key Symbol("##260") not found
Stacktrace:
[1] getindex(h::Dict{Symbol, MathOptInterface.ModelLike}, key::Symbol)
@ Base ./dict.jl:482
[2] value(node::OptiNode, vref::VariableRef)
@ Plasmo ~/julia-1.6.2/share/julia/packages/Plasmo/s5YhC/src/optinode.jl:48
[3] top-level scope
@ REPL[22]:1
This can be replicated in the example optigraph_4_nodes.jl by calling:
JuMP.value(node, node[:x])
In optinode.jl:48, the call to JuMP.backend(node).result_location[node.id] throws the error because the node.id symbol is different from the key in the result_location dict.
The text was updated successfully, but these errors were encountered:
Just FYI, fixing this revealed another issue with running optimize! on a node after a graph. It is normally possible to track separate solutions on a node versus the graphs that contain it. Right now, if you optimize a node directly, it will clear all of solutions on each graph. I'll plan to file an issue with a working example.
JuMP.value(node::OptiNode,vref::VariableRef) throws an error:
This can be replicated in the example optigraph_4_nodes.jl by calling:
In optinode.jl:48, the call to JuMP.backend(node).result_location[node.id] throws the error because the node.id symbol is different from the key in the result_location dict.
The text was updated successfully, but these errors were encountered: