New users (and maybe also existing ones) can get started more quickly when example assets exist. This issue proposed to add three commonly-used ones, which should exist in the public space (now owner account).
We should create:
- a simple market
- a solar & battery combination
- a heat pump & buffer.
The latter two reference the market as consumption-price.
For these new public assets, they should be created when we run flexmeasures add initial-structure.
I still need to figure out how to make it as easy as possible to generate some initial data. I.e. each asset requires one or more datasets so one can actually do something.
Where in FlexMeasures could that be? We could generate data when the asset is being copied, but there is no UX or business logic design idea for this yet.
For example, an asset can have a JSON attribute describing how to create data once the asset is being created / copied. Maybe downloading small data sets from github, and moving the dates to tomorrow.
I also would like for the UX (see also other issue in this story) to empower the user to opt-in for this (e.g. a checkbox for "create toy data set").
New users (and maybe also existing ones) can get started more quickly when example assets exist. This issue proposed to add three commonly-used ones, which should exist in the public space (now owner account).
We should create:
The latter two reference the market as consumption-price.
For these new public assets, they should be created when we run
flexmeasures add initial-structure.I still need to figure out how to make it as easy as possible to generate some initial data. I.e. each asset requires one or more datasets so one can actually do something.
Where in FlexMeasures could that be? We could generate data when the asset is being copied, but there is no UX or business logic design idea for this yet.
For example, an asset can have a JSON attribute describing how to create data once the asset is being created / copied. Maybe downloading small data sets from github, and moving the dates to tomorrow.
I also would like for the UX (see also other issue in this story) to empower the user to opt-in for this (e.g. a checkbox for "create toy data set").