Closed dlcole3 closed 10 months ago
The above error happens on the most recent version of Plasmo.jl (v0.5.3). However, I just tried this with the most recent master branch of Plasmo, and the error no longer occurs. So maybe this will not be an issue in the next release?
Yes, i confirm this works on main. We can close this once we cut v0.5.4.
I am using expanded subgraphs in Plasmo using the
Plasmo.expand
function. The solution of whichever subgraph is optimized first is reset whenoptimize!
is called on the other expanded subgraph. This only happens in the first instance, and I am not sure why. You can see the error replicated in the code below.Note that the solution is only reset once, and only for the very first expanded subgraph optimized. If I call
optimize!(expanded_subgraphs[1])
after the above code, no solutions are reset and I can query solutions from either expanded subgraph