Skip to content
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

FPS is dependent on hardware #4

Open
andreped opened this issue Oct 4, 2022 · 0 comments
Open

FPS is dependent on hardware #4

andreped opened this issue Oct 4, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@andreped
Copy link
Owner

andreped commented Oct 4, 2022

Currently, when using the pretrained RNN model with the app, the FPS is greatly dependent on how fast the accelerometer is streaming data. This means that if we are able to generate 50 samples in a second, and the AI only takes 50 samples, the AI will only use 1 second of history in the predictions.

This is of course suboptimal. Quite often models are also trained using a setup where data is streamed with a specific FPS. Hence, we should be able to cap the maximum FPS to a specified limit such that the AI is given sufficient history to solve the task.

This can be easily solved by adding a mechanism to only fetch data after a specific duration.

@andreped andreped added the bug Something isn't working label Oct 4, 2022
@andreped andreped added this to DSS Jan 27, 2023
@andreped andreped moved this to Todo in DSS Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Todo
Development

No branches or pull requests

1 participant