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
Fix succeeded_power calculation in PV power distribution (#1217)
This was reported incorrectly earlier using a variable that was never
set. That variable and related (unused) channels have been removed.
This also updates the PV pool tests to ensure that the distribution
results are accurate.
Copy file name to clipboardExpand all lines: RELEASE_NOTES.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@
47
47
48
48
## Bug Fixes
49
49
50
-
- Components used to be just forgotten by the power manager when all proposals are withdrawn, leaving them at their last set power values. This has been fixed by getting the power manager to set the components to their default powers, based on the component category (according to the table below), as the last step.
50
+
- The power manager used to just forgot components when all proposals to them are withdrawn, leaving them at their last set power values. This has been fixed by getting the power manager to set the components to their default powers, based on the component category (according to the table below), as the last step.
51
51
52
52
53
53
| component category | default power |
@@ -58,4 +58,6 @@
58
58
59
59
- PV Pool instances can now be created in sites without any PV. This allows for writing generic code that works for all locations, that depends on the PV power formula, for example.
60
60
61
+
- `Success/PartialFailure` results from `PVPool.power_distribution_results` now report correct `succeeded_power` values.
62
+
61
63
- The `find_first_descendant_component` method in the component graph was allowing non-root components to be used as the root component during traversal. This was leading to confusing behaviour when the root component couldn't be identified deterministically. For example, if the root category was specified as a meter, it could start traversing from a different meter each time. It is no-longer possible to specify a root category anymore and it always traverses from the `GRID` component.
Copy file name to clipboardExpand all lines: src/frequenz/sdk/microgrid/_power_distributing/_component_managers/_pv_inverter_manager/_pv_inverter_manager.py
0 commit comments