ParametricOptInterface.jl
ParametricOptInterface.jl copied to clipboard
jump-dev
Extension for dealing with parameters
@andrewrosemberg motivated me. I love how well layers can play with each other. This will not be merged (as part of POI src) as it does not make sense to...
```julia ERROR: LoadError: ArgumentError: The optimizer ParametricOptInterface.Optimizer{Float64, Xpress.Optimizer} does not support `compute_conflict!` Stacktrace: [1] compute_conflict!(optimizer::ParametricOptInterface.Optimizer{Float64, Xpress.Optimizer}) @ MathOptInterface C:\Users\guilhermebodin\.julia\packages\MathOptInterface\mz9FK\src\MathOptInterface.jl:108 [2] compute_conflict!(model::Model) @ JuMP C:\Users\guilhermebodin\.julia\packages\JuMP\glJ0u\src\optimizer_interface.jl:502 ``` Probably a simple new dispatch...
Closes https://github.com/jump-dev/ParametricOptInterface.jl/issues/146 We actually don't support the `NLPBlock` because POI re-orders the variables by removing parameters. The tests passed because they had parameters at the end. But that isn't a...
I have found an error when modifying one of the test cases: If a parameter is created before the other variables, the model errors when optimizing. ``` ipopt = Ipopt.Optimizer()...
After a chat with @odow and the recent progress with POI we discussed revisiting the use of POI in PowerSimulations.jl I've created a simulation script to test the implementation of...
We have added a few benchmarks and can run them every time a new release is out. This is the first one. **edit in the PR https://github.com/jump-dev/ParametricOptInterface.jl/pull/82 we changed some...
Won't be duals, but there might be ways of getting these shadow prices. For LP's we might get everything from simplex dictionaries...