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

It is not accurate #40

Open
Zumbalamambo opened this issue Sep 10, 2017 · 8 comments
Open

It is not accurate #40

Zumbalamambo opened this issue Sep 10, 2017 · 8 comments

Comments

@Zumbalamambo
Copy link

If I move my face outside the screen, it is still showing bpm values from nowhere

@PandaWhoCodes
Copy link

The data shown is not real-time. It has a certain delay. Try moving out of the screen for more than 40 seconds - 1 minute

@Zumbalamambo
Copy link
Author

Is there any ways to make it realtime?

@Zumbalamambo
Copy link
Author

even after moving out for 1 minute, it is still recognizing...

@bcba25
Copy link

bcba25 commented Jul 4, 2019

++ same issue here. Would be nice to hear authors comments on this.

@Zumbalamambo
Copy link
Author

@hxdef2517 rewriting the evaluation function and the filter, I have managed to make it accurate. Threading does the magic of making it real-time. Now that it works accurate as well as real-time.

@prudhvirapeti
Copy link

@Zumbalamambo please let me know how did you rewrite the evaluation function and filter,it would be
helpful if you can mail me
->[email protected]

@SijinJohn
Copy link

@Zumbalamambo how did you make it .

@allComputableThings
Copy link

I also see accuracy issues. Even with house lights turned off, the signal seems to consistently hover around 60Hz, when I'm seeing 70-100 on a finger pulse oximeter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants