None of keypoints detected from my own data about ros_openpose HOT 4 CLOSED

@akamob

Thanks for opening this issue. It is quite interesting at first. Because at the backend, the same OpenPose is used in both cases.. Basically, the OpenPose when used with this package is detecting 0 people. The image quality is poor but the python binding of OpenPose is detecting 1 person.

I suggest you do a little more debugging to find the actual cause of this confusing behavior.

1. Please use the video (mp4) file on the complied OpenPose to see if Openpose detects anything. Please refer to Quick Start Overview

./build/examples/openpose/openpose.bin --video examples/media/video.avi \
--face --hand --write_json output_json_folder/

2. We have seen the python bindings are working fine, can you please use the python bindings with this package by enabling synchronous mode as mentioned in Implementation Versions Info.

roslaunch ros_openpose run.launch camera:=nodepth synchronous:=true \
py_openpose_path:=absolute_path_to_py_openpose

3. Can you please confirm that the test image for 01_body_from_image.py is taken from the recorded video (and has exactly the same resolution as the video)?
4. Can you please confirm that you have added "--net_resolution -1x128" to your 01_body_from_image.py file?

from ros_openpose.

Hi, @ravijo, thank you very much for your reply:)

I forgot to mention I build OpenPose in cpu_only mode due to the limited computational power. And the following are my test results:

1. I test my video file on OpenPose and it can detect some keypoints. Although the skeleton is incomplete and sometimes OpenPose still detect 0 people.
   

2. I'm not sure if I'm doing it right, py_openpose_path means to access the absolute path shown in the following picture?
   
   I run this command:
   roslaunch ros_openpose run.launch camera:=nodepth synchronous:=true \ py_openpose_path:=/home/lk3696/yi_ros_openpose/src/openpose/build/python/openpose/

And I got the warn:

[ WARN] [1646801737.361694890]: Shutdown request received.
[ WARN] [1646801737.361725319]: Reason given for shutdown: [[/rosOpenpose] Reason: new node registered with same name]
rosOpenposeSync: /usr/include/boost/smart_ptr/shared_ptr.hpp:734: typename boost::detail::sp_member_access<T>::type boost::shared_ptr<T>::operator->() const [with T = const sensor_msgs::CameraInfo_<std::allocator<void> >; typename boost::detail::sp_member_access<T>::type = const sensor_msgs::CameraInfo_<std::allocator<void> >*]: Assertion `px != 0' failed.
shutdown request: [/echo] Reason: new node registered with same name

3. Yes, my test image come from the recorded video and they have same resolution.
   

4. I'm not add --net_resolution -1x128 in 01_body_from_image.py file.
   

from ros_openpose.

@akamob

Seeing your screenshot, I am quite sure that the images you are getting are of poor quality. Because OpenPose can detect it SOMETIMES ONLY.

You can either (a) try to improve the image quality, or (b) play with the OpenPose configurations such as net_resolution etc. Basically, we do not want to resize down images in this scenario.

Please let me know your progress in this specific case.

from ros_openpose.

Closing this issue as no further comments were received. Feel free to comment if the issue still exists.

from ros_openpose.