mirror of
https://github.com/Akkudoktor-EOS/EOS.git
synced 2026-08-31 12:46:38 +00:00
docs: describe feed-in tariff forecast
This commit is contained in:
@@ -40,6 +40,10 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
|
|||||||
- Model direct PV-to-load consumption probabilistically from the bundled conditional minute-load
|
- Model direct PV-to-load consumption probabilistically from the bundled conditional minute-load
|
||||||
table. The expected direct flow is used consistently for PV bypass, residual load, battery
|
table. The expected direct flow is used consistently for PV bypass, residual load, battery
|
||||||
charging, and grid export on hourly and 15-minute optimization grids.
|
charging, and grid export on hourly and 15-minute optimization grids.
|
||||||
|
- Add a dynamic `FeedInTariffEnergyCharts` forecast for direct marketing. Published Energy-Charts
|
||||||
|
day-ahead market prices are retained at their native hourly or quarter-hourly resolution and
|
||||||
|
missing slots at the end of the optimization horizon are extended with weekly or daily seasonal
|
||||||
|
ETS forecasts. A median fallback is used when the available history is too short for ETS.
|
||||||
|
|
||||||
## 0.3.0 (2026-03-17)
|
## 0.3.0 (2026-03-17)
|
||||||
|
|
||||||
|
|||||||
@@ -233,7 +233,8 @@ Configuration options:
|
|||||||
|
|
||||||
The `FeedInTariffEnergyCharts` provider uses the raw Energy-Charts day-ahead market price as the
|
The `FeedInTariffEnergyCharts` provider uses the raw Energy-Charts day-ahead market price as the
|
||||||
feed-in tariff. It stores prices in `feed_in_tariff_wh` without adding electricity import charges
|
feed-in tariff. It stores prices in `feed_in_tariff_wh` without adding electricity import charges
|
||||||
or VAT. The native Energy-Charts resolution, including quarter-hour data, is retained.
|
or VAT. The data is loaded from the Energy-Charts `/price` endpoint for the configured bidding
|
||||||
|
zone. The native Energy-Charts resolution, including quarter-hour data, is retained.
|
||||||
|
|
||||||
Energy-Charts usually supplies prices only for the published day-ahead period. If that data does
|
Energy-Charts usually supplies prices only for the published day-ahead period. If that data does
|
||||||
not cover the complete configured prediction horizon, the provider extends it as follows:
|
not cover the complete configured prediction horizon, the provider extends it as follows:
|
||||||
@@ -245,13 +246,20 @@ not cover the complete configured prediction horizon, the provider extends it as
|
|||||||
|
|
||||||
The seasonal periods are adjusted to the source resolution. For example, quarter-hour data uses
|
The seasonal periods are adjusted to the source resolution. For example, quarter-hour data uses
|
||||||
four values per hour. Values already supplied by Energy-Charts are kept unchanged; only missing
|
four values per hour. Values already supplied by Energy-Charts are kept unchanged; only missing
|
||||||
future slots after the last published price are forecast.
|
future slots after the last published price are forecast. Consequently, a 15-minute optimization
|
||||||
|
uses four forecast values per hour without converting them to hourly averages.
|
||||||
|
|
||||||
|
When direct marketing is enabled, this feed-in-tariff series is passed to the optimizer separately
|
||||||
|
from the electricity purchase-price series. The successful Energy-Charts path therefore does not
|
||||||
|
derive the feed-in tariff by subtracting taxes, grid fees, or other charges from an end-customer
|
||||||
|
electricity price.
|
||||||
|
|
||||||
Example configuration:
|
Example configuration:
|
||||||
|
|
||||||
```json
|
```json
|
||||||
{
|
{
|
||||||
"feedintariff": {
|
"feedintariff": {
|
||||||
|
"direct_marketing_enabled": true,
|
||||||
"provider": "FeedInTariffEnergyCharts",
|
"provider": "FeedInTariffEnergyCharts",
|
||||||
"provider_settings": {
|
"provider_settings": {
|
||||||
"FeedInTariffEnergyCharts": {
|
"FeedInTariffEnergyCharts": {
|
||||||
|
|||||||
Reference in New Issue
Block a user