Live 3D module: zeroes or NaNs?

[AdeV-Oly]

Hey guys,

I've been working with the 3D (live) reconstruction module for a while now and was left with a question. Let me break it down:

• Looking back at the data, the data is partially filled with zeroes; I guess for keypoints that weren't detected by OpenPose;
• i.e., for keypoints not detected, the origin is given as the value (which is physically not possible in the universe as we know it :p).
• However, I don't remember seeing any dots or anything else 'popping-up' anywhere during the 3D reconstruction; a segment/limb would just disappear;
• i.e. that left me to believe that OpenPose would just return 'NaN' as a value for keypoints that weren't detected.

So now to my question: what is going on here? Does OpenPose return a 0 value for undetected keypoints during the live reconstruction as well; and can I not see them/the origin? Or will it have a NaN value during the live reconstruction, but does a filter of some sorts convert these NaNs to 0s when it saves it in JSON files?

It's a bit of nitpicking, but I was wondering this for practical reasons!

[hadi1376tm]

Hey guys,

I've been working with the 3D (live) reconstruction module for a while now and was left with a question. Let me break it down:

* Looking back at the data, the data is partially filled with zeroes; I guess for keypoints that weren't detected by OpenPose;

* i.e., for keypoints not detected, the origin is given as the value (which is physically not possible in the universe as we know it :p).

* However, I don't remember seeing any dots or anything else 'popping-up' anywhere _during_ the 3D reconstruction; a segment/limb would just disappear;

* i.e. that left me to believe that OpenPose would just return 'NaN' as a value for keypoints that weren't detected.

So now to my question: what is going on here? Does OpenPose return a 0 value for undetected keypoints during the live reconstruction as well; and can I not see them/the origin? Or will it have a NaN value during the live reconstruction, but does a filter of some sorts convert these NaNs to 0s when it saves it in JSON files?

It's a bit of nitpicking, but I was wondering this for practical reasons!

Hi, may i see your custom code for 3d reconstruction?

[AdeV-Oly]

Hey guys,
I've been working with the 3D (live) reconstruction module for a while now and was left with a question. Let me break it down:

* Looking back at the data, the data is partially filled with zeroes; I guess for keypoints that weren't detected by OpenPose;

* i.e., for keypoints not detected, the origin is given as the value (which is physically not possible in the universe as we know it :p).

* However, I don't remember seeing any dots or anything else 'popping-up' anywhere _during_ the 3D reconstruction; a segment/limb would just disappear;

* i.e. that left me to believe that OpenPose would just return 'NaN' as a value for keypoints that weren't detected.

So now to my question: what is going on here? Does OpenPose return a 0 value for undetected keypoints during the live reconstruction as well; and can I not see them/the origin? Or will it have a NaN value during the live reconstruction, but does a filter of some sorts convert these NaNs to 0s when it saves it in JSON files?
It's a bit of nitpicking, but I was wondering this for practical reasons!

Hi, may i see your custom code for 3d reconstruction?

Hey Hadi,

Do you mean my code to reconstruct the JSON output in the program that I use (which is Matlab, so unsure if you would be able to use that)?

Or do you mean the code to reconstruct a person in 3D with OpenPose? Because I don't have that; I 'simply' used the manual provided on this Github.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.