Support showing instantaneous sensor data with a custom event frequency#542
Merged
Support showing instantaneous sensor data with a custom event frequency#542
Conversation
Signed-off-by: F.N. Claessen <felix@seita.nl>
Collaborator
Pull Request Test Coverage Report for Build 3674188427
💛 - Coveralls |
…e up with default for instantaneous sensors Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
…ent frequency Signed-off-by: F.N. Claessen <felix@seita.nl>
…e None value Signed-off-by: F.N. Claessen <felix@seita.nl>
…or UDI events Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
…stantaneous sensors Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
…rsion) Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
…sample-instantaneous-sensor-data # Conflicts: # flexmeasures/api/common/schemas/sensor_data.py
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Base automatically changed from
398-support-optional-source-in-sensorsdata-get
to
main
December 2, 2022 10:32
Signed-off-by: F.N. Claessen <felix@seita.nl> # Conflicts: # flexmeasures/api/common/schemas/sensor_data.py # flexmeasures/api/v3_0/sensors.py # flexmeasures/api/v3_0/tests/conftest.py # flexmeasures/api/v3_0/tests/test_sensor_data_fresh_db.py
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
nhoening
approved these changes
Dec 9, 2022
Signed-off-by: F.N. Claessen <felix@seita.nl>
# Conflicts: # documentation/changelog.rst # requirements/app.in # requirements/app.txt
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrade timely-beliefs to expose new resampling functionality for instantaneous sensor data:
flexmeasures show beliefscan now handle showing (and saving) instantaneous sensor data and non-instaneous sensor data together./sensors/datanow allows fetching instantaneous sensor data in a custom frequency, by using the "resolution" field. I've chosen to not (yet) expose a "frequency" field to the user API, but to keep only the "resolution" field. The resolution of the fetched data is now explicitly part of the return message, while the frequency is still implicit (i.e. the length of the data divided by the duration).