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
We want to base fm.Asset, fm.Market and fm.WeatherSensor on tb.SensorDBMixin, as a prerequisite to base our fm.TimedValue time series values on tb.TimedBelief, but also to take immediate advantage of the concept of knowledge horizons (and knowledge times) built into Timely Beliefs.
The concept of knowledge horizons allows us to standardize the notion of a forecast horizon for power measurements and prices. Power and price forecasts are distinct in terms of when their true values could have been known. Power values can be known after the deliver period (when power flow has been measured), while prices can be known well in advance of the delivery period to which the price pertains (for example, at the gate closure of some call auction, or on the publication date of some tariff).
I propose to:
set the knowledge time for tariffs to their publication date
set the knowledge time for auctions to their gate closure
set the knowledge time for power and weather sensors to right after the fact
We can then ensure that the forecast horizon is interpreted as relative to the knowledge time, the time at which the true outcome could have been known. At least two todo items (specifically, in data/queries/utils.py and api/common/utils/validators.py) are linked to this issue, and the horizon of existing auction prices and tariffs in the database may have to be updated to reflect the change in anchoring the horizon to their relevant knowledge time rather than to their event end.
The text was updated successfully, but these errors were encountered:
We want to base
fm.Asset
,fm.Market
andfm.WeatherSensor
ontb.SensorDBMixin
, as a prerequisite to base ourfm.TimedValue
time series values ontb.TimedBelief
, but also to take immediate advantage of the concept of knowledge horizons (and knowledge times) built into Timely Beliefs.The concept of knowledge horizons allows us to standardize the notion of a forecast horizon for power measurements and prices. Power and price forecasts are distinct in terms of when their true values could have been known. Power values can be known after the deliver period (when power flow has been measured), while prices can be known well in advance of the delivery period to which the price pertains (for example, at the gate closure of some call auction, or on the publication date of some tariff).
I propose to:
We can then ensure that the forecast horizon is interpreted as relative to the knowledge time, the time at which the true outcome could have been known. At least two todo items (specifically, in
data/queries/utils.py
andapi/common/utils/validators.py
) are linked to this issue, and the horizon of existing auction prices and tariffs in the database may have to be updated to reflect the change in anchoring the horizon to their relevant knowledge time rather than to their event end.The text was updated successfully, but these errors were encountered: