Description:
We want to make forecast output post-processing configurable from the forecaster config.
Currently, we already support an existing parameter to ensure non-negative forecast values. We should keep backwards compatibility for that parameter, but add a more generic configuration for clipping and snapping forecasted values before they are stored.
Proposed config example:
{
"config": {
"lower": "0 kW",
"snap": {
"8 kW": ["8 kW", "11 kW"],
"12 kW": ["11 kW", "12 kW"]
},
"upper": "20 kW"
}
}Expected behavior:
Values below lower are clipped to lower.
Values above upper are clipped to upper.
Values inside a configured snap interval are replaced by the snap target.
Units are optional. If no unit is provided, values are interpreted in the output sensor unit.
Existing non-negative behavior should keep working for backwards compatibility.
Example:
"snap": {
"0 kW": ["0 kW", "4 kW"]
}
This would snap values between 0 kW and 4 kW to 0 kW.
Description:
We want to make forecast output post-processing configurable from the forecaster config.
Currently, we already support an existing parameter to ensure non-negative forecast values. We should keep backwards compatibility for that parameter, but add a more generic configuration for clipping and snapping forecasted values before they are stored.
Proposed config example:
{ "config": { "lower": "0 kW", "snap": { "8 kW": ["8 kW", "11 kW"], "12 kW": ["11 kW", "12 kW"] }, "upper": "20 kW" } }Expected behavior:
Values below lower are clipped to lower.
Values above upper are clipped to upper.
Values inside a configured snap interval are replaced by the snap target.
Units are optional. If no unit is provided, values are interpreted in the output sensor unit.
Existing non-negative behavior should keep working for backwards compatibility.
Example:
"snap": {
"0 kW": ["0 kW", "4 kW"]
}
This would snap values between 0 kW and 4 kW to 0 kW.