flexmeasures
flexmeasures copied to clipboard
The intelligent & developer-friendly EMS to support real-time energy flexibility apps, rapidly and scalable.
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 ―...
Closes #436 - [x] Add replay button to sensor page - [x] Add replay button to asset page - [x] Get chart data including older beliefs - [x] Loop through...
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...
The function [get_sensor_by_generic_asset_type_and_location(https://github.com/FlexMeasures/flexmeasures/blob/main/flexmeasures/api/common/utils/api_utils.py#L291) finds assets by exact location, comparing floats. > I believe it's not good practice to compare floats for equality. See [here](https://www.peterbe.com/plog/comparing-real-values) for instance. Not only Postgres, also...
As pointed out in PR https://github.com/SeitaBV/flexmeasures/pull/223, we need to add tests for our sensor views (see `ui.views.sensors.SensorUI`), for example, in a new `test_sensor_crud.py`. This may require mock API responses, 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...
Add an optional duration parameter to the schema, instead of always falling back to `FLEXMEASURES_PLANNING_HORIZON`.