Question about Depth information when using IntelRealsense about ros_openpose HOT 7 CLOSED

I ran your latest code and there was no errors!! Thank you for fixing the bugs !!

from ros_openpose.

Hi @Shunichi09

Thanks for the confirmation. I am closing this issue now. Feel free to report issues if you find any!

from ros_openpose.

Hi @Shunichi09

Thank you very much. I am glad you could follow the instructions and made it work.

(the value only has 1.0 or 2.0 or 3.0 or 4.0 or 5.0)
It's supposed to have float values like 1.1.

This is surprising. Last time, I checked everything was working fine. I doubt maybe the values you are seeing are just a coincidence? Did you check it many times with multiple frames? Furthermore, if the RVIZ visualization is working fine, then there should not be any problem.

Now back to your query, the values are represented in SI units inside the frame topic. Therefore, if the depth values are in millimeters, a conversion from millimeter to the meter is required. This conversation is done based on the image encoding and can be seen here.

Let me know if the issue persists. I will check once again at my side.

from ros_openpose.

Thank you for your reply.
In my case the RVIZ visualization worked fine, but the depth information only took int values like 1.0, 2.0...
It means that the human bone which was drawn by green line in RVIZ moved not smoothly.
(only Z position, X and Y position worked fine!!)

Did you check it many times with multiple frames?

Yes, I did...

Now back to your query, the values are represented in SI units inside the frame topic. Therefore, if the depth values are in millimeters, a conversion from millimeter to the meter is required. This conversation is done based on the image encoding and can be seen here.

I'm using D435i of IntelRealSense so I think depth values are in millimeters.
Does it mean your code should work fine ??

from ros_openpose.

Hello @Shunichi09

I checked the code and found the same issue. It is a bug introduced in the recent commit. Therefore, can you please use an old commit as shown below-

git checkout 583d09dfb82a3a393190825920ffa644255ff099

Meanwhile, I am working on the bug! Stay tuned.

from ros_openpose.

@ravijo Thank you for your support!!
Ok, I will use the old version of your repository. I'm looking forward to your updating.
Again, Thank you very much.

from ros_openpose.

Hello @Shunichi09

Can you please pull the latest changes from the repository and check if the problem is solved?

Thanks

from ros_openpose.