-
Notifications
You must be signed in to change notification settings - Fork 22
adds CSV provider #77
adds CSV provider #77
Conversation
Not really something, that needs to be added here, just an idea: a helper script creating these .csv from a "life" system is probably easy to do: Give it a list of VSS paths, and it can depending on metadata, subscribe current value for sensors and current&target value for actuators while writing a CSV file. (Don't forget to flush on Ctrl-C :) ). But just an idea for the future |
d632cf5
to
ddd02ce
Compare
I updated the branch for the CSV-provider, @erikbosch and @SebastianSchildt could you please have another look. The idea of having a script to generate the CSV-files from a life system is good. To me this is beyond the scope of this PR but I will have look into it for a further PR. |
23fb3af
to
97212c5
Compare
97212c5
to
4611c76
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some minor comment regarding documentation. Decide for yourself if you want to rephrase or not.
This PR adds a provider which reads VSS signals from a given CSV-file and replays this data and the changes over time to an instance of the kuksa.val databroker.