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

putIterationsPerSec before added to Buffer #87

Open
martinpflaum opened this issue May 25, 2020 · 1 comment
Open

putIterationsPerSec before added to Buffer #87

martinpflaum opened this issue May 25, 2020 · 1 comment

Comments

@martinpflaum
Copy link

martinpflaum commented May 25, 2020

Hi i am really a beginner so i am not sure if i got this right,
but inn line 136 of fps_dem_trn.py putIterationsPerSec is called which will draw the class label on this image. But the same image is also used to predict the labels later on because it is put into the buffer. Why not switch line 140 and 136 and then instead of calling crop_img = frame[0:720, 0:720] do crop_img = frame.copy(). Also line 144 will be needed to be changed to cv2.imshow("Frame", frame). And thanks for the great repo its really cool to see the model working in realtime.

Regards Martin

@martinpflaum
Copy link
Author

martinpflaum commented May 25, 2020

Its also a bit strange that there is no regulation in which frequence the frames are put into the buffer. so accuracy changes depending on how fast or slow the pc is. Does the framerate on which the model was trained differ a lot from 12 fps (Jester Dataset)?
regards martin

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

1 participant