PowerModelsSecurityConstrained.jl icon indicating copy to clipboard operation
PowerModelsSecurityConstrained.jl copied to clipboard

A PowerModels Extension for Security Constrained Optimization Problems

Results 10 PowerModelsSecurityConstrained.jl issues
Sort by recently updated
recently updated
newest added

v0.1.0 @JuliaRegistrator register()

I think this statement needs to be reversed?

After v0.4 review coverage report for dead code.

Modify the test networks to include a case where a flow violation occurs in a branch outage case. Currently the only violations occur in generator outages for scenario_02.

Make the file naming convention consistent.

See if flow-cut violation variables can be added to solution dict.

- [ ] should `run_scopf_cuts_dc_soft` allow base-case flow violations? - [ ] can voltage target model be simplified in `run_opf_pg_pf_rect_5`

Add a 500 node network with a pre-filter contingency list to include the most interesting contingencies.

https://github.com/lanl-ansi/PowerModelsSecurityConstrained.jl/blob/5239af613f6bee3bcb0e86a78449115711c8cb87/src/io/goc_c1.jl#L1235-L1244 This logic implies that we output zero for the shunt susceptance if the solution data structure doesn't have shunts. It seems like we should fall back to the network...

The README states that this package does not support switches, unlike PowerModels.jl. I was wondering if there is any particular challenge to implementing switches here, or if it just wasn't...