-
Notifications
You must be signed in to change notification settings - Fork 15
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
Difference in "run-yarppg qt6" and default settings #26
Comments
Hi, If you know the FPS, you can convert between the two with HR_bpm = 60 * fps / HR_fpb. I should probably mention this in the docs. Or I can think about adding FPS tracking to the simplest UI as well. |
Although, since the simplest UI is not really optimized and does frame retrieval, processing and visualization sequentially (qt6_simple partly does this in separate threads) tracking FPS through a clock might not be so easy. Edit: although thinking about it. Tracking the FPS with the perf_counter should be more accurate than using the FPS of the camera - since processing time may reduce the actual FPS. |
Thank you very much :) |
I just updated the simplest UI to track FPS and show HR in bpm. This streamlines the interpretation of both user interfaces. |
Hello, tell me please, whats the difference between default and "run-yarppg qt6" settings?
I have 2 different results. When i execute "run-yarppg with qt6", i get more accurate and correct results (HR ~70, close to fitness watch) than when I run my program with default settings (HR ~22)
What could this be related to?
The text was updated successfully, but these errors were encountered: