Jose Daniel Lara

This should also apply to the EventModel being developed in the `jd/outages` branch

> Which solver? Gurobi? If so: this is expected behavior. > > In no case is this a bug in PowerModels.jl. It's strictly an issue for whatever solver you are...

I get your point, we had to make similar compromises in PowerSimulations.jl to add explicit ub and lb constraints instead of range ones precisely because of the solver's compatibility with...

> I took another look at this to see if Gurobi had changed. It hasn't. While it appears to have support for interval constraints, it actually implements `l https://docs.gurobi.com/projects/optimizer/en/current/reference/c/model.html#c.GRBaddrangeconstr I...

> > so when they arrive at Gurobi they are compatible with direct mode? > > They can use something like: > > optimizer = MOI.Bridges.Constraint.SplitInterval{Float64}( > Gurobi.Optimizer(), > )...

You can use PowerNetworkMatrices.jl to get the LODF

One issue to consider is the following, in Models with unit commitment (hydro and thermal) if the unit is connected to a PV Bus bus it is essentially off the...

@copilot review the code errors in the getter function that is failing in the tests and make a correction to the tests. Check the logs from the GitHub actions.

The code also needs testing for LODF using ward decomposition

@daniel-thom lets go with #2 Make the new function with the expectation that we won't have many more. This one is a case that we call a lot in models...