-
Notifications
You must be signed in to change notification settings - Fork 66
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
Frame rate too low #123
Comments
Right now this is the expected performance for OpenPose. We are looking at acceleration options and incorporating newer vision of the libraries to see if we can improve performance. Just out of curiosity, what’s the CPU utilization?
From: Manuel Mueller <notifications@github.com>
Reply-To: OpenPTrack/open_ptrack_v2 <reply@reply.github.com>
Date: Friday, February 14, 2020 at 9:09 AM
To: OpenPTrack/open_ptrack_v2 <open_ptrack_v2@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [OpenPTrack/open_ptrack_v2] Frame rate too low (#123)
Hello,
I just realized that my sampling rate with which I receive pose tracking data is too low. Right now its around 10-13 Hz.
Currently I am using single-camera pose tracking. My system got a NVIDIA Quadro P600, so I guess the GPU should not be the problem.
I already checked the publishing rate at ~/open_ptrack_docker_config/single_camera_tracking/open_ptrack_config/tracking/conf/moving_average_filter.yaml , which is set to 30.
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.130 Driver Version: 384.130 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Quadro P6000 Off | 00000000:21:00.0 On | Off |
| 44% 75C P0 119W / 250W | 2473MiB / 24435MiB | 88% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1332 G /usr/lib/xorg/Xorg 423MiB |
| 0 3315 G compiz 137MiB |
| 0 12332 G /usr/lib/firefox/firefox 3MiB |
| 0 13233 C /opt/ros/kinetic/lib/nodelet/nodelet 555MiB |
| 0 13922 G /opt/ros/kinetic/lib/rviz/rviz 73MiB |
| 0 14352 C ...ace/ros/devel/lib/rtpose_wrapper/rtpose 1275MiB |
+-----------------------------------------------------------------------------+
How can I fix this?
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#123?email_source=notifications&email_token=AADFGR24YNCENILHIO65YMDRC3F3DA5CNFSM4KVMFWGKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4INUDSAA>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADFGR5LWEIYC5LJNMRMFSDRC3F3DANCNFSM4KVMFWGA>.
|
Okay, so I cannot get higher frame rates right now, even if I find a way to accelerate my GPU?
What do you guess, when will you be able to update OpenPTrack v2 with a newer version of OpenPose (months, years, ...)? I will check the CPU utilization tomorrow. Thank you! |
Correct, OPTv1 only included person tracking, which is what the quote refers to. We have no definitive plans for updating to the newest OpenPose, but it is being tracked in open issue #48 |
Okay, thank you for your answer and your effort! |
Person tracking and object tracking in version 2 will also function at 30fps. It's just pose that doesn't
…________________________________
From: Manuel Mueller <notifications@github.com>
Sent: Sunday, February 16, 2020 4:22:56 PM
To: OpenPTrack/open_ptrack_v2 <open_ptrack_v2@noreply.github.com>
Cc: Burke, Jeff <jburke@remap.ucla.edu>; Comment <comment@noreply.github.com>
Subject: Re: [OpenPTrack/open_ptrack_v2] Frame rate too low (#123)
Okay, thank you for your answer and your effort!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#123?email_source=notifications&email_token=AADFGR6PS7F76ODI5EAK5B3RDGHBBA5CNFSM4KVMFWGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4PXKY#issuecomment-586742699>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADFGRYHMILBCP2OCPRLJQTRDGHBBANCNFSM4KVMFWGA>.
|
Hello,
I just realized that my sampling rate with which I receive pose tracking data is too low. Right now its around 10-13 Hz.
Currently I am using single-camera pose tracking. My system got a NVIDIA Quadro P600, so I guess the GPU should not be the problem.
I already checked the publishing rate at ~/open_ptrack_docker_config/single_camera_tracking/open_ptrack_config/tracking/conf/moving_average_filter.yaml , which is set to 30.
How can I fix this?
Thank you!
The text was updated successfully, but these errors were encountered: