Kristijan Bartol

I also have the same problem with PyTorch3D, which I haven't solved. As a temporary solution, I commented out pytorch3d imports. Luckily, I didn't need them, but this requires a...

Hi @jin-s13 , thank you for your assistance and I apologize for inactivity. I planned to have time for this, but got burried under other obligations. I postponed it for...

I'm sorry, guys. I have to postpone this for later. It is still on my roadmap, but I have some higher priority tasks in the next few months.

I guess this feature is now implemented in https://github.com/PyTorchLightning/metrics/issues/799, except for MeanBad{n}Error metric? Should we also attempt to implement this third metric in torchmetrics instead of here?

Hi @anas-zafar , thank you for the reminder and I'm sorry to disappoint! I am currently working hard to finish my new work so I can't finish v0.2. As a...

Hi @yohanshin , I apologize for my late response! You should be able to use `h36m_known.pt`. The `h36m_custom.pt` comes in in case you have your "custom" parameters, i.e., estimated by...

Hi @AndreAhmed , Could you also provide the results for the updated height? Are the measurements now more accurate? Note that the results you get from a single image might...

All the measurements are extracted exactly as shown in the Figure you attached. You might say their definition is "fixed" w.r.t. SMPL(-X) meshes, yes. If you specify a different height,...