You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* add current-voltage formulation in rectangular coordinates
* add tests for OPF and PF problem types
* add initial docs
* constraint formulation tweak
* remove unneeded constraints
* adding doc strings
* Debugged and unit tested
* IVRPowerModel subtype of ACRPowerModel
* dcline power limits through variable definitions
* separate series and total branch current variables
* Update CHANGELOG.md
* add check variable bounds test
At this time, any kind of comment, question, feature request or bug report is welcome in the issue tracker. If you are asking a question, please search the issues for an answer before making a post.
3
+
At this time, any kind of comment, question, feature request or bug report is welcome in the issue tracker. If you are asking a question, please search the issues for an answer before making a post.
4
4
5
5
## Code Contributions
6
6
@@ -9,7 +9,7 @@ Community-driven development and enhancement of PowerModels is welcomed and enco
9
9
That said it is important to keep in mind the code-quality requirements and scope of PowerModels in mind, before preparing a contribution.
10
10
11
11
### PowerModels Scope
12
-
The primary motivation for PowerModels is to help researchers quickly and easily replicate _established_ results in power system optimization.
12
+
The primary motivation for PowerModels is to help researchers quickly and easily replicate _established_ results in power system optimization.
13
13
More preliminary research and development efforts are best left to other packages, which extend PowerModels.
14
14
That said, the PowerModels package should have a software design that makes building such extensions as easy as possible.
15
15
@@ -19,7 +19,7 @@ To that end, the following code quality controls are necessary for all contribut
19
19
- all features must have unit tests
20
20
- naming conventions must be consistent
21
21
- core features must have documentation
22
-
- code style must be consistent (e.g. 4 spaces for indetnation)
22
+
- code style must be consistent (e.g. 4 spaces for indentation)
23
23
24
24
Due to these quality control requirements, pull request to PowerModels may require lengthy discussion and code review (e.g. see [#111](https://github.com/lanl-ansi/PowerModels.jl/pull/111)).
- Frederik Geth (@frederikgeth) CSIRO, storage modeling advise, Branch Flow and current-voltage formulation
62
64
- Jonas Kersulis (@kersulis) University of Michigan, Sparse SDP formulation
63
65
- Miles Lubin (@mlubin) MIT, Julia/JuMP advise
64
66
- Yeesian Ng (@yeesian) MIT, Documenter.jl setup
@@ -69,13 +71,13 @@ The primary developer is Carleton Coffrin(@ccoffrin) with support from the follo
69
71
70
72
If you find PowerModels useful in your work, we kindly request that you cite the following [publication](https://ieeexplore.ieee.org/document/8442948/):
71
73
```
72
-
@inproceedings{8442948,
73
-
author = {Carleton Coffrin and Russell Bent and Kaarthik Sundar and Yeesian Ng and Miles Lubin},
74
-
title = {PowerModels.jl: An Open-Source Framework for Exploring Power Flow Formulations},
75
-
booktitle = {2018 Power Systems Computation Conference (PSCC)},
74
+
@inproceedings{8442948,
75
+
author = {Carleton Coffrin and Russell Bent and Kaarthik Sundar and Yeesian Ng and Miles Lubin},
76
+
title = {PowerModels.jl: An Open-Source Framework for Exploring Power Flow Formulations},
77
+
booktitle = {2018 Power Systems Computation Conference (PSCC)},
0 commit comments