Nicolas Höning
Nicolas Höning
Scheduling is the first operation we should start to rate-limit, as it is most expensive. Foremost, this protects against bad/rogue client implementations. My suggestion (taking into account the state before...
That part still uses Bokeh, but we should switch it to our Altair support. We should also remove the [GET /api/v2_0/charts/power](https://flexmeasures.readthedocs.io/en/latest/api/v2_0.html#get--api-v2_0-charts-power) endpoint. Or replace it with an Altair chart-based one.
We deliver some scheduling algorithms out-of-the-box, with the core FlexMeasures code. Currently, this includes batteries and EV charging stations. But certainly some algorithms will be more elaborate, more specific or...
Right now, the scheduler assumes that the sensor capacity is given in MW. It should become more versatile, e.g. for kW. Now that we have better support for a lot...
[Annotations](https://github.com/FlexMeasures/flexmeasures/blob/main/flexmeasures/data/models/annotations.py) are simple notes with metadata about our time series data, and they can be attached to sensors, assets and accounts. Their value lies in enriching the IoT data ―...
The sensor API misses the basic endpoints to be able to do CRUD. The /dev/sensor API should also move to API v3.
Recently, the CSS started using variables for colors. Mainly, we use a primary and a secondary color. The idea of this ticket is that it is possible to edit an...
In `ui.static.js.flexmeasures.js`, we have lots of code about the general behavior of the FlexMeasures UI. We also have specific code, e.g. for the control page (lines 212 to 287 as...
We have the `flexmeasures edit attribute` CLI command. It allows to edit attribute values of several types on assets and sensors: float, bool, str, int. (attributes are where we store...
When the endpoints from #433 exist, we can add these abilities to the sensor page, and also allow users to add sensors from the asset page. We could copy the...