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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,7 +96,8 @@ Neither anonymous contributors nor those utilizing pseudonyms will be accepted.
96
96
97
97
There are other great tools out there to manage DCO signoffs for developers to make it much easier to do signoffs:
98
98
* Git makes it easy to add this line to your commit messages. Make sure the `user.name` and `user.email` are set in your git configs. Use `-s` or `--signoff` to add the Signed-off-by line to the end of the commit message.
99
-
*[GitHub UI integrations](https://github.com/scottrigby/dco-gh-ui) for adding the signoff automatically to commits made with the GitHub browser UI
99
+
*[Github UI automatic signoff capabilities](https://github.blog/changelog/2022-06-08-admins-can-require-sign-off-on-web-based-commits/) for adding the signoff automatically to commits made with the GitHub browser UI. This one can only be activated by the github org or repo admin.
100
+
*[GitHub UI automatic signoff capabilities via custom plugin](https://github.com/scottrigby/dco-gh-ui) for adding the signoff automatically to commits made with the GitHub browser UI
100
101
* Additionally, it is possible to use shell scripting to automatically apply the sign-off. For an example for bash to be put into a .bashrc file, see [here](https://wiki.lfenergy.org/display/HOME/Contribution+and+Compliance+Guidelines+for+LF+Energy+Foundation+hosted+projects).
101
102
* Alternatively, you can add `prepare-commit-msg hook` in .git/hooks directory. For an example, see [here](https://github.com/Samsung/ONE-vscode/wiki/ONE-vscode-Developer's-Certificate-of-Origin).
|`id`|`int32_t`| - | ID of a component, the id should be unique along all components, i.e. you cannot have a node with `id` 5 and a line with `id` 5. |✔|✔|❌ (id needs to be specified in the update query, but cannot be changed) |✔|
155
-
|`energized`|`int8_t`| - | Indicates if a component is energized, i.e. connected to a source |✔|❌|❌|✔|
155
+
|`energized`|`int8_t`| - | Indicates if a component is energized, i.e. connected to a source ||❌|❌|✔|
156
156
157
157
## Node
158
158
@@ -163,9 +163,9 @@ The base type for all power grid components.
163
163
| name | data type | unit | description | required | input | update | output | valid values |
|`u_rated`|`double`| volt (V) | rated line-line voltage |✔|✔|❌|❌|`> 0`|
166
-
|`u_pu`|`RealValueOutput`| - | per-unit voltage magnitude |✔|❌|❌|✔||
167
-
|`u_angle`|`RealValueOutput`| rad | voltage angle |✔|❌|❌|✔||
168
-
|`u`|`RealValueOutput`| volt (V) | voltage magnitude, line-line for symmetric calculation, line-neutral for asymmetric calculation |✔|❌|❌|✔||
166
+
|`u_pu`|`RealValueOutput`| - | per-unit voltage magnitude ||❌|❌|✔||
167
+
|`u_angle`|`RealValueOutput`| rad | voltage angle ||❌|❌|✔||
168
+
|`u`|`RealValueOutput`| volt (V) | voltage magnitude, line-line for symmetric calculation, line-neutral for asymmetric calculation ||❌|❌|✔||
169
169
170
170
171
171
## Branch
@@ -184,15 +184,15 @@ In this case, the attribute `from_status` and `to_status` is always 1.
184
184
|`to_node`|`int32_t`| - | ID of node at to-side |✔|✔|❌|❌| a valid node id |
185
185
|`from_status`|`int8_t`| - | connection status at from-side |✔|✔|✔|❌|`0` or `1`|
186
186
|`to_status`|`int8_t`| - | connection status at to-side |✔|✔|✔|❌|`0` or `1`|
187
-
|`p_from`|`RealValueOutput`| watt (W) | active power flowing into the branch at from-side |✔|❌|❌|✔||
188
-
|`q_from`|`RealValueOutput`| volt-ampere-reactive (var) | reactive power flowing into the branch at from-side |✔|❌|❌|✔||
189
-
|`i_from`|`RealValueOutput`| ampere (A) | current at from-side |✔|❌|❌|✔||
190
-
|`s_from`|`RealValueOutput`| volt-ampere (VA) | apparent power flowing at from-side |✔|❌|❌|✔||
191
-
|`p_to`|`RealValueOutput`| watt (W) | active power flowing into the branch at to-side |✔|❌|❌|✔||
192
-
|`q_to`|`RealValueOutput`| volt-ampere-reactive (var) | reactive power flowing into the branch at to-side |✔|❌|❌|✔||
193
-
|`i_to`|`RealValueOutput`| ampere (A) | current at to-side |✔|❌|❌|✔||
194
-
|`s_to`|`RealValueOutput`| volt-ampere (VA) | apparent power flowing at to-side |✔|❌|❌|✔||
195
-
|`loading`|`double`| - | relative loading of the line, `1.0` meaning 100% loaded. |✔|❌|❌|✔||
187
+
|`p_from`|`RealValueOutput`| watt (W) | active power flowing into the branch at from-side ||❌|❌|✔||
188
+
|`q_from`|`RealValueOutput`| volt-ampere-reactive (var) | reactive power flowing into the branch at from-side ||❌|❌|✔||
189
+
|`i_from`|`RealValueOutput`| ampere (A) | current at from-side ||❌|❌|✔||
190
+
|`s_from`|`RealValueOutput`| volt-ampere (VA) | apparent power flowing at from-side ||❌|❌|✔||
191
+
|`p_to`|`RealValueOutput`| watt (W) | active power flowing into the branch at to-side ||❌|❌|✔||
192
+
|`q_to`|`RealValueOutput`| volt-ampere-reactive (var) | reactive power flowing into the branch at to-side ||❌|❌|✔||
193
+
|`i_to`|`RealValueOutput`| ampere (A) | current at to-side ||❌|❌|✔||
194
+
|`s_to`|`RealValueOutput`| volt-ampere (VA) | apparent power flowing at to-side ||❌|❌|✔||
195
+
|`loading`|`double`| - | relative loading of the line, `1.0` meaning 100% loaded. ||❌|❌|✔||
196
196
197
197
198
198
### Line
@@ -249,7 +249,7 @@ In this case the winding voltage is decreased if the tap position is increased.*
249
249
|`tap_min`|`int8_t`| - | position of tap changer at minimum voltage |✔|✔|❌|❌||
250
250
|`tap_max`|`int8_t`| - | position of tap changer at maximum voltage |✔|✔|❌|❌||
251
251
|`tap_nom`|`int8_t`| - | nominal position of tap changer |❌ default zero |✔|❌|❌|`(tap_min <= tap_nom <= tap_max)` or `(tap_min >= tap_nom >= tap_max)`|
252
-
|`tap_size`|`double`| volt (V) | size of each tap of the tap changer |✔|✔|❌|❌|`> 0`|
252
+
|`tap_size`|`double`| volt (V) | size of each tap of the tap changer |✔|✔|❌|❌|`>= 0`|
253
253
|`uk_min`|`double`| - | relative short circuit voltage at minimum tap |❌ default same as `uk`|✔|❌|❌|`>= pk_min / sn` and `> 0` and `< 1`|
254
254
|`uk_max`|`double`| - | relative short circuit voltage at maximum tap |❌ default same as `uk`|✔|❌|❌|`>= pk_max / sn` and `> 0` and `< 1`|
255
255
|`pk_min`|`double`| watt (W) | short circuit (copper) loss at minimum tap |❌ default same as `pk`|✔|❌|❌|`>= 0`|
@@ -275,11 +275,11 @@ For each `appliance` a switch is defined between the `appliance` and the `node`.
|`u_measured`|`RealValueInput`| volt (V) | measured voltage magnitude |✨ only for state estimation |✔|✔|❌|`> 0`|
389
389
|`u_angle_measured`|`RealValueInput`| rad | measured voltage angle (only possible with phasor measurement units) |❌|✔|✔|❌||
390
-
|`u_residual`|`RealValueOutput`| volt (V) | residual value between measured voltage magnitude and calculated voltage magnitude |✔|❌|❌|✔||
391
-
|`u_angle_residual`|`RealValueOutput`| rad | residual value between measured voltage angle and calculated voltage angle (only possible with phasor measurement units) |❌|❌|❌|✔||
390
+
|`u_residual`|`RealValueOutput`| volt (V) | residual value between measured voltage magnitude and calculated voltage magnitude ||❌|❌|✔||
391
+
|`u_angle_residual`|`RealValueOutput`| rad | residual value between measured voltage angle and calculated voltage angle (only possible with phasor measurement units) ||❌|❌|✔||
392
392
393
393
394
394
### Generic Power Sensor
@@ -427,8 +427,8 @@ The table below shows a list of attributes.
|`p_measured`|`RealValueInput`| watt (W) | measured active power |✨ only for state estimation |✔|✔|❌|
429
429
|`q_measured`|`RealValueInput`| volt-ampere-reactive (var) | measured reactive power |✨ only for state estimation |✔|✔|❌|
430
-
|`p_residual`|`RealValueOutput`| watt (W) | residual value between measured active power and calculated active power |✔|❌|❌|✔|
431
-
|`q_residual`|`RealValueOutput`| volt-ampere-reactive (var) | residual value between measured reactive power and calculated reactive power |✔|❌|❌|✔|
430
+
|`p_residual`|`RealValueOutput`| watt (W) | residual value between measured active power and calculated active power ||❌|❌|✔|
431
+
|`q_residual`|`RealValueOutput`| volt-ampere-reactive (var) | residual value between measured reactive power and calculated reactive power ||❌|❌|✔|
432
432
433
433
434
434
# Selection of calculation method
@@ -462,4 +462,4 @@ Following are guidelines to be considered while selecting a state estimation `Ca
462
462
463
463
Every iteration of power-flow or state estimation has a step of solving large number of sparse linear equations i.e. `AX=b` in matrix form. Computation wise this is a very expensive step. One major component of this step is factorization of the `A` matrix. In certain calculation methods, this `A` matrix and its factorization remains unchanged over iterations and batches (only specific cases) which makes it possible reuse the factorization, skip this step and improve performance.
464
464
465
-
**Note:** Prefactorization over batches is possible when switching status or specified power values of load/generation or source reference voltage is modified. It is not possible when topology or grid parameters are modified, i.e. in switching of branches, shunt, sources or change in transformer tap positions.
465
+
**Note:** Prefactorization over batches is possible when switching status or specified power values of load/generation or source reference voltage is modified. It is not possible when topology or grid parameters are modified, i.e. in switching of branches, shunt, sources or change in transformer tap positions.
0 commit comments