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

Frame rate too low #123

Open
muella91 opened this issue Feb 14, 2020 · 5 comments
Open

Frame rate too low #123

muella91 opened this issue Feb 14, 2020 · 5 comments

Comments

@muella91
Copy link

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!

@jburkeucla
Copy link
Contributor

jburkeucla commented Feb 14, 2020 via email

@mnemllr
Copy link

mnemllr commented Feb 16, 2020

Okay, so I cannot get higher frame rates right now, even if I find a way to accelerate my GPU?
The 30 FPS of OpenPTrack v1 is only valid for person track I guess?

This tracking data is delivered at 30 frames per second as a simple JSON-formatted stream via UDP, which can be incorporated easily into creative coding tools, such as Max/MSP, Touchdesigner, and Processing.

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!

@bsubbaraman
Copy link
Contributor

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

@mnemllr
Copy link

mnemllr commented Feb 16, 2020

Okay, thank you for your answer and your effort!

@jburkeucla
Copy link
Contributor

jburkeucla commented Feb 16, 2020 via email

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

4 participants