Oscar Dowson
Oscar Dowson
> Do you mean by monolithic JuMP problem, I mean a single scenario.
> Well I guess the only thing left is for me to actually write the code and see. Yip :smile: > thank you again No problem
Closing because of the lack of a reproducible example. If it is still an issue and you have a reproducible example, please comment below and I will re-open the issue.
> otherwise JuMP needs to traverse the tree-like structure (or even a graph) to retrieve some item, which is quite complex Pyomo keeps things as trees, and yes, they do...
Another option is to explicitly be able to pass in a namespace: ```Julia struct Namespace data::Dict{Symbol,Any} end model = Model() @variable(model, x >= 0) @expression(model, blocks[1:2], Namespace()) @variable(model, x >=...
Maybe we don't even need to provide explicit `Namespace` objects, we just need a way for the user to choose where to store things in macros, and that it will...
@blegat: could you sketch what you had in mind here? Adding some default tests for the shapes doesn't help us show that we use the appropriate shape for a constraint?...
Sure. But this doesn't really help us catch the fact that the solver might return a "different" value to the one we expected (if we didn't think clearly) for the...
MutableArithmetics is not something that we necessarily expect third-parties to widely implement. What is the motivation and where would it be used?
> Why not? Isn't this point of an interface package? Because it requires making the type a `