flexmeasures
flexmeasures copied to clipboard
The intelligent & developer-friendly EMS to support real-time energy flexibility apps, rapidly and scalable.
When showing sensor data for a selected asset, is can be useful to show context from other sensors. While it is already possible to show sensor data from public assets,...
## Description The command `flexmeasures show beliefs` adds the sensor ID in case of trying to export sensors with the same name. However, if we want to hand this over...
## Description Inputting a 'p' or an 's' while editing an attribute or filtering a listing on the asset page shouldn't trigger replay functionality. ## How to test Go to...
## Description Support start_time and end_time query parameters for *GET /assets/\* call ## Look & Feel . ## How to test Pass new parameters to *GET /assets/\*, check we get...
## Description Running against the simulation DB with 196 Assets and 59 users, the existing code takes about 134s to load the asset page. With the changes introduced in this...
## Description This PR introduces `create_soc_schedule`, a function to generate a state of charge (SOC) schedule from provided data. It also handles the creation or retrieval of the corresponding SOC...
## Description 1. Split status by data source 2. Change staleness calculation for Forecaster / Scheduler sources (staleness should be calculated as difference between now and max event start time)...
## Description `QuantityOrSensor("/MWh")` can now be used for energy price fields. Any unit is accepted as a numerator: this includes currencies, such as EUR/MWh, USD/MWh and AUD/MWh, but also kg/MWh...
The use case I have for this is to support a control policy to charge immediately, or actually rather, as soon as possible, while still taking into account other constraints...