Yes, that’s exactly the idea. This optimizer can already now be used with any price and weather forecast provider, given that the data is found as a proper timeseries.
I would really want to deprecate and remove the EntsoE price fetching and the FMI weather forecast fetching from this package since they are completely separate topics. This optimizer simply needs the price and weather forecast timeseries but it doesn’t mean that those architecturally belong to this package.
I am aware that there is at least one weather forecast binding available which saves the data as timeseries. But the FMI weather forecast data this solution fetches is curated by a real human meteorologist i.e. it’s much more accurate than alternative data sources which are only providing data from one weather model. So if somebody is interested to update FMI Weather binding so that it
a) uses the fmi::forecast::edited::weather::scandinavia::point::simple data provider by FMI meteorologist instead of using the Harmonie weather model
b) saves the data as a proper timeseries
… then we would be able to use that binding instead of maintaining it here in parallel.
Markus