Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mix in Sensor from Timely Beliefs #12

Closed
Flix6x opened this issue Feb 1, 2021 · 1 comment · Fixed by #13
Closed

Mix in Sensor from Timely Beliefs #12

Flix6x opened this issue Feb 1, 2021 · 1 comment · Fixed by #13

Comments

@Flix6x
Copy link
Contributor

Flix6x commented Feb 1, 2021

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.

@Flix6x Flix6x added the Data label Feb 1, 2021
@Flix6x Flix6x added this to the Data model based on timely beliefs milestone Feb 1, 2021
@Flix6x Flix6x self-assigned this Feb 1, 2021
@create-issue-branch
Copy link
Contributor

Branch issue-12-Mix_in_Sensor_from_Timely_Beliefs created!

@Flix6x Flix6x linked a pull request Feb 1, 2021 that will close this issue
@Flix6x Flix6x added this to To do in Data model based on timely beliefs via automation Oct 25, 2021
@Flix6x Flix6x moved this from To do to Done in Data model based on timely beliefs Oct 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant