ESP
ESP copied to clipboard
The Example-based Sensor Predictions (ESP) system applies machine learning to real-time sensor data.
That is, a way to prevent the system from sending the same prediction to output streams over and over. Probably a reversion to class 0 (null class) and then a...
Should this be added to the existing output stream or a separate stream (e.g. TCP connection to a different port)? Could also be good to allow streaming of data at...
Not just the predictions themselves. Similar to #340, should this be an addition to existing streams? A new stream?
More generally, we should be able to run in headless mode without depending on openFrameworks at all. This would be a first step towards separating the runtime from the GUI...
Thinking about it more, it seems likely that we're going to need more sophisticated event / focus handling for the GUI to work properly. For instance, we probably want a...
That is, we should probably have ESP directly in an "ESP" directory in the root of this repository. It seems silly have an Xcode directory with only one thing in...
How much support is there for custom plots / visualizations? Does the ESP interface still need to be compiled against the ESP example? How hard is it for others users...
This would allow us to write the GUI in whatever framework we wanted (browser-based might be good), while retaining flexibility in the choice of machine learning framework. It would require...
Currently, they're only shown for samples recorded by pressing '1' to '9'.