Closed bucktoothsir closed 4 years ago
You just wrote the same thing twice.
I guess he meant between Poses_D3_Positions_mono and Poses_D3_Positions_mono_universal. And also what the difference among those two and Poses_D3_Positions?
From their README:
The parametrizations we provide are 3D positions in the original coordinate space (D3_Positions) and transformed for monocular prediction using the camera parameters (D3_Positions_mono). We also provide 3D Angles for monocular prediction (D3_Angles_mono) and projections of the skeleton onto the image plane (D2_Positions). Lastly we provide 3D positions using the same limb lengths for all subjects (D3_Positions_mono_universal) as a 3D position parametrization that is invariant to subject size. The skeleton information is provided in the metadata.xml file that is delivered with our code.
So D3_Positions
is in world space, D3_Positions_mono
is in camera space (origin == camera position), D3_Positions_mono_universal
has poses scaled to a universal size.
@anibali I guess they may be in different coordinate systems. D3_Positions is the world coordinate system, and D3_Positions_mono is in the camera coordinate system?
@EveningLin Yes
@anibali I still donnot understand D3_Positions_mono_universal. Can you kindly explain "using the same limb lengths for all subjects" ? And in what situation it will be used?
It means that the skeletons are "normalised" to a common scale (e.g., a tall person and short person will have similar limb lengths). It's up to you whether this is something you want to use.
Thanks a lot for your quick reply.
"a tall person and short person will have similar limb lengths" wouldn't this cause something wrong? Does this mean the tall person is normalized to the common scale and other body parts also normalized propotionally? Can I take it as "clip" a person into a common range?
I still can't figure out a situation in which it can be used.
I am confused about it because I saw some pose estimation model used Poses_D3_Positions_mono_universal instead of using Poses_D3_Positions or Poese_D3_Positions_mono.
It depends on what you are trying to achieve. If you are just trying to recover the configuration of joints to e.g. recognise an action, then you might not care about scale differences and could therefore use Poses_D3_Positions_mono_universal to simplify the problem. The scale/depth ambiguity problem is tricky, and not everyone is interested in solving it when doing pose estimation.
emm, you are right, it does make sense to ignore scale when considering pose estimation. I think I get a better understanding about it. Thanks. One more question, Poses_D3_Positions_mono_universal is also in camera coordinate system like Poses_D3_Positions_mono or in world coordinate system?
"mono" in the name means camera coordinate system (i.e., monocular pose estimation).
it seems that they stores the same value