-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SeeDot: Example Arduino code always predict label '9' #130
Comments
The documentation on using the Arduino sketch is present here: I will highlight some of the things relevant to this issue. By default, the Arduino prediction code runs only on a single data point since the entire data set cannot fit on the device. This behavior is used to compute the total prediction time of the generated code. There is one more mode called the accuracy mode, where the entire dataset is streamed to the device using serial communication. In this setting, the generated code sequentially runs on each entry in the data set. This mode is useful to compute the accuracy of the generated code. Since you are running the prediction time mode (default mode), the generated code is being run on only a single data point. Hope this description helps. Regards, |
Oh, of course, that makes total sense. Thank you very much :-) I'm closing the issue because of your good response. |
I have modified
Is there something else I must do? Nothing is happening in the serial because of If I send |
In the accuracy mode, you need to send each data point to the device using serial communication. There is a master, typically a desktop machine, that has access to the data set and is responsible for sending each data point to the client, the Arduino device. The first step in the Arduino code is to sync with the master. After that, each data point is sent as a stream of bytes. The You would need to write code for the master to make this work. |
Ok, that was the answer I was looking for – I will try to make it work. |
When going through the Arduino/ProtoNN tutorial and running it on the device it seems to always predict label '9'.
Is this a sign of a correctly functioning example? Am I missing something?
The text was updated successfully, but these errors were encountered: