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
This PR adds configurable resampling behavior to the logical meter,
allowing callers to change the default resampling function and override
it per metric or per (component_id, metric) pair.
**Changes:**
- Add `LogicalMeterConfig` builder-style API for default resampling
function and per-metric/per-component overrides.
- Update `LogicalMeterActor` to select the resampling function using
override precedence (component-specific → metric-only → default →
average).
- Update examples/tests and bump `frequenz-resampling` dependency to
`0.2`.
Copy file name to clipboardExpand all lines: RELEASE_NOTES.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,16 +2,16 @@
2
2
3
3
## Summary
4
4
5
-
This release makes incremental improvements to the client and the quantity types.
5
+
<!-- Here goes a general summary of what this release is about -->
6
6
7
7
## Upgrading
8
8
9
-
-The `MicrogridClientHandle::list_electrical_components` method now expects `ElectricalComponentCategory` enum values instead of `i32`, to filter by component category.
9
+
-`LogicalMeterConfig` instances can't be created directly anymore, and need to be created using the `LogicalMeterConfig::new` method. This helps avoid future breaking changes, as we add more config parameters.
10
10
11
11
## New Features
12
12
13
-
-The new `MicrogridClientHandle::augment_electrical_component_bounds` method can be used to augment the bounds for specific metrics of electrical components.
13
+
-It is now possible to change the default resampling function, and to override the resampling function for specific metrics.
14
14
15
-
- All methods on `Quantity` types are now `const`.
15
+
## Bug Fixes
16
16
17
-
-`Quantity` types have two new methods `min` and `max`, similar to the `min` and `max` methods on fundamental numerical types.
17
+
<!-- Here goes notable bug fixes that are worth a special mention or explanation -->
0 commit comments